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?

1 files changed, 1 insertions, 1 deletions

diff --git a/src/map.hh b/src/map.hh
index bbd77fc..12a4143 100644
--- a/src/map.hh
+++ b/src/map.hh
@@ -13,7 +13,7 @@ enum : uint8 {
 	STATUS_SWAPPED = 2,
 
 	// TODO(fusion): It seems this is only used with the `NONE` entry in the
-	// hash table. I haven't seen it used **yet** but It may have a purpose
+	// hash table. I haven't seen it used **yet** but it may have a purpose
 	// aside from preventing swap outs.
 	STATUS_PERMANENT = 255,
 };