EVE Online Dev Tracker

Hi all

If you’ve not seen the information about the second Native Mac Client playtest, please check out the news article first as it contains important information.

This thread is for general feedback for the client and the launcher. If you’ve found a bug, first please file a bug report from the client unless you’re unable to do so. You are welcome to discuss bugs in this thread.

Thank you for the report. This is being addressed and will hopefully be fixed soon.

Hello! We recommend that you use any of the following ways:

• Please take action on each event, such as accept it.

• Create every event instead of just modify the old one.

Hello! Please kindly note that the skill training queue limit for alpha accounts is 24 hours.

Hello! Please accept an event in the client and refresh the calendar in the app to see if the issue gets resolved.

If you are using an external monitor you could try the solution presented in the linked forum post.

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

This usually occurs when you start a client with an account that is already running.

Your launcher log file for the session in question might have provide more details on why this occurred for you. But since the launcher only keeps the last five logs it’s unlikely you still have the log for that session.

If this happens a...

… 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...