Bug 2758 - goon pounce bug
Status: RESOLVED FIXED
Alias: None
Product: Tremulous
Classification: Unclassified
Component: Misc
Version: unspecified
Hardware: All Windows XP
: P2 normal
Assignee: Tremulous Bugs
QA Contact:
URL:
Depends on:
Blocks: 2783
 
Reported: 2006-06-22 04:03 EDT by gatewarstrekme
Modified: 2007-10-03 05:37:25 EDT
1 user (show)

See Also:


Attachments
client engine toggleconsole stop key down event (326 bytes, patch)
2006-07-04 00:15 EDT, Tony J. White
server side fixs for pounce/lcannon spamming (708 bytes, patch)
2006-07-04 00:18 EDT, Tony J. White
server side fixs for pounce/lcannon spamming (1.12 KB, patch)
2006-07-13 18:24 EDT, Tony J. White
lucifer cannon spam fix (736 bytes, patch)
2006-07-21 14:16 EDT, Tony J. White
goon pounce spam fix (1.61 KB, patch)
2006-07-21 14:18 EDT, Tony J. White
svn802 pounce bug (3.52 KB, patch)
2006-07-25 17:34 EDT, Tony J. White
svn802 pounce bug (4.06 KB, patch)
2006-07-26 11:40 EDT, Tony J. White

Description gatewarstrekme 2006-06-22 04:03:03 EDT
If a player is a goon, and presses to pounce, then, before releasing, opens the console, they pounce at an unbelievable rate. This coaxes incredible speed out of goons and is being exploited.
Comment 1 Norfenstein 2006-07-03 20:34:57 EDT
This bug is probably also responsible for lucifer cannon spam: charge up to the minimum then bring down the console (don't release fire) and you'll fire automatically.

For the goon bringing down the console while charged (keeping secondary fire held throughout) will make you pounce but it doesn't appear to do any damage.
Comment 2 Tony J. White 2006-07-04 00:15:59 EDT
Created attachment 950 [details]
client engine toggleconsole stop key down event


When the client toggles their console all the state of all down keys should be forgotten to prevent cases when a key is apperantly up and down at the same time.

patch is against 755 but applies cleanly to 802
Comment 3 Tony J. White 2006-07-04 00:18:03 EDT
Created attachment 951 [details]
server side fixs for pounce/lcannon spamming


Reset STAT_MISC (pounce charge) once a pounce has been released and force weaponTime after the lucifer cannon has been fired.

Patch is for 755, but applies cleanly to 802.
Comment 4 Tony J. White 2006-07-13 18:24:56 EDT
Created attachment 958 [details]
server side fixs for pounce/lcannon spamming


Uses correct weaponTime setting depending on if it was a primary or secondary luci fire.
Comment 5 Tony J. White 2006-07-19 19:34:42 EDT
The latest patch breaks the ability for goon pounce to do damage.
Comment 6 Tony J. White 2006-07-21 14:16:26 EDT
Created attachment 971 [details]
lucifer cannon spam fix

same fix from last patch minus the goon pounce stuff
Comment 7 Tony J. White 2006-07-21 14:18:00 EDT
Created attachment 972 [details]
goon pounce spam fix

uses stats[ STAT_STATE ] & SS_CHARGING to track if a pounce is in progress and will not let a new pounce start until the previous one has finished regardless of keys.
Comment 8 Tony J. White 2006-07-25 17:34:28 EDT
Created attachment 981 [details]
svn802 pounce bug

this implements a new struct "pmext" to both pmove_t and gclient_t that works essentially the same as playerstate, but does not get transmitted over the network.  It can be used to keep state between the Pmove code and the rest of the game code.

Currently it only has one element "pouncePayload" which was moved from gclient_t.  This frees up stats[ STAT_MISC ] for use in Pmove to fix the pounce bug.
Comment 9 Tony J. White 2006-07-26 11:40:45 EDT
Created attachment 982 [details]
svn802 pounce bug

ugh, forgot to reset pouncePayload properly.  this should be the last patch for this.
Comment 10 Roman "kevlarman" Tetelman 2006-11-16 02:19:11 EST
(In reply to comment #9)
> Created an attachment (id=982) [details]
> svn802 pounce bug
> 
> ugh, forgot to reset pouncePayload properly.  this should be the last patch for
> this.
> 

not quite, the console was fixed, but chat/team chat/target chat will still trigger this bug.
Comment 11 Tim Angus 2007-09-15 20:30:43 EDT
(In reply to comment #10)
> not quite, the console was fixed, but chat/team chat/target chat will still
> trigger this bug.

As I understand it, the actual exploitable bug is fixed already. The problem remaining is really just cosmetic. I've addressed this in r992. Reopen if there are still problems.
Comment 12 Tim Angus 2007-10-03 05:37:25 EDT
See r1024.