its unbelievable that with a few bugs still in the game that they started new servers. i guess they need to pay the programmers to fix them..
The last stable version i recall was right before they changed the lobby and removed global crowns. Before then the game was at its most stable in terms of functionablity.
l
Counts no longer train from the mass production. Say you have a group of villages you want to train 4-5 counts it skips counts. other units seem to queue up ok.
mini map broken in this release when in HR mode now. Move within the mini map or clicking the arrows kicks you out of the HR and back into your own account.
Also broken with mimimap but not new is groups are dropped when you scroll / move around with the arrows then click a village.
I am going to respond to this post with a professional opinion as I was a coder in the early 2000s. I highly doubt the programmers aren't making bugs purposely. I believe they are utilizing AI (eg chatgpt etc) more to generate the code and pasting it into their builds. I have been experimenting lately with AI for coding in my old programming languages of the late 1990s / early 2000s. It is very good at quickly developing new features which is an inexpensive way to update this game without long man hours. The original developers of this game would had been very dedicated to their error testing processes and hense when they fixed a problem in the old days that problem stayed fixed. Now with my recent experience with using AI to help with code building, it tends to overlook some things that a human would consider, and hense we are getting more bugs with each new release with new features added. I've seen in this last update 6.14 that a problem that was here in 6.12 but was fixed last month in 6.13 is now back again - golden armour production for accounts under HR. A decent human coder would likely be aware of this having just fixed the problem, but AI may not necessarily do the same.
I have sent in a ticket for this and currently awaiting updated response.
In conclusion, this appears to me the coders are heavily relying on AI more and doing less testing than the old school developers would had done.
With this update they have broken mass production of golden armor again for when HR of an account. This problem occurred a few weeks ago and then they fix it in last month's patch. Now with the new Version 6.1.4 it is broken again.
I should mention that I was a programmer in the late 1990s / early 2000s and don't recall the number of problems being seen here. we checked our code and tested the latest version in house with dummy data before letting a small number of customers run with the new version for a time before rolling it out to the rest of the customers.
I would suggest they create a beta server which is perhaps 10x speed and for new accounts let them start with some villages of various development stages, but mostly maxed. Run the updates on the beta version first an announce it to all the community to try it first. We can then report back bugs before and have hopefully fixed before releasing to all servers. It would go a long way at not pissing everyone off.
They have broken mass golden armour production again when operating in HR mode. It was fixed last month after being broken for a few weeks. now they screwed this part of the game again.
They have an update next week. Lets hope they fixed everything as they listed some items but i'm a bit nervous as some problems are not mentioned.
I see an update is due out next week. Be sure to re-check the bugs you found and re-submit any not addressed.
no, he is spending around $500 or more on crowns so he can spin on the wheel to get resources at the certain tiers of points then does a special build order to advance his points to the next tier level where the wheel returns are bigger.
Just a luck of the draw if you play in on a server where an opposing side has someone also doing the same and is not a noob.
This is true Cleo, ....but my sett was the fourth sett and the number NOT number 4 , no it was not, it was 5449.
How bad do you have to screw up to get the numbers to start at 5446 , instead of 1 .
I think they have combined their back end databases with other worlds or servers hense player numbers and settlement numbers are no longer starting at 1. In the past they seemed to have a seperate database for every server world.
If they really wanted to reduce server lag and server load they should address the redundant code in their page which is increasing noticeable when the group code is not used. On every page they are loading the names of every settlement into the webpage for no apparent reason when not in a settlement group. I have an account with 13,000 villages. when i open any page when not in a group it will load every one of my settlement names into a list. This includes opening a simple attack report. The page size in my case goes up to 2.5mb in size every page i load. Now if i go into a group with say 5 villages and I open the same attack report the filesize that it opens is drops to around 80kb. I sent a report ticket a couple of months ago but i have not seen anything different been done. Instead they tried to get cute with gold smith and break a few things in the process. I do appreciate the new goldsmith feature.... its great with a 13,000 village account but the broken things need a work around.
I hope they address the 2.5mb file size for every page soon.
Also the mass production of armour is currently broken for accounts in HR mode. Cant produce armour when sitting except if doing it one village at a time. Probably not a major issue for a new world, but on worlds when the account has a lot of villages then its not good.
Sent bug report ticket. reponse was they knew about the above issues but no date on when it will be addressed.
Also affected by the renaming problem is you are unable to label incoming attacks on the banner.
So now is a good time to spam attack because they can't mark their attacks anymore and they also cant remove attacks very easily since they limited it to 10 actions displayed on the screen.
It looks like the developers broke this feature because they want players on old worlds to play the new worlds. They dont make any money on old worlds because people dont spend crowns on old worlds. The wheel of fortune can earn enough to pay premium for most people on old worlds.
New update or 6.0.1 is worse than 6.0.0. It feels like the developers are testing how much patience we have.
- Groups are broken
- mass recruit is broken
- barracks/settlement view page continues to be broken when they limit the number of actions visible at a time to 10
- Global crowns / global items were never fully re-imbursed as they promised
More people I talk to are fed up to including you Richard. I know you actually contribute a lot each world you play.
It is becoming apparent to me that with every new release they put new bugs in and break some features. Seems to have been the case since the beginning of the year.
Haven't seen anything positive been added for quite some time despite the hype written in the notices.
When starting a new village, the other one becomes abandoned.
What happens is that people create the village and then they don't develop it, leaving the ratio forever and because of the ratio, we can't conquer the villages
They go abandoned after about 6 weeks and randomly spawn somewhere around the edge of the map. Its not an issue for moderate numbers but when a sea of them are created as mentioned above then yes it can be very time consuming to deal with at the 2nd-3rd month of the world. Sometimes they have removed some of them from the map when a huge number is a problem for a world. Hopefully in the new update the developers have made tools for the admins to deal with them easier. I hold my breath though,
o recomeçar ainda se justifica pois o jogador nao gosta de estar num sector e recomeça num outro sector para ficar mais perto das pessoas amigas ou ate da sua aliança.o que nao se tolera é criarem a aldeia e depois nao a desenvolvem ficando para sempre com os 50 pontos e nem dá para atacar nem conquistar
Starting over is still justified because the player does not like being in one sector and starts over in another sector to be closer to friends or even their alliance. What is not tolerated is creating the village and then not developing it, remaining with it forever. 50 points and you can neither attack nor conquer
Either
1. relocation if want to move to new sector.
2. set village to delete (5 days) and start with new name
3. keep building and go pure defense until conquest protection ends and gift to a team mate then start after being conquered.
Like i said, the Start Again feature is abused 95% of the time it is used by cheaters to get them free villages before the conquest period is over on some world settings.
Hoping the developers with the new version of the lobby system make it harder for people with script bots to create new villages en-mass.
Also the "Start again" feature is abused over 95% of the time so needs to be addressed somehow. These two changes would go a long way to addressing your concerns.
You can find out who were the old gifts by keeping a record of all the player names, and the settlement number that they owned. TRUE its a bit of work to do from a team or player perspective, though game developers can easily make a way for their admins to see who the deleted accounts belonged to and if they restarted. There are ways for admin to know, but their hands are probably tied to do anything about it or its just too much work to know whats going on unless they are actually playing the world and following closely.
Edit Chirris.
This seems to happen for various reasons.
- Someone in your alliance may have support in the village you are attacking. But since its a world with many villages then its unlikely support in every village.
- Sometimes this happens if the defender doesn't have an alliance. Since that member already has an alliance, suggest that player disband their alliance and create a new one. Then you can try agaain.
- It could be player specific. I suggest one of your members leave your alliance, create their own alliance and then try again.
