.qc (dot qc) - the group for quake c coders of all denominations. If you make quake one mods and write code in quake c, join our group! I'll try to answer any quake c questions - please post your inquiry in the forums...
|Axe frames bug & variable bounds checks||Locked|
numbersix quake-c coder++
|Dec 26 2015 Anchor|
I came across this here: Quakeone.com
How does it happen?
If you dont know exactly how this works, replicating it is darn near impossible. Most players have likely never seen this.
1. Select axe
When the fire frames finish, frames will continue to increment as long as you run without stopping:
* The easiest way to determine walkframe is to put a console print in the code for player_stand1.
Why does this happen?
When any axe fire frame set finishes:
Points self.think to "player_run" found as "void() player_run" in players.qc.
If frames were incrementing normally 6 would follow 5 and this would catch it.
This test fails for any value not 6.
Make that change and the axe frame bug will never rear its head.
Edited by: numbersix
Only registered members can share their thoughts. So come on! Join the community today (totally free - or sign in with your social account on the right) and join in the conversation.