What went wrong?

By using our site, you accept the use of cookies to make your visit more pleasant, to offer you advertisements and contents tailored to your interests, to allow you to share content on social networks, and to create visit statistics for website optimisation. More information

  • What went wrong?

    What was the big change that happened a month ago that has led to such unstable servers? With new bugs almost daily found at least on the speed servers (not sure on slows) - Surely someones trully ballsed up somewhere? Why can't the game revert back to the coding prior to these issues?

  • We apologize for the inconvenience caused in the game. The worry from the community about frequent bugs has already been reported to HQ.

    The codes are tested well before rolling out, but sometimes the bugs are popping up while loaded to main live servers. Our team is doing their best to fix the bug quickly and come with roll out pretty fast.

  • It really doesn't feel like much is being done to prevent the bugs from happening though...There have been multiple gamebreaking bugs lately and there are even some at the moment...And the one I know of is possible due to the server being legit trash.

    Can't you get your specialists to fix it?

  • I hope you are referring to the unexpected downtime that we faced last month. Travian Games is taking precaution to avoid such unpleasant experience in future.

    The issues are unintentionally happening and random. When it happen specialists are there to fix it soon.

  • No I'm talking about the current issue that makes it possible to queue buildings for free. Only works on buildings, unfortunately it doesn't give us free ress to queue troops this time..But I'm sure the specialists are already working on a hotfix.

  • dario wrote:

    I hope you are referring to the unexpected downtime that we faced last month. Travian Games is taking precaution to avoid such unpleasant experience in future.

    The issues are unintentionally happening and random. When it happen specialists are there to fix it soon.
    Oh thank god these issues are unintentional. At least if they were intentional then TG would actually have a plausible excuse, except they don't. Just shows how incompetent TG really are.

  • While the MH cant fix the game. Raising a ticket it the fastest way to get information passed directly to techsupport. The simple act of moving the ticket direct to their queue with the details of a player who has experienced the issue gives Techsupport and QA a fighting chance of reverse engineering back to the cause of the problem.
    128-10-93-85-10-128-98-112-6-6-25-126-39-1-68-78

    Game Rules | Terms & Conditions | Rules FAQ

    Game issues can only be answered by sending an In-Game Message to Multihunter / Support
    Or via the Homepage Support form

  • Lemon wrote:

    Meme wrote:

    Your avatar makes you look about twelve years old. Naturally you have reported this to the in game MH?
    No I haven't as the MH can't fix the game.
    Yeah but... but....

    As a contribution to the correct operation of the game, the user is advisedto always appropriately document any defects that occur in the game orin any other deliveries or services of TRAVIAN GAMES and, in particular,to report them, documenting any error messages that occur.(3) For the user's own protection, and in particular for reasons of securing evidence,the user is recommended to direct any notices of defects in writingto TRAVIAN GAMES.(4) TRAVIAN GAMES shall not assume any guarantees in the legal sense, unlessexpressly otherwise agreed in writing.

  • dario wrote:

    We apologize for the inconvenience caused in the game. The worry from the community about frequent bugs has already been reported to HQ.

    The codes are tested well before rolling out, but sometimes the bugs are popping up while loaded to main live servers. Our team is doing their best to fix the bug quickly and come with roll out pretty fast.
    That simply can't be true. The Sheer amount of bugs you've had shows that there is no way they are being sufficiently tested?

    Three Major Bugs - With the Unlimited Wheat, 100% Recruitment Bonus, Free Resources for Buildings - And Countless 'Minor' Bugs, such as Elephants and Settlers not displaying correctly on overview and so forth. You say that these bugs 'pop' up during load to main servers, why wouldn't your test environment be based on the 'live' server? If you are testing this against an outdated version, then you're not performing an accurate testing. These bugs are not 'hidden', they're clear as day to see and should've been picked up prior to any of your changes going live.

    In Regards to one bug alone - The Unlimited Troop bug, this has been identified for three days now - and upon discussions with Admin they have advised that this is Still being fixed. What's being done to prevent it? They're checking every so often to ensure no one abuses it - If it wasn't for the honest view originally reporting it would it have been noticed - I very much doubt it. But now we're sat trusting an already clearly incompetent staff to monitor such flaws.

    The Standard has dropped dramatically over the years, previously if you had a query or concern, the staff member/admin would answer it correctly or look to find out to inform you. Now we get shoddy answers such as 'i think' it should, or 'not sure' - When there was issues within Comx the one decided it was opportunity for a bit of 'trolling' - Who are we meant to rely on when these are our (customers) only point of contact?

  • Lemon wrote:

    Press F to pay respect for the poor hamsters
    f





    Amalgon wrote:

    You say that these bugs 'pop' up during load to main servers, why wouldn't your test environment be based on the 'live' server? If you are testing this against an outdated version, then you're not performing an accurate testing. These bugs are not 'hidden', they're clear as day to see and should've been picked up prior to any of your changes going live.
    The update was implemented on the com8 beta before being rolled out on other servers, with both the bug with settlers and elephants not showing, as well as faulty Residence/Palace description being there already. Then they got rolled out ~a week later to other servers with the same bugs ¯\_(ツ)_/¯


    Animis opibusque parati

    com8 (F&S beta) and now back to retirement...

  • I've noticed a few comments recently about the development process and while I can't comment on the process Travian use (since I have no involvement in it and don't know their processes) I might be able to shed light on generic development processes.

    Testing sites, (sometimes referred to as 'staging') are designed to replicate the live environment as best as possible. It's impossible to recreate it completely though. You don't get the full traffic to a staging site, so you can't test that element other than stress testing load balancers, but even that doesn't replicate end user behaviour perfectly. Often things like Google Analytics aren't used on staging sites either and some eCommerce elements aren't (though definitely not impossible).

    For small wordpress sites, a small release can be sorted in a day. The process from my experience involves; Investigate > Code change > internal test > Push to live > Live testing > If successful, beer / If unsuccessful, repeat from start but with stronger coffee.

    For bigger websites with multiple domains, eCommerce, multiple plugins, etc, every release could have a 4 week start-to-finish process including various regression testing stages. Regression testing usually involves testing everything on the site while in staging, and then again on live. From my experiences doing this in my day job, I can tell you there are bugs which always find their way to live despite thorough regression testing. Why? Because different environments react differently.

    The best way to explain it, is to compare writing code to medicine. You can test a new treatment on one patient who is very very similar to another patient. Yet when testing it on the second patient you may notice small differences - the second patient gets the hiccups every night at 6pm, because this patient reacts different to having their IV drip replaced. Giving them a different IV solution may solve it, it may make it worse, it may have no impact.

    Bizarre medical metaphors aside, for such a large set of websites, there is likely a procedure in place, but that unfortunately can't catch everything. And of course there may be areas in which Travian could improve their development processes.

  • Hawk wrote:

    I've noticed a few comments recently about the development process and while I can't comment on the process Travian use (since I have no involvement in it and don't know their processes) I might be able to shed light on generic development processes.

    Testing sites, (sometimes referred to as 'staging') are designed to replicate the live environment as best as possible. It's impossible to recreate it completely though. You don't get the full traffic to a staging site, so you can't test that element other than stress testing load balancers, but even that doesn't replicate end user behaviour perfectly. Often things like Google Analytics aren't used on staging sites either and some eCommerce elements aren't (though definitely not impossible).

    For small wordpress sites, a small release can be sorted in a day. The process from my experience involves; Investigate > Code change > internal test > Push to live > Live testing > If successful, beer / If unsuccessful, repeat from start but with stronger coffee.

    For bigger websites with multiple domains, eCommerce, multiple plugins, etc, every release could have a 4 week start-to-finish process including various regression testing stages. Regression testing usually involves testing everything on the site while in staging, and then again on live. From my experiences doing this in my day job, I can tell you there are bugs which always find their way to live despite thorough regression testing. Why? Because different environments react differently.

    The best way to explain it, is to compare writing code to medicine. You can test a new treatment on one patient who is very very similar to another patient. Yet when testing it on the second patient you may notice small differences - the second patient gets the hiccups every night at 6pm, because this patient reacts different to having their IV drip replaced. Giving them a different IV solution may solve it, it may make it worse, it may have no impact.

    Bizarre medical metaphors aside, for such a large set of websites, there is likely a procedure in place, but that unfortunately can't catch everything. And of course there may be areas in which Travian could improve their development processes.
    You have time for all that but can't check in on the WW!

    Re testing the issue they don't update the, what you refer to as a, staging enviroment for minor patches. Aka your (travian's) developers are n00bs.