Zandronum Chat on our Discord Server Get the latest version: 3.2.1
Source Code
My View | View Issues | Change Log | Roadmap | All Projects Issue Support Ranking | Rules | My Account
  

View Revisions: Issue #3469 [ Back to Issue ]
Summary 0003469: Client fires weapon too early after map resets in 3.1
Revision 2018-08-28 02:24 by unknownna
Description The client also fires the weapon too early after map resets. This, like the respawn issue, is very important to have fixed as the first few kills in a duel can make a considerable difference in the game.
Revision 2018-08-28 19:31 by unknownna
Description The client fires the weapon too early after map resets since 3.1. This, like the respawn issue, is very important to have fixed as the first few kills in a duel can make a considerable difference in the game.
Revision 2018-08-28 02:24 by unknownna
Steps To Reproduce changemap_weap_desync.wad

1. zandronum -host -iwad doom2.wad -file changemap_weap_desync.wad +survival 1 +sv_survivalcountdowntime 1
2. Connect a client to the server.
3a. Copy-paste "join;wait 48;+attack;wait 1;-attack" into the console. No rockets will come out.
If that doesn't work, use the bind in step 3b instead.
3b. Copy-paste "join;wait 49;+attack;wait 1;-attack" into the console.
Revision 2018-08-28 19:31 by unknownna
Steps To Reproduce changemap_weap_desync.wad

1. zandronum -host -iwad doom2.wad -file changemap_weap_desync.wad +survival 1 +sv_survivalcountdowntime 1
2. Connect a client to the server. No ping emulation should be needed.
3a. Copy-paste "join;wait 48;+attack;wait 1;-attack" into the console. No rockets will come out.
If that doesn't work, use the bind in step 3b instead.
3b. Copy-paste "join;wait 49;+attack;wait 1;-attack" into the console.
4. Spectate and repeat step 3a or 3b. It should desync rather quickly.




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker