lots of systems running in my game. arrows show a dependency. the system or systemset on the pointer-side of the arrow requires that it's run *after* the system or systemset on the origin-side of the arrow.
i'm really surprised how pleasant it is to simulate a full aircraft using the ECS paradigm.
![screenshot of an untested function that is fed 7 arguments, and attempts to return the value contained in argument 6 using pointer arithmetic relative to the base pointer. i have no inline arithmetic for the base pointer, so this is probably the simplest way for now. i wonder if i'm going insane or if this actually has to be done this way. it's hard for me to conceptualize the difference between constant/static and runtime when it comes to assembly, cause it's just so different from system-level languages. i sat there staring at the screen for many minutes before i realized i had to add the m[reg] capability for load. and i can't do arithmetic on that either since it's "runtime". it's hard to explain because i haven't wrapped my head around it.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:umf7io4mm4l2afqbdialeqze/bafkreie4pewcqtvcv5itheunno62bdbkuvdxssdgeydrwedffytja4d2pa)
