tibia/game/src, branch masterTibia 7.7 decompiled game serverhttps://kaplar.net/tibia/game/atom?h=master2026-08-01T16:03:27Zone last adjustment to `CloseContainer` (hopefully?)2026-08-01T16:03:27Zfusion32marcopuzziello@gmail.com2026-08-01T15:54:04Zurn:sha1:3fd1bdbaaffc6582943e3c9b3c28c20976fcb2ad
I've also reverted the search range of `NotifyTrades` to
(12, 10), because it's just not related to `CloseContainer`.
It is called before objects are moved, and on the case the
object is split, it is called on the remaining part.
adjustment to last commit2026-07-25T12:18:09Zfusion32marcopuzziello@gmail.com2026-07-25T12:18:09Zurn:sha1:db5050d5dbc0525d05837f728bea52f7954286cc
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?
adjust search radii for `NotifyTrades` and `CloseContainer`2026-07-10T03:27:08Zfusion32marcopuzziello@gmail.com2026-07-10T03:27:08Zurn:sha1:6b5e20e65d05e468dc663189ab302e02c4788c6a
This fixes an issue, also present on the original binary, where
containers thrown from Z=0 to the edge of the screen at Z=7 would
remain open to surrounding players. The previous 12-10 radii were
missing 2 SQM each when considering the maximum offset between
floors.
minor tweak to script recursion depth checks2026-06-21T00:50:45Zfusion32marcopuzziello@gmail.com2026-06-21T00:49:39Zurn:sha1:386fa9b8078a1b32187dfcbfc2a0ed7543e16346fix player state desync on login (#59)2026-06-01T04:54:15Zfusion32marcopuzziello@gmail.com2026-06-01T04:52:28Zurn:sha1:a8d26b6ce32066812fd46ac88804048d38218db3fix issues and warnings when compiling with glibc < 2.32 (#57, #58)2026-05-29T02:56:29Zfusion32marcopuzziello@gmail.com2026-05-29T02:56:29Zurn:sha1:e2ba7cd29617ae05087ad3d25c55a2eb8ce607a3
This also fixes some inconsistencies such as mixing both strerror
and strerrordesc_np, and possible formatting issues.
minor fix to monster targeting logic2026-05-25T21:19:39Zfusion32marcopuzziello@gmail.com2026-05-25T21:19:39Zurn:sha1:d1c4dce3be82aa7e50ddb5b43f15ecc00a16f985fix issues with TMonster constructor + Search functions + UH formula2026-05-09T15:40:41Zfusion32marcopuzziello@gmail.com2026-05-09T15:24:34Zurn:sha1:54c2169ec9a99e34e1270e43e9fd1fccd3d2a824
The issue with the TMonster constructor was obvious, but the others
were slightly different from the original.
fix issue with CUMULATIVE + THROW loot (#56)2026-05-06T00:54:32Zfusion32marcopuzziello@gmail.com2026-05-06T00:54:32Zurn:sha1:7beaa081de8aedd28f4c7ce717bcfbd2b09230d3small change to monster talking2026-04-16T10:34:02Zfusion32marcopuzziello@gmail.com2026-04-16T10:21:23Zurn:sha1:a9f70ed1f12ac451f28ae82c270c74b31bd764d6
Monsters will prefix their lines with "#Y" when they're supposed
to yell. The minotaur mage from the leaked files uses a "#W" prefix
which is either a mistake or some removed feature? Either way, it
wouldn't be a problem with the original binary because it would only
check for a leading "#" before removing a three character prefix.