Back to News

fix: dispatch DataAction.Revive by ReviveType, reject non-classic options

•By Moh•changelogdawn
Changelog

- Add ReviveType enum (Normal/Here/Random/Immediate/Refine) matching the five values the 6609 client sends in MsgAction(94).Data1 from the death dialog

- WorldClient.OnReviveRequest dispatches by ReviveType: Normal teleports to map spawn (delegates to existing Revive(here:false)), the other four are rejected with a system whisper since they don't exist on a classic server

- Stop collapsing Data1 to a bool in MsgAction.cs — the previous Revive(Data1 != 0) honored Revive Here / Random / Immediate / Refine clicks because any non-zero value mapped to here:true, leaving the player at their corpse without going through any of the gating those features expect

- Internal Revive(bool here) is untouched so all server-triggered revives (events, magic, /revive command, Reviver creature) keep working