aboutsummaryrefslogtreecommitdiff
path: root/TODO.md
diff options
context:
space:
mode:
authorfusion32 <marcopuzziello@gmail.com>2025-06-25 10:09:17 -0300
committerfusion32 <marcopuzziello@gmail.com>2025-06-25 10:09:17 -0300
commitea319bc2fbef91e3ea062be554b215756648d1d3 (patch)
treeaa26422a754346e9881e5e0b510f78fd4cfe068c /TODO.md
parent8bc2e5dc3a523af471065752a534d20d878c60b0 (diff)
downloadgame-ea319bc2fbef91e3ea062be554b215756648d1d3.tar.gz
game-ea319bc2fbef91e3ea062be554b215756648d1d3.zip
finish `crnonpl.cc`
Diffstat (limited to 'TODO.md')
-rw-r--r--TODO.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/TODO.md b/TODO.md
index 251a0a8..fe5db50 100644
--- a/TODO.md
+++ b/TODO.md
@@ -11,6 +11,7 @@
- The map container uses type id zero but it seems to also be used as a "no type"
id which makes me want to add some `isNone()`, `isNull()`, `isVoid()` check to
`ObjectType` to be used as an alias when pertinent.
+- Make some `TNonplayer` random step function? One version that does a random step and another that does a random step keeping some distance from a certain position.
## Stack allocations
Any functions that use `alloca` or some other form of dynamic stack allocations will cause decompiled functions to be an absolute mess. It usually shows up in the decompiled code as both a size computation like `-(VAR + CONST & 0xfffffff0)`, followed by some assignment. It doesn't make total sense without looking at the disassembly. I've encountered ~30 such computations and expect the functions containing them to be amongt the most challenging/annoying to be properly decompiled.