aboutsummaryrefslogtreecommitdiff
path: root/Makefile
diff options
context:
space:
mode:
authorfusion32 <marcopuzziello@gmail.com>2026-07-25 09:18:09 -0300
committerfusion32 <marcopuzziello@gmail.com>2026-07-25 09:18:09 -0300
commitdb5050d5dbc0525d05837f728bea52f7954286cc (patch)
tree352e32090c7e6de2babb996238700172e5716534 /Makefile
parent6b5e20e65d05e468dc663189ab302e02c4788c6a (diff)
downloadgame-db5050d5dbc0525d05837f728bea52f7954286cc.tar.gz
game-db5050d5dbc0525d05837f728bea52f7954286cc.zip
adjustment to last commit
Increasing the search radii for `CloseContainer` from (12, 10) to (14, 12) prevented players from exploiting the issue alone but it could still be leveraged when there was another player involved. In this case, you have another 2 SQM on both sides that need to be accounted for, so using (16, 14) should prevent it as well. And it may be a coincidence, but pretty much all other searches use these values, so I'm not sure what to make of it. They might be related?
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions