"Server Fixes: Login Crash, Text Bug & Combat Validation"
Server Update
Fixed: login server crash after a party disconnect
If the server dropped everyone at once recently, this was why. We pulled it out of a crash dump.
What was happening
You disconnect while in a party → your session is parked for ~90s so you can reconnect straight back into it.
If you were kicked from, or left, that party during those 90 seconds, the parked session got freed — but the server still had it listed as the owner of your account.
The next time that account logged in, the server tried to send the "you're already logged in elsewhere" notice to a session that no longer existed → crash, and everyone got dropped.
What changed
A parked session is now shut down properly when its party seat is released, instead of being freed while still registered. Also fixed the ordering that let this run at the wrong time during a party disband.
No client download needed — server-side only.
Patch Notes — Text Fix
Fixed
Removed the stray
Y110204label that was floating over scenery in Asgard (stones, clouds, castle pieces, the station platforms and the bridge). Those objects are meant to be unnamed — they were showing a broken text entry instead.The same broken entry was leaking into skill and buff tooltips, where unnamed buffs displayed
Y110204in place of a blank name. Those now read correctly.Restored a line of quest dialogue that had been silently missing from the game as a side effect of the same issue.
Under the hood
A single row in the game's text table had an empty value, and the client's text loader mis-read it — swallowing the next entry and turning the "no name" placeholder into garbage. Both the data and the loader have been fixed, so an empty text entry can't corrupt its neighbour again.
No action needed on your end — just grab the latest patch.
Combat Update
Server-side combat validation has been improved. A few small things you may notice:
A swing can miss if your target moves out of reach as the blow lands.
A skill will refuse to cast if your target is out of range — and costs you no HP/MP/ST.
Your client already worked this way; the server now agrees. Normal play is unaffected.
If a legitimate attack is ever refused at proper range, please report it — that's a bug and we want to hear about it.
As always: irregular client activity is logged, and repeated offences lead to removal from the server.