BUGS IN THE NEW WEBGL VERSION OF THE GAME
I have moved this post over from the BETA test feedback topic since moderators no longer respond to posts over there - Please do not delete this.
I was switched to the new version of the game 4 weeks ago. There are so many bugs and problems with it that it is impossible to list them all - here are a few:
- Raiding and Galley trick don't work because of missing links and options
- General equipment screen is a mess (See separate post)
- Opponents listed by General Name not player name on some screens - very confusing
- Jump to map locations from raiding screen is not working
- Copy Paste does not work in message system. Impossible to import text from outside game.
- Graphics don't update on action completion
- Graphics are really really ugly (Faded colors, outlines not crisp, ugly fonts, perspectives not respected, oversized tribute boats, very badly done animations like siege fires etc. - Really Nasty Work! - Hurts the eyes to look at it.
- Text "wiggles" when scrolling screen and even on some fixed windows - very very irritating to look at.
- Game takes forever to load (3 minutes or more) this is very bad because it crashes and freezes frequently.
- The action update time is at least double that of the old game which is HUGE. This game is so dependent on performing thousands of actions a day to compete so if each action takes twice as long to execute Plarium just doubled the "cost" of playing the game. (I have a new computer with latest software and a > 50 Mbps fiber connection - So it's not my hardware or software!)
There are hundreds more... I have already gone from daily player to once a week. It's too painful for daily interaction. I'm not paying money to be tortured this way!
Beta testing should be the last step before a new product is launched. This product was not anywhere near ready to be launched. Using your customers as Guinea pigs to avoid paying for QA testing shows a lack of respect. Requesting detailed technical information on each bug when there are 100s of them is ridiculous. Are the developers so incompetent they can't chase them down from good descriptions? Or is it again a question of shifting the burden of doing the QA work from paid staff to your involuntary Guinea pigs?
