CCP_Aurora

I guess that’s left up to the judge’s interpretation. I’m thinking bellicose gang tbh.

… Can I enter?

This is a fairly complicated question! Given my understanding of destiny ticks, the way this would go is the following: (disregarding latency for the moment)

• Ship decloaks, SRT timer started
• During the timer, whenever you send a lock request the server looks at it and says “no, can’t do this yet” and notifies you of this fact on the next tick (you can see this yourself by spamming lock requests on a thing during SRT and watch the notification flash once per second, at the tick rate)
• After 4.5 seconds the server now knows that it can accept new lock requests, it queues a task to notify the client of this on the next tick, but you can still send the command in earlier and it will accept it
• Assuming you get a command into the queue immediately to begin locking then the locking process will start immediately and run for its duration, in this case 3.2s, notifying your client of a successful lock after 4 ticks (however you receive a packet asap noti...

I’ll be sure to try and discuss this in the...

Bunch of small updates being worked on, I’ll be sure to keep poking them about this one for you!

Edit: It’s on the list, they’ll be done in bulk here soon.

I understand that some of you are unhappy that you aren’t being given the chance to influence whether these gates are being built, but this is a reminder to please keep your responses civil.

You are allowed to express disappointment but inappropriate comments will be removed and warnings / silences issued as necessary.

That’s the dream!

We should hopefully be able to bring in some of these videos into the client in the near-ish future.

That we can do

I’m just trying to think of other ways it could be worked into the paths perhaps as well.

Thanks for the feedback - we’ll take a look at how the magic 14 are presented.

They have some value in being broadly applicable and good queue filler, but you’re right we don’t really want these to become the default training queue for a brand new player either.

This resource is pretty focused on showing players what they can do in-game and learning first steps in terms of mechanics and opportunities. We’re looking at other ways to better surface lore / world news, but if I can find a way to work a bit more lore / a link into it from these academy pages I’ll be happy to do so.

Thanks! And yes, we’re aware. We’re working on adding the updated fit now.

We’re trying to fill a different niche. E-Uni is a fantastic resource but we wan...

Yep, voting is now closed. Thanks to everyone who took the time to vote!

We learned from the best haha

But this will be the last one. Our lead was shrinking slowly just before the percentages went dark for the last 24 hours. So there’s still a risk for our top competitor (the healthy meals app) to overtake us here.

Today is your last chance to vote for Project Discovery as ‘Best Public Service, Activism & Social Impact Game’ in the 25th Annual Webby Awards. Vote now to help EVE win the internet’s top honor!

Please take a minute of your time to vote now and get your contributions recognized.

A ‘reinforced’ node is a node like any other - the difference is that instead of letting the load balancer auto assign a system to a node as would normally happen, we manually assign the system simulation to its own node, so it’s not competing with any other processes on the server and has access to all of the available resources. We have a few decently powerful machines we can swap in for such purposes, but it’s not a big difference in computing power from our standard nodes.

It does sound dramatic!

A node is basically a server in the cluster (the network of servers) that make up the game. Each node runs various processes for the game to work - markets, character info, solar system simulations (the main flying around and doing stuff part of the game), etc.

When a node dies it takes with it all of the services which were assigned to it (these may vary day to day for most nodes as the system auto-allocates based on how much resources they’ve needed recently).

Here you can see the basic layout of the EVE cluster which makes up the game. The nodes in this image are the SOL and Proxy servers:

In this case, this was a SOL node death. A ...

A node death occurred in the Forge market at 11:32. This node failure is currently impacting the cluster with multiple other systems now experiencing issues. Players may get disconnected if they are on affected nodes.

We are currently working on restoring all nodes to proper functionality. We will update with more details as they become available. Thank you for your patience.

Update 12:29: Systems have been restored and should now be working properly. There are some lingering issues with portal app functionality which we are working on resolving.

I’d try restarting your client and giving it 10 minutes or so to update the database. If you still have things missing, put in a ticket to support.

Server team: Points to network team

Network team: Sleeping in a wire closet somewhere, blissfully unaware of any issues

Huh, that explains why the error log buffer is filled with 86TB of “SERED HAS RETURNED, THE MACHINE GODS TREMBLE” print commands.

We became aware of mutliple node failures due to a database issue at 15:37. We are currently investigating the cause and working to restore the game servers. More information will be made available regarding this issue as it is uncovered.

Update 15:50: Cluster is being brought fully offline with a 5 minute timer to be restarted.

Update 15:55: Database issues have been resolved, nodes are coming offline for restart. Expected return to service shortly.

Update 15:58: Currently attempting to restart cluster.

Update: 16:01: Cluster is back online, currently in VIP mode for final tests.

Update: 16:03: VIP disabled, cluster is now open once again. We will continue to monitor it for stability.