forked from teamnwah/openmw-tes3coop
[Client] Don't force skill update on cell change
Previously, an attempt by the server to simultaneously change a player's cell and skills (as you'd expect when a player file is loaded) led to: 1) The server sending the cell packet first and the skill packet afterwards 2) The player receiving the cell packet and sending their own skill packet as part of the client's forced skill update 3) The player receiving the skill packet from the server 4) The server receiving the skill packet from the player The result was that, if the player then left the server without sending another skill packet, the server's memory retained the skills the player had sent instead of the skills it had sent to the player. This is the first step in a solution to that situation and similar ones.new-script-api
parent
07d75abdf8
commit
cac4684986
Loading…
Reference in New Issue