Event Period: Thursday, February 8, at 12:00 a.m. (PST) to Wednesday, February 21, at 6:59 a.m.
Read on for details.
We are planning a mass test on Singularity for testing changes for the February release.
This time we are testing a number of significant changes in the audio code and graphics engine, Upwell structure changes, and general client and server performance.
If you’re interested in attending please join us on Singularity on Thursday the 25th of January at 17:00 UTC.
Participants will receive a reward of two million skillpoints (available only on the test server Singularity).
Please note that numbers, art assets, and other game properties on the test servers are not final and may change before they are released.
We're happy to announce that the Octopus Red Flight SKIN set has been made available in the New Eden Store for selected Caldari hulls:
Head on over to the New Eden Store to grab these SKINs for your collection!
Purchasing SKINs is easy:
Greetings capsuleers, and especially greetings fleet commanders and CEO's.
After some discussion with the CSM early last week about issues with filing fleet fight notifications, teams Webster and Tech Co have collaborated to bring an update and improvement to the fleet fight notification tool. For those who have not seen this before, this tool allows players to confidentially notify CCP of their intention to have a large fight. This allows us to place the solar systems involved in the fight on a dedicated high-performance node to provide the best possible experience.
The CSM raised the issue of players struggling to use the tool, which would sometimes reject requests for node reinforcement for unclear reasons. The common concerns were that the issue seemed to be related to requests for fights within the next 24 hours.
After investigation, we have found that the exact cause of the issue was a logic statement that was not quite correct, and went like this:
"If the start time of the fight is less than 24 hours from the time the request is filed, reject the request".
This is incorrect because nodes are mapped at downtime. Thus, if you file a request at 17:00 for a fight starting at 14:00 the next day, it will be rejected. If you file a request at 17:00 for a fight starting at 19:00 the next day, it will be accepted. However, these two statements are actually functionally synonymous, because the node must be mapped at downtime on the day regardless.
Savvy FC's have figured this out, but it is confusing to those not in on the secret. Prior to last Tuesday's fight in 9-4RP2, some pilots expressed frustration over their inability to file notifications, while others were able to slip requests in mere hours before downtime.
We have changed the logic of this procedure. The notification tool now performs three checks, in this order:
To put the third point another way: you must file a request at least one hour before the downtime prior to your anticipated battle.
We would like to remind pilots filing requests that more warning is better, but this change should take a lot of the pain out of filing short notice notifications.
This change was deployed today at 14:00 UTC.
We're happy to announce that there is currently a 30% discount sale in progress on the following Equilibrium of Mankind SKINs in the New Eden Store:
These discounts will be available through until downtime on January 23rd, so be sure to grab SKINs for your collection at these lower prices while you can!
Purchasing SKINs is easy: