Rain

--------------------------------------------------------------- TBC QUICK START GUIDE - HOW TO CONNECT --------------------------------------------------------------- Elysium Project's upcoming "The Burning Crusade" server is a brand new realm provided by the Elysium team that will feature WoW's second expansion in its entirety . The game will be hosted on a new realm with a copy of the original vanilla database and characters will be available to play immediately. A new client will be required to access the new realm. No, this doesn't mean the current vanilla realms will "convert" to TBC. That wont happen. If you are unsure about how to connect to the new realm, please follow the below instructions. How to connect: 1: Since TBC does not run on the 1.12.1 client, we will need the 2.4.3 client. Download a client from this website https://www.dkpminus.com/blog/wow-2-4-3-download/. (Torrent is recomended) 2: Once installed, navigate to your realmlist.wtf file, disable "read only" mode in the properties, and replace the existing text with set realmlist logon.elysium-project.org 3: Log in and enter the realm selection screen. Here you will see all the realms hosted on the login server. If you cannot see the realm, be sure you are on the correct tab on the bottom. 4: Log in and play! Note: you must already have an account with Elysium to access the realm. If you have not yet signed up, you can easily do so here https://elysium-project.org/ Remember, TBC requires new addons. Addons designed for 1.12.1 will not work with the TBC client. If you experience crashes, please try downloading a new client. Big thanks to Ziggy for putting this guide together!

And you'll see this exact thing happening in classic. Sorry - we can't protect against game mechanics.

Great to hear 🙂

Hi there. It's because you transferred the character from another realm. This is to avoid selling transferred chars for money. Thanks! Rain

Hi there - no there is no system setup like you mentioned. The only potential issue could be related to an addon you're all using, or for some reason, your WDB cache folder had to be cleared. This is the first I'm hearing of the issue since we started a few years ago. If it happens again please take a video and let me know. Rain

Hmm - it seems it was disconnected from your account upon the merge, or, your account itself wasn't brought over. I've restored the character to your current account, Scorv. Enjoy!

Hi there. When you log in - what account name are you using?

Greetings friends, Nighthaven & Elysium’s past year and a half has been amazing. With Crogge & Shenna leaving the project and new ownership at Elysium for the past 4 months, we have seen some incredible turn around. Nighthaven has just under 2.5 million characters, and almost 1.1 MILLION accounts. Many of you have reached out over the past few months for information on our upcoming Burning Crusade expansion realm. The support has been phenomenal! The hype is real between both our wonderful community, and our staff. We have had countless hours of testing from our QA staff and Nighthaven guilds in preparation for this launch. We certainly would not be where we are now without that dedication. When we decided to start TBC development, we had one goal in mind: Be the best. So, what does that mean to us? Flawless day 1 launch (Anyone who follows other servers has seen how rough their launches have been the past few months) Realm/server capability of handling over 10k connections 95%+ Quest completion 100% Dungeon and raid completion Dark Portal Event Fully Blizzlike experience No custom content Blizzlike class and gameplay mechanics Ability to transition your characters seamlessly from Nighthaven to TBC 100% working arenas and battlegrounds Given these high standards we’ve set for ourselves, we have pushed hard to have everything complete by end of Quarter 1 2019 (end of March). This, unfortunately, is no longer a viable date. We have had some developer IRL issues the past 2 months that saw our main devs go very part time until their lives were sorted. We’ve hired on new people, but it’s a difficult process to find people who are as dedicated to this project as we are. That being said, we have recently gained access to some new developers who will be coming on board to assist us in the bulk of what’s remaining (quests and database related issues). These final fixes aren’t difficult - they are simply time consuming. So, we’re going to push back our TBC release to end of Q2 2019 - released before the summer! Obviously we don’t want to do this, and I would love to launch TODAY - but it’s just not complete, and I don’t think its fair to offer a product that isn’t going to perform to the high standard we set for ourselves. That brings me to my next announcement … Our thought process has gone something along the lines of “Well, we’re in 1.12 on Nighthaven, we’re losing players due to no end game content, and we have no choice but to delay TBC. What’s the solution?” Then … a booming voice came, seemingly out of nowhere, like SIL himself had entered our voice chat: “FRESH”. By the grace of SIL, it was decided. Lets launch a Fresh Vanilla PVP realm for our community to race to 60, start some new classes, experience FRESH content, incorporate some players from other servers that are closing, form new guilds and new friendships - and once TBC launches, allow the transfer to TBC from BOTH realms if they choose - regardless of patch progression. “But what about my Nighthaven character? I’ve worked so hard!” - Yes. We know. We 100% agree, and we don’t want you to lose that progress. It will be completely transferrable to TBC upon its launch. Nighthaven will stay online, of course. Fresh Realm Details: Fast Paced Vanilla (Same patch progression as NH) PVP Launch date: Saturday, March 30th (Mark your calendars!) Name: TBD (Likely we’ll have a player contest to name it!) Elysium/Nostalrius core Monthly PVP Tournaments PVP Battleground Optimizations Transfer to TBC Expansion Realm During Nighthaven’s infancy, we had some issues with mount costs, and world bosses. We want to stress to everyone that those issues have been fixed and won’t be altered at any time by the staff. Yes, we realize Classic is launching sometime in the “summer”. We intend to be in TBC at that time, and anticipate people will still want to play for free, on our truly classic server - not Activision’s business model classic. Time will tell! I know a lot of you will be disappointed with the TBC delay - but lets keep our chin up, keep playing the game we love, and leave it up to me to whip the devs into shape. Thanks all! Rain Administrator, Elysium Project

There is a fix for this somewhere on our github. Please search for it. https://github.com/elysium-project/bug-tracker/issues We don't support addons.

This also needs more context. I don't know what I'm looking at with your screenshot. Is this on our TBC beta realm? Where is this exactly?

Hi there. If you played on Anathema with that character, it will be restored (hopefully) in January! However if you played on Elysium PVP or Darrowshire, it has already been merged into Nighthaven and should be accessible! Rain

Did you try deleting the items in your backpack related with the quest before accepting the quest again?

They should be there! Sometimes they get taken and the respawn rate is variable.

Hi all, After implementing the latest evasion mechanic changes, our wonderful devs have now begun the uphill battle of cleaning up our spell resist code and making it as Blizzlike as possible. This will be a fundamental change to our code, and its important to get feedback and any additional information/references from players. Please take a look at the GitHub post below: https://github.com/elysium-project/classic-bug-tracker/issues/1002 We are also very interested in any evidence you have on what boss spell resist levels should be. If you have input or suggestions, please make sure to provide references and as much information as possible to backup any claims. Thanks everyone!

Hi there. I would suggest abandoning the quest, deleting your WDB Folder, and picking it up again. The quest is confirmed as fixed.