Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Respawn - Rejip sometimes not working #64

Open
7 of 12 tasks
Tapawingo opened this issue Jan 6, 2024 · 1 comment
Open
7 of 12 tasks

Respawn - Rejip sometimes not working #64

Tapawingo opened this issue Jan 6, 2024 · 1 comment
Labels
kind/bug Something isn't working as intended
Milestone

Comments

@Tapawingo
Copy link
Member

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING

  • If I delete this entire template or parts of it and go my own path, the team may close my issue without further explanation or engagement.
  • If I list multiple bugs/concerns in this one issue, the team may close my issue without further explanation or engagement.
  • If I write an issue that has duplicates, the team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
  • If I leave the title incomplete when filing the issue, the team may close my issue without further explanation or engagement.
  • If I file something completely blank in the body, the team may close my issue without further explanation or engagement.
  • If I file an issue without collecting logs (RPT file, etc...), the team may close my issue without further explanation or engagement.

Version

v2.1.1-dev

Description

Sometimes when players rejip their pre-disconnected state is not invoked.

Steps to reproduce

  1. Go back to lobby after Safestart has been disabled
  2. Join as a new unit
  3. Observe as your old unit's state is not reloaded

Expected behavior

The new player unit should be loaded into the same state as the old unit. That being they should receive the gear, lives, stance and position data.

Where did the issue occur?

  • Dedicated
  • Self-Hosted Multiplayer
  • Singleplayer
  • Editor (Singleplayer)
  • Editor (Multiplayer)
  • Editor

Log Files

No response

Mission Files

No response

Additional Context

No response

Screenshots

No response

@Tapawingo Tapawingo added the kind/bug Something isn't working as intended label Jan 6, 2024
@Tapawingo Tapawingo added this to the v2.2.0 milestone Jan 6, 2024
@Tapawingo
Copy link
Member Author

This issue is caused by how the pre-discon state is handled. If you don't disconnect entirely from the server but only go back to lobby the unit state won't be saved as the "handleDisconnects" event won't be triggered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working as intended
Projects
None yet
Development

No branches or pull requests

1 participant