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

View Revisions: Issue #4277 [ Back to Issue ]
Summary 0004277: "Hold" state name causes broken behavior
Revision 2024-05-10 15:30 by BinaryCode
Steps To Reproduce Example WAD includes 2 weapons:
1st ignores flags on high ping
2nd is "weaponready skipping the alt/fire state and jumping straight for alt/hold if called from the latter" (probably difficult to explain)

Host a test server and use Clumsy (https://jagt.github.io/clumsy/) to test.
Revision 2024-05-10 16:23 by WaTaKiD
Steps To Reproduce Example WAD includes 2 weapons:
1st ignores flags on high ping
2nd is "weaponready skipping the alt/fire state and jumping straight for alt/hold if called from the latter" (probably difficult to explain)

Host a test server and use Clumsy ('https://jagt.github.io/clumsy/ [^]' ) to test.
Revision 2024-05-10 15:30 by BinaryCode
Description Reporting this bug for someone else.
Revision 2024-05-16 01:19 by Ru5tK1ng
Description The current bug at hand is that weaponready jumps to the incorrect state if called from a hold state or its intentional but undocumented
Revision 2024-05-16 04:00 by unknownna
Steps To Reproduce Example WAD includes 2 weapons:
1st ignores flags on high ping
2nd is "weaponready skipping the alt/fire state and jumping straight for alt/hold if called from the latter" (probably difficult to explain)

Host a test server and use Clumsy ('https://jagt.github.io/clumsy/ [^]' ) to test.

Offline, hold +attack and +altattack in at the same time to reproduce the issue. The broken pistol will not jump to the state that prints "C" on the screen.




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker