Home | Evony News | Season 1 Civilization Ultimate Battlefield Preview
Dear Evonians,
The Season 1 Civilization Ultimate Battlefield is coming!
The most powerful monarchs from across the continent have emerged victorious in the battle against the Order of Dawn, stepping onto a grand battlefield where fate and hope intertwine.
The battle for the continuation of civilization is entering a new, more intense phase. An unprecedented showdown is about to erupt, determining the future of civilization and who will claim the ultimate glory!
Season 1 Civilization Ultimate Battlefield Reward Examples
Qualification Preliminaries
The Clash of Civilizations – Assault will begin on August 21, 2024!
On August 25, 2024, the Clash of Civilizations battlefield kicks off! All servers will compete in the Clash of Civilizations battlefield to secure 512 spots in the Civilization Ultimate Battlefield. Then, servers that earn a spot will advance to Civilization Ultimate Battlefield.
The top 1 server in each battle will directly qualify for Civilization Ultimate Battlefield.
Other servers will be ranked based on their Clash of Civilizations scores, with qualifications granted accordingly.
Only servers that have been open for more than 5 months are eligible to participate in the Clash of Civilizations battlefield.
We will announce qualifying servers via in-game mail. You can also view the qualifying servers by clicking the “Participants” button in the event interface once the Civilization Ultimate Battlefield begins.
After the Clash of Civilizations battlefield ends, the system will send rewards based on individual and server rankings. You can check your server’s ranking on the Rankings page of the Clash of Civilizations battlefield.
Civilization Ultimate Battlefield Rules
The Civilization Ultimate Battlefield is expected to officially begin on September 1st, 2024!
The system will match 8 servers to compete against each other, with the rankings determined by battlefield scores across three stages: Preliminary, Semifinal, and Final.
The preliminaries plan to start on September 1st. The top 1 server from each match will advance to the semifinals. For servers that do not advance to the semifinals, the system will determine the 65th to 512th place based on their preliminary battlefield scores.
Then, the semifinals plan to start on September 8th. The top 1 server from each match will be promoted to the final. For servers that do not advance to the finals, the system will determine the players’ rankings from 9th to 64th based on their battlefield scores in the semifinals.
Finally, the finals will start on September 15th. Servers that advance will compete in the final to determine the final rankings from 1st to 8th!
Event Rewards
Participation grants generous rewards, with the champion server earning exclusive rewards such as Light Effect, Castle Decoration, Avatar Frame, Clash Coins, Blood Crystals, Ruby Necklaces, and Super Safe Resource Chests! The system will send server ranking rewards after Civilization Ultimate Battlefield ends.
In addition, we will send personal score rewards after each stage ends. Depending on your rank, rewards may include Light Effect, Gems, Runestone Chests, Glory Golden Twigs, common speedups, and more.
You can view the detailed event rules and rewards through [Battlefield] – [Civilization Ultimate Battlefield].
Please pay close attention to the event start dates and mail notifications to ensure you don’t miss out on any opportunities!
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.