Fix invisibilidad #522
Merged
Fix invisibilidad #522
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #465 y fix #518
Varios cambios acá. Principalmente las validaciones para enviar los personajes invisibles al cliente no eran las mismas en los dos lados que se usan. Queda pendiente reescribirlo mejor esto algún día.
Si un usuario invisible se alejaba de otro usuario, debe borrarse el char en el cliente. Esto no funcionaba.
Faltaba también controlar el caso que un usuario se mueva cerca de otro estando invisible. Es necesario mandar paquetes al cliente acá para que no se quede bloqueado en una posición.
Esto va mergeado con un PR en el cliente que se llama igual. Mergear ambos a la vez ya que hay cambios de paquetes.