Home | Evony News | Advanced Notice: Evony Server Merge in 2023
Dear Evonians,
To create a better gameplay environment, we plan to do a server merger in the near future. After the merger, the two servers will share the same world map but can still enter the game from the respective original server access. The new server’s number will be determined by the higher SvS ranking. All the personal data will remain and this includes the buildings’ level, VIP level, Gems, Gold, resources, sub-cities, Generals, troops, and items. That means players will not lose any of their personal data.
Evony Server Merger
The Server Merger will happen in the following pairs:
Server 105 and Server 192
Server 628 and Server 615
Server 694 and Server 601
Server 382 and Server 365
Server 338 and Server 341
Server 635 and Server 618
Server 81 and Server 157
Server 339 and Server 364
Server 765 and Server 781
Server 472 and Server 552
Server 251 and Server 189
Server 344 and Server 294
Server 735 and Server 804
Server 200 and Server 193
Server 297 and Server 316
Server 613 and Server 563
Server 239 and Server 215
Server 348 and Server 303
Server 196 and Server 270
Server 140 and Server 160
Server 197 and Server 287
Server 604 and Server 525
Server 307 and Server 399
Server 308 and Server 319
Server 603 and Server 607
Server 611 and Server 649
Server 478 and Server 454
Server 309 and Server 367
Server 574 and Server 637
Server 698 and Server 652
Server 697 and Server 700
Server 742 and Server 780
Server 641 and Server 657
Server 456 and Server 499
Server 450 and Server 476
Server 291 and Server 258
Server 632 and Server 621
Server 312 and Server 318
Server 355 and Server 402
Server 159 and Server 272
Server 284 and Server 313
Server 207 and Server 238
Server 798 and Server 782
Server 44 and Server 10
Server 85 and Server 183
Server 32 and Server 208
Server 333 and Server 225
Server 760 and Server 695
What happens after the server merger?
The Alliance will remain but all the Alliance Buildings will be removed. All players will be randomly teleported on the new world map. Rebuilding the Alliance City does not cost resources or time. (If an Alliance hasn’t built the Alliance City or is building the Alliance City, it will still cost resources and time as usual) The Alliance Donation and stored Warehouse is rebuilt.
A player still owns his/her original sub-cities. The Server with a higher SvS ranking keeps its original sub-cities and takes in the non-NPC sub-cities from the other Server. The NPC sub-cities from the other Server will be removed.
The bookmarks on the two Servers will be deleted because they won’t be useful anymore to all the Servers.
All the Resource Spots and Monsters will reset. All the Relics will be removed. All the troops outside will automatically return to their City.
All the rankings will reset and refresh according to the players’ data on the new Server. The SvS ranking and Battlefield ranking will show as the new Server number that has a higher ranking.
The Empire name, Kings and Titles for the Server with higher SvS ranking will remain unchanged, the Empire name, Kings, and Titles for the Server with a lower SvS ranking will be deleted. If a player has unlocked The Monarch’s Glory, he/she will still get the glory in the new Server. If not, the player will have to be King twice again.
All Temple Effects of the original Server will be removed.
The Monarch Competition Event will reset and the last stage event’s rewards will be sent.
The world chat messages will be removed.
The Undead Event and Monarch Competition records will be removed.
The monarch’s name will be added with a number if two players have the same name. For example, two players, both named Evony, will become Evony 1 and Evony 2.
The arch of triumph data of the two Servers will be combined.
The Temple data is subject to the Server with the higher Server War rank.
In Evony, Mounted Troops excel at attacking Monsters and Bosses. The new Assistant General feature allows the main and assistant generals to combine their strengths for even greater power.
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
This website uses cookies
Websites store cookies to enhance functionality and personalise your experience. You can manage your preferences, but blocking some cookies may impact site performance and services.
Always Active
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Service URL
_dc_gtm_
Used to monitor number of Google Analytics server requests
1 minute
-
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
-
_ga
ID used to identify users
2 years
-
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
-
_ga_
ID used to identify users
2 years
-
_gid
ID used to identify users for 24 hours after last activity
24 hours
-
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
-
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
-
__utma
ID used to identify users and sessions
2 years after last activity
-
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
-
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
-
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
-
__utmxx
Used to determine when the A / B or Multivariate test in which the user participates ends
18 months
-
FPAU
Assigns a specific ID to the visitor. This allows the website to determine the number of specific user-visits for analysis and statistics.
session
-
FPID
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
-
FPLC
This FPLC cookie is the cross-domain linker cookie hashed from the FPID cookie. It’s not HttpOnly, which means it can be read with JavaScript. It has a relatively short lifetime, just 20 hours.
session
-
AMP_TOKEN
Contains a token code that is used to read out a Client ID from the AMP Client ID Service. By matching this ID with that of Google Analytics, users can be matched when switching between AMP content and non-AMP content. Reference: https://support.google.com/analytics/answer/7486764?hl=en
30 seconds till 1 year
-
_gat_gtag_
Used to set and get tracking data
1 hour
-
cookiePreferences
Registers cookie preferences of a user
2 years
-
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
-
GA_OPT_OUT
Cookies used for functionality allow users to interact with a service or site to access features that are fundamental to that service. Things considered fundamental to the service include preferences like the user's choice of language, product optimizations that help maintain and improve a service, and maintaining information relating to a user's session, such as the content of a shopping cart.
10 Nov 2030
-
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
-
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
-
comment_author
Used to track the user across multiple sessions.
Session
-
comment_author_email
Used to track the user across multiple sessions.
Session
-
comment_author_url
Used to track the user across multiple sessions.
Session
-
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
-
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.