vswarte / er-online-summons Goto Github PK

Rework the spawn procedure a bit:

• In case of a client we should request the host to spawn a summon for us.
• In case of a host we should listen for these requests and make the decision on whether or not this is a valid request.
• In case of a host we should spawn the summons and broadcast SummonSpawned to all clients.
• In case of a host we should never handle SummonSpawned messages as these are meant to inform clients of a new summon.
• In case of a client we should never handle SummonSpawned from any other lobby member than the host.

Currently the way Mimic Tears are rendered is very inconsistent, sometimes it will copy the host, sometimes it will copy the any random one of the other players.

There's also this nasty bug where the blob kinda "stays" where it is after the chrins is fully done with its spawn animation.
My best guess is that we need to figure out how it finds the face + character data for the player it's emulating and hook that to feed it the proper owner of the summon.

Currently summons are fixed to following the host. I'll need to hook this and make the AI follow the appropriate player (the summoner).

This protocol should handle the despawn of summons. This involves another request message from the client specifically for despawns and a message to inform clients of the despawn.

One problem with described approach is that hosts can opt not to broadcast the despawn at this point leaving the summon in everyones world except theirs and that of the person requesting the despawn. But I am not sure what to do about this 🤷.

• A client should send a message to request despawn of their summons.
• A client should immediately despawn the summons on their end as the host can deny broadcasting this event.
• A host should handle the despawn request and validate it.
• A host should, if a valid despawn request was sent, despawn the summons and broadcast a message to inform clients of the despawn.
• A client should handle this despawn message and despawn the summons locally.

Currently there's a while loop that polls the steam user pipe availability. Instead it might be beter to move init to a hook of SteamAPI_Init and do mod construction from there.

The location of the SteamAPI_Init can be found by inspecting exported symbols in the steam_api64.dll module. Making for a hook that shouldn't break across version changes.