Its because the SDK documentation is a little misleading. You can't add any extra actual states (as in; you can't add any new bits to pass over, you can still make as many kbutton_t's as you want though.) its capped at 16 bit, and theres no way to increase it without modifying the netcode in the engine.
You'll have to replace IN_ALT1, or the other unused flag that I discovered the other day; IN_RUN So if you rename IN_RUN to IN_ATTACK3, it should work. And you'll be able to use IN_ATTACK3 elsewhere on the server/client. -omega Frontline Force - http://www.flfmod.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Thornhill Sent: February 26, 2003 5:35 PM To: [EMAIL PROTECTED] Subject: [hlcoders] Additional Weapon Functions So I've been trying this for a while, using Michael Shimmins tutorial (http://hlpp.telefragged.com/tuts/multi-fire-modes.htm) and have thus far been unable to get it to work it to work. I gave up on it before when Michael himself was helping me with it and now have decided to tackle it again. It seems that the the code gets stuck in the client.dll, in input.cpp at the following stick of code: if (in_attack3.state & 3) { bits |= IN_ATTACK3; } I threw an alert in there and it seemed to loop for a few minutes, and then stopped. Anyone know what might be cause it, or if there's a better way to be doing this than Michael suggests? -Jeff _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
