diff options
| author | fusion32 <marcopuzziello@gmail.com> | 2026-07-25 09:18:09 -0300 |
|---|---|---|
| committer | fusion32 <marcopuzziello@gmail.com> | 2026-07-25 09:18:09 -0300 |
| commit | db5050d5dbc0525d05837f728bea52f7954286cc (patch) | |
| tree | 352e32090c7e6de2babb996238700172e5716534 /src/query.cc | |
| parent | 6b5e20e65d05e468dc663189ab302e02c4788c6a (diff) | |
| download | game-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 'src/query.cc')
0 files changed, 0 insertions, 0 deletions