Traduzione Comunicato postato da: Sanya Thomas

Le due domande piu' ricorrenti da quando abbiamo annunciato annunciato il concetto del server clustering sono state "quali server verranno clusterizzati" e come verranno gestiti i gruppi tra server.

Alle 8:00 AM EST di Martedi 8 Febbraio tutti i server saranno spenti per patcharli alla 1.74 dalle 10:30 AM, tutti i Server torneranno online eccetto Palomides, Iseult, Bors, and Gawaine che verranno clusterizzati alle 3:00 PM EST.

Riguardo ai personaggi di diversi erami all'interno dei server clusterizzati che gia' esistono: Noi ovviamente non Cancelleremo nessuno dei personaggi esistenti, comunque, i giocatori dei rispettivi server clusterizzati non potranno loggare negli altri reami  per 8 ore dopo aver sloggato dall'ultimo reame. Per esempio, se logghi dal reame di Midgard su bors, e slogghi, non potrai loggare su Hibernia Gawaine o Albion Iseult per 8 ore, potrai comunque loggare qualsiasi altro personaggio su Midgard, ovviamente facendolo resetterai il "Realm timer".

Da domani, i giocatori su qualsiasi dei server nel cluster potranno scegliere un reame, e non saranno piu' in grado di creare nuovi personaggi sugli altri reami nel rispettivo cluster.

Come Sempre, noi controlleremo qualsiasi segnalazione sul "cross teaming", e prenderemo i dovuti provvvedimenti quando il cheating può essere dimostrato.

 
The top two questions we’ve received ever since we announced the concept of server clustering are “what servers will be clustered” and “what will you do about cross teaming?”

I giocatori che sono stati con noi durante il lancio di New Frontiers si ricorderanno che abbiamo resettato tutte le relic e bloccato tutti i keep (e riaperti con un rilascio controllato) per dare ai giocatori piu' campo possibile, stiamo programmando la stessa cosa per i server cluterizzati.

Posso riprendere esattamente il mio vecchio post, perche andremo a seguire esattamente la stessa procedura:

Nessuno dei reami sarà pronto o ben difeso durante le prime ore, per indirizzare questa situazione riguardante solo oggi, andremo a realizzare una fortificazione temporanea, andremo a realizzare tre stati di procedura, dandovi la possibilita' di organizzare le vostre linee di combattimento e di difesa prima di marciare in battaglia, questa procedura e' per oggi, e SOLO per oggi.

Articolo originale in inglese !

At 8:00 AM EST on Tuesday, February 8, all the servers will be taken down for 1.74. At 10:30 AM, all servers will return except for Palomides, Iseult, Bors, and Gawaine. Those servers will be clustered and brought back online at about 3:00 PM EST.

Regarding characters from different realms within the cluster that already exist: We will obviously not be erasing any characters. However, players on clustered servers will not be able to log into different realms within the cluster for eight hours after logging out of any particular realm. For example, if you log in to your Midgard character on Bors, and log out, you will not be able to log into your Hibernian from Gawaine or your Albion friend from Iseult for eight hours. You can log into any character from Midgard, of course, but that will reset the “realm timer.”

After tomorrow, players with no characters on any of the servers in the cluster will be able to choose one realm, and will not be able to make characters of a different realm anywhere in the cluster.

As always, we will continue to investigate any reports of cross teaming, and take action when cheating can be proven.

Players who were with us when New Frontiers was launched will remember that we reset all relics, and locked down all the keeps (and then opened them with a controlled release) to give players as even a playing field as possible. We’re planning to do this again for the clustered servers.

I can even reuse my old post, because we’re going to follow exactly the same schedule:

None of the realms will be fully prepared or well defended for the first few hours, and to address this one-day-only phenomenon, we’re going to build in a little fortification time. We’re going to put in three stages of temporary speed bumps. This way, we’ll all get the chance to develop our front lines and defenses before we march out to battle. These speed bumps are for today, and today ONLY.

Here’s what you’ll find going on today:

- When the servers first go live this afternoon:

* all relics will have been returned to their home shrines;

* all keeps and towers will be unclaimed and set to level one;

* all keeps and towers can be claimed and upgraded, but not be attacked.

- Stage One, accompanied by a system broadcast alerting players of the change, will set Caer Benowyc, Bledmeer Faste, and Dun Crauchon to be attackable (including all associated towers).

- Stage Two, accompanied by a system broadcast alerting players of the change, will set Caer Berkstead, Caer Erasleigh, Caer Boldiamm, Nottmoor Faste, Blendrake Faste, Glenlock Faste, Dun Crimthainn, Dun Bolg, and Dun na nGed to be attackable (including all associated towers).

- (Starting at approximately 9pm EST) Stage Three, accompanied by a system broadcast alerting players of the change, will set Caer Sursbrooke, Caer Renaris, Caer Hurbury, Hlidskialf Faste, Fensalir Faste, Arvakr Faste, Dun da Behnn, Dun Scathaig, and Dun Ailinne to be attackable (including all associated towers).

The primary reason that we use the term 'approximately' is to note that these will be hot changes to the servers, and, as such, these changes will gradually flow to each server. It’s not like flipping a switch, unfortunately. While we will be making these changes as quickly and as carefully as possible, the process is not instantaneous.

And of course, this being launch day, there may be unforeseen issues that alter these planned times. Watch the Camelot Herald for updates, and spread the word in game to your allies that do not read the Herald.

This is the only cluster we will bring live for the time being. Once we see how things are going and address any issues that come up, we will begin the discussion about which servers should comprise the next cluster.

As always, we thank you for your feedback and your patience!