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 #1838 [ All Revisions ] [ Back to Issue ]
Summary 0001838: Clientside puffs
Revision 2014-11-21 12:42 by Arco
Description I made my clientside puffs for my custom binary, certain people liked it a lot. Others turned it off. So it's important to be 'toggleable'.

I need input though on if this really should be bound to connection type. This seems like a feature that people will want on without sacrificing connection type. People like me with good connections like seeing the shot come out instantly.

This will further add to our obnoxious spaghetti zdoom code. The additions are relatively straight forward, but it requires syncing up with the server and client. Therefore this most likely should go in the user info.

Maybe I can turn that unlagged byte field that is !!'d into a bitfield where 0x02 indicates clientside puffs? Save on an extra byte we don't need to send... unless you feel its worth sending it as a byte on it's own.
Revision 2014-11-17 20:25 by cobalt
Description I made my clientside puffs for my custom binary, certain people liked it a lot. Others turned it off. So it's important to be 'toggleable'.

I need input though on if this really should be bound to connection type. This seems like a feature that people will want on without sacrificing connection type. People like me with good connections like seeing the shot come out instantly.

This will further add to our obnoxious spaghetti zdoom code. The additions are relatively straight forward, but it requires syncing up with the server and client. Therefore this most likely should go in the user info.

Maybe I can turn that unlagged byte field that is !!'d into a bitfield where 0x02 indicates clientside puffs? Save on an extra byte we don't need to send... unless you feel its worth sending it as a byte on it's own.
Revision 2014-06-16 01:43 by Watermelon
Description I made my clientside puffs for my custom binary, certain people liked it a lot. Others turned it off. So it's important to be 'toggleable'.

I need input though on if this really should be bound to connection type. This seems like a feature that people will want on without sacrificing connection type. People like me with good connections like seeing the shot come out instantly.

This will further add to our obnoxious spaghetti zdoom code. The additions are relatively straight forward, but it requires syncing up with the server and client. Therefore this most likely should go in the user info.

Maybe I can turn that unlagged byte field that is !!'d into a bitfield where 0x02 indicates clientside puffs? Save on an extra byte we don't need to send... unless you feel its worth sending it as a byte on it's own.




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker