Stodola

Every day at exactly the same time, the server databases are backed up. This causes a few minutes of high load that can appear as a crash and can cause disconnects.

You'll need to raise an In-game ticket.

This has nothing to do with us.

We do not restore gold or items lost due to server issues, rollbacks, mis-clicks, mis-loots, scamming, hacked characters, or any other reason with the sole exceptions of: 1. Quest items that have been previously possessed by the character and can be verified. We do not fix selecting the wrong quest reward or changing your mind later. 2. Raid items wherein loot is not dropped by a boss, cannot be looted, or for another reason where the entirety of the boss kill is recorded, unedited, and clearly shows the full raid group and the raid ID.

This is not the cause/issue.

db.vanillagaming.org is not an authoritative source on whether a quest should be solo-able. It is intended that this quest takes a party to complete as it did in original vanilla.

We do not disclose information related to server instability for the same reason we don't discuss our techniques for finding gold sellers or detecting and removing bots. Threads regarding server stability are pointless as there is nothing we can share with you beyond "Yes it is down", "No it is not down", and "It is back up". All of which you can get from our twitter and discord.

Posts that are bug reports, unrelated to the specific changes in this patch, or that are just complaining, will be removed. If you want to make a post about those things, use an appropriate forum, if you want to report a bug use the issues register on the official github. Please respect the purpose of this thread and stop hijacking it.

This is not a fix for the rate at which things spawn, it's a fix for things not respawning at all after a period of time.

Please let us know if any residual respawn issues exist.

All my hype.

This issue is a technical one related to the way the core works. The status page polls the realm database to determine which realms are up. Each realm updates that database when it starts up and shuts down. However, if a realm shuts down uncleanly or is under heavy load (which also can appear to end users as if the realm is offline) then the database flag will not be updated. In the former case, realm status is refreshed once the realm starts up again.

All abilities are coded to work as 1.12.1 implementations. If an ability does not work according to 1.12.1 then that is a bug. Please report any such bugs to our official github issue register with as much detail and evidence as possible. Developers do not monitor or respond to these forums.

Make sure you post it in the ban appeals forum section. Not here :P

We appreciate your concern over this but we cannot possibly respond to every single post or query about when a fix will arrive. It will arrive when it's fixed and tested and ready. All progress on fixes can be tracked on GitHub through the issue tracker, and this is also where all bug reports must be lodged in order for the open source contributors and our own developers to see and work on.

We do not offer a method for changing the email address bound to an account - this is simply not possible. We recommend that all accounts are established on email addresses owned and controlled by the player, so that issues like this (and the same applies for educational institution email addresses) do not occur. The email address is the core authentication for an account. It cannot be changed.

Make an in-game ticket with the name, class, level, race, and realm of the deleted character.

Have you checked to see if it is still enabled? A large number of 2FA requests were processed recently per the announcement.

If you have a complete, unedited video of the kill that clearly shows the Raid ID and the raid members, and the fact that no loot dropped, then the raid leader should make an in-game ticket with a link to the video. Outside of this, there is nothing we can do to help you.

This is very true. Raid songflower buff is allowed as bliz-like, this is something that raids have coordinated back in retail and we allow it here.

The population on both Anathema and Elysium PVP was capped at 11k and had 2-3k queues (up to a few hours) on launch.

More correctly, the logon server does not talk or connect to the realm servers at all, the logon server relies on flags in the database to determine whether a realm is up or not (the realm server itself updates these flags when it starts and stops). The logon server simply directs the game client to the realm server after authentication is complete.

This issue has been reported and can be tracked here: https://github.com/elysium-project/server/issues/2060

Make an in-game ticket.

Patch 1.7: