Community Update: Week 30

This is what happened since the last community update:

Final Version of the Interface Redesign

On Thursday, our graphic artist David introduced the final version of the interface redesign that will soon replace our current UI on the devblog. For recall, the main reasons why we want to change the interface are:

  • Optimizing the interface for our minimum screen resolution of 1024 x 768 px
  • Reorganizing elements in a more logical and intuitive manner
  • Improved integration of the latest features, i.e. inventory, heroes, quests
  • Visually improved design of the interface

You can check out the details about the changes we made since our last concept works in this devblog entry.

Beta Update 2.43

The development of the new Grepolis update 2.43 has been finished on Friday. The latest changes have already been deployed on our beta environment (http://beta.grepolis.com). This version mainly contains bugfixes and improvements for Grepolympia.

The current update schedule is the following:

  • July, 25th: first French and German worlds;
  • July, 30th: EN market;
  • July, 31st: FR and DE markets;
  • August, 1st: international roll-out.

Monthly Feature Voting

Last week was the third official monthly feature voting. The results are the following:

  • Town Being Attacked Shown in Notification 4.34/5
  • Online Status of Alliance Members 4.21/5
  • Effects in Simulator 4.06/5

Therefore, we will integrate the first suggestion in the game with 2.45. Thanks for your ideas and for participating in our vote.

Current Progress

On Monday and Tuesday, the team focused on fixing bugs and the development of version 2.44 started today. The goal of this version is to implement the new user interface as introduced here last week.

Weekly Stats

The following stats are for activity between July 18th and July 24th:

Bugs

  • 21 bug reports have been created this week
  • 14 bugs have been resolved this week
  • 6 bug reports have either been a duplicate or invalid
  • 56 bug reports are currently unresolved

Bugs hot-fixed during the week

  • N/A

Support activity

  • 5522 tickets opened
  • 5736 tickets answered
  • 5.65 hours average first response time
  • 146 tickets rated
  • 3.93 rate average (of 5)
Tagged with: , ,
Posted in Community Updates
7 comments on “Community Update: Week 30
  1. Primitive says:

    I have just a quick question, my apologies I it has been asked, is there an ETA for the new mobile app? Using the current one is painful and I cannot wait for the new version 🙂

  2. anonymous says:

    So, 2.43 will be installed on the EN market on the 30th of July, correct?

  3. Good evening,

    “Therefore, we will integrate the first suggestion in the game with 2.45 […]”. I dont understand this. This monthly voting is on a wrong way. All of the ideas were good, and all of them should be implemented to the game. There should be a yes or no button in the voting to decide which idea to implement, but only 1 idea can win. Thats not good. If an idea has more “yes” than “no” it should be implemented to the game. Online status, and effects in the simulator were also very good ideas, why only 1 can win?

    Thank you,
    Tamás

    • Marcel Zons says:

      Sure, we could change the voting so each player can only pick one of the suggestions. But the way it is now we get to know which feature will cause the most satisfaction througout the community.

      The remaining suggestions (which didn’t win) are not lost. They will probably be implemented as well, somewhen. The voting just points which of the features gets implemented first. 😉
      (and bad rated features will be ignored)

  4. Quack says:

    I think this rating system will lead to biased results. People will tend to rate the features they want less much worse in order to push the one idea they want most. This rating system does not reflect the true opinion about the quality of a feature/idea but just what people want most if they had to choose. I would therefore suggest you put in a 3 way ranking system (first/second/third place) and the user can rank the ideas to his/her liking.

  5. Stoned Silly says:

    I agree. As in voting I think a simple yay or nah system would be effective.