Rainyan
commented
2 months ago This is clearly better than what we had, but I think it's still slightly off from the original.
For example, comparing the van cap in nt_dawn:
map nt_dawn_ctg
// spawn a bot to the other team
sv_cheats 1; bot_add
// steps:
// 1. make sure you spawn in the outside, so your capzone is inside
// 2. go grab the ghost from the world
cl_showpos 1
// This teleports you just barely outside the capzone range.
// Might still not be quite 100% accurately the actual limit, but it's pretty close:
setpos -350 179.750344 -135; setang 0 -90 0
// This triggers the van cap for original NT:
setpos -350 179.750343 -135; setang 0 -90 0For the remake, this limit is somewhere closer to setpos -350 178.7 -135; setang 0 -90 0 before the cap actually goes in. So I think we're most likely off by 1 unit (Y coord \~179.7 vs \~178.7 in this example) somewhere. Peeking at the disassembly, I think the original implementation calls CEntitySphereQuery for this, but I'm guessing we could just offset our calculation accordingly to get the same behaviour.
Agiel
For parity the distance is calculated in 3D instead of 2D, and the cap zone radius is not halved. Also, a distance less than or equal to the radius should be a cap, not just less than (this caused some annoying off by a frame issues in one of my old plugins 😅).
Fixes #269.