- summary: The server ending the character's current game context, typically around a fight. Empty; nothing is sent back.
- area: Game.Context
The server ending the character's current game context, typically around a fight. Empty; nothing is sent back.
Kind event · Area Game.Context
Carries nothing. Arrival means: the context the character was in is over.
WHAT TO DO WHEN YOU RECEIVE IT
1. Drop everything scoped to the context: the actors you track on the map and, if you
were fighting, all fight state. The client does the same - it leaves its current
context, which switches that context's services off, and holds no context at all
afterwards.
2. SEND NOTHING BACK. No handler of this message builds a request, on any dumped
build.
3. Send nothing that needs a context until ContextCreationEvent names the next one.
IN A FIGHT IT ALSO ENDS THE FIGHT. Up to 3.4 the client's fight services handled this message themselves: its fight-preparation and fight-battle handlers close the fight locally, and when the fight was still marked as running - no result had arrived - the battle handler logs "Brutal end of fight (no known result)" and finishes it with an empty result. From 3.5 the context service leaves the fight context instead, which switches the fight services off. Read the log text literally: in a normal fight the result comes first and this message only closes the context; on its own, it means the fight was cut short and no result will follow.
IT IS NOT THE ONLY WAY OUT OF A CONTEXT. ContextCreationEvent of the other kind also
leaves the current context, so do not wait for this message before accepting a new
one.
A 3.4 build declares an optional int32 in it; the client never reads it.
When you may send it
- Requires
context_readyinferred
State it changes
- Invalidates
context_readyinferred — the client leaves and drops its current context and holds none until the nextContextCreationEvent - Invalidates
roleplay_contextinferred — the client leaves its current context, the roleplay one included, and holds none until the nextContextCreationEvent
Related messages
- Reply not yet recovered: what makes the server send it is not established here. It is the teardown half of a context switch, and the next context arrives as
ContextCreationEvent; the fight messages around it have no signature.