• Dear forum reader,
    To actively participate in our forum discussions or to start your own threads, in addition to your game account you need a forum account. You can
    REGISTER HERE!
    Please ensure a translation in to English is provided if your post is not in English and to respect your fellow players when posting.

Feedback Daily Changelog w/c 1st March

iPenguinPat

Squire
Adding a delay to aborting quests as a ghost change is the worst possible "solution" for fixing the recurring quest abuse.

Players that built their cities around recurring quests should not be punished for cleverly using the mechanics that innogame provided.

Macro users are the biggest abusers of recurring quests. This nerf will only require a slight adjustment in their click delay, and they'll be off the the races again, recurring like nothing ever happened. Meanwhile, legit players are stuck with a painfully slow recurring quest cycle that makes questing almost too slow and painful to manage.

This appropriate option would be to be more proactive at seeking out macro users and penalizing them for breaking the rules/cheating. If a player is willing to setup their city to maximize the mechanics of the game, they should not be penalized for the exploits of cheaters. Please rollback the quest abort delay to how it was before. The majority of players should not suffer because the few that are cheating and abusing the system.

This video covers the topic of macro abuse:
 

Heinrich IV

Merchant
Does anybody know when the GB dialog position or size was changed? I did not find it in change log but the position of th ebutton is different now resulting again in more mouse movement and of course as result of this in lower fighting speed in GB.
 

Outlaw Dread

Baronet
Adding a delay to aborting quests as a ghost change is the worst possible "solution" for fixing the recurring quest abuse.
........
This video covers the topic of macro abuse:

FoElite’s video on "how to cheat in Forge of Empires", lays out very clearly how macro-users are damaging the game, and how Inno's introduction of a delay was a terrible, and useless, response.

Then: post a link to that video on every feedback forum you can, with a call for Inno to undo the delay to aborting quests, and instead adopt some real solutions that actually would end use of macros.

The greater the number of players calling for change, the more likely Inno will listen.
 

Julian24

Viceroy
how Inno's introduction of a delay was a terrible, and useless, response.

Then: post a link to that video on every feedback forum you can, with a call for Inno to undo the delay to aborting quests, and instead adopt some real solutions that actually would end use of macros.
You know inno already said, that it is a bug and that they are going to fix it? Right?
 

iPenguinPat

Squire
You know inno already said, that it is a bug and that they are going to fix it? Right?

For the first 24 hours, support was saying that it was not a technical issue or bug and that it was behaving as intended. I have plenty of screenshots from players all over that got the same form message saying it was intended.

They have said it will be "fixed' but they didn't say the user experience would return to how it was previously. Until we see what the fix is, it seems reasonable to provide feedback that any additional delay not supported by the playerbase.

The lack of transparency is not a good look for this type of thing. I'll detail the issue(s) more in another medium where it's more appropriate.
 
Last edited:
Top