Discussion in 'Time Locked Progression Servers' started by Finchy, Jun 30, 2015.
soooo...they're releasing kunark now, and TL is getting a couple hours to get their epics done...gg
Soooo.... about those transfers off ragefire....
Ragefire down yet again. Get your stuff together DBG.
Holy Crap, i just saw 5 cazic thules on track before i crashed....
Yup, was fighting, noticed the chat went bad (Duo boxing) then about 5 min. we pulled. and my spells were working, then CRASH
Well Daybreak? What's the word?
Complete hardware failure with 12 hour rebuild?
30 minute quick fix?
Ragefire down! Loot and scoot Ragefire!
It's those filthy casuals, revolting on the unlock timer lol.
spending my down time making characters with my ragefires mains names on Lockjaw in case i decide to transfer over I can at least keep my names
Edit: happy to report all of them were available
So whats with the massive rollback im down alot of plat and exp?
That rollback is BS. I hit my level maybe 30 minutes before the crash and lost it.
Is some guild exploiting a crash bug to get raid spawns? Does Daybreak know what the issue is?
Lets not bring out the finfoil hats just yet... Maybe the most populated server ever is also the server with the most hardware stress?
Ragefire is remarkably stable given its population. The regular servers routinely suffer from channels crashing, sometimes repeatedly which can last for days. They are also prone to lag spikes, constant lag, and crashes which again can last for days.
As for the rollbacks, unless it is forced by DGC itself they revert you back to your last save point. You even get a message in whichever chat window you have "other" going into whenever you information is saved. So the rollback from a crash can be of wildly different time frames for different people. To force a save point, zone. Many people on Live will gate once a raid is beaten and they get currency and whatever and banner back, if they get any loot gate again and then come back to prevent anything lost from such a crash. It beats the customer server response of feel free to complete the event again once the lock out timer is up.
Separate names with a comma.