| View previous topic :: View next topic |
| Author |
Message |
Fresco Grandmaster Cheater
Reputation: 4
Joined: 07 Nov 2010 Posts: 600
|
Posted: Fri Apr 03, 2015 12:54 pm Post subject: NoClip Cheat Code ( Disable collision detection ) |
|
|
This game does not have a developer-console.
It's a First Person Shooter.
In general, how would you disable ( nop ) collision detection ?
NoClip = Pass trough walls and other objects while your avatar ( i.e. the character you're playing as ) is not affected by gravity.
I already have the NoGravity part implemented but I have no idea what to look for collision detection.
The NoGravity part was easy: just find the address of your players Z position, find out the code that constantly decreases it ( gravity ), make sure it doesn't write to any other addresses and nop it. _________________
... Fresco |
|
| Back to top |
|
 |
atom0s Moderator
Reputation: 205
Joined: 25 Jan 2006 Posts: 8587 Location: 127.0.0.1
|
Posted: Fri Apr 03, 2015 1:26 pm Post subject: |
|
|
Use your X/Y coords for no-clip stuff. Find what writes to them then run against walls that block you and such and determine where the checks are that way for the boundaries. _________________
- Retired. |
|
| Back to top |
|
 |
Fresco Grandmaster Cheater
Reputation: 4
Joined: 07 Nov 2010 Posts: 600
|
Posted: Sat Apr 04, 2015 1:26 pm Post subject: |
|
|
Already tried that. Doesn't work.
I get a couple of codes, one what writes to X/Y coordinates when i press the movement keys, one that writes while in the air ( inertia / momentum / etc... ) other two that i have no idea what they are doing, one that gets executed just once when I hit the wall.
I tried nopping them all, all together and one by one, but none allowed me to pass trough walls.
Any other ideas ? _________________
... Fresco |
|
| Back to top |
|
 |
Zanzer I post too much
Reputation: 126
Joined: 09 Jun 2013 Posts: 3278
|
Posted: Sat Apr 04, 2015 1:42 pm Post subject: |
|
|
It's not going to be as simple as NOP'ing the value.
You need to find where it compares that coordinate with the object's boundaries and says yay or nay.
Maybe try this:
Stand someplace out in the open and save all of your coordinates.
Instead of NOP'ing, hardcode those coordinates into the instruction (don't update the address).
So if the instruction is movss xmm0,[eax], you can create a custom variable and change it to movss xmm0,[myvar].
Try that at each of the instructions. |
|
| Back to top |
|
 |
|