Leaderboard

For those who are hungry for updates, thanks for all the kind words and support. As holidays are around the corner, my free-time has been a bit taxed lately as I strike the balance between KotOR things and spending time with my and my fiance's family. (Not to mention keeping up with my real job 😬) However, I did spend some time formalizing some of the various "wishlist" features, as well as other pending investigations within the repository issues view. Most upcoming work on my radar for this project is of the unexciting sort. I want to adjust the way I'm modelling game objects in the patching framework to better reflect the underlying inheritance in the base game (i.e. Functions that take a CSWCObject can accept a CSWCCreature, which is derivative, as valid input, etc). I also want to improve/expand the address database system. Right now, they're being stored in plain-text TOML format, which is fine at the current scale, but as this project has grown, this system is already becoming unwieldy. I'm looking to swap to using SQLIte, such that we can have efficient, live, swappable local databases that we can just dump address data directly out Ghidra into. Finally, kotor 2 reverse engineering just needs more work. Kotor 1 is in a great place, such that if we were only targeting that game, I could really accelerate this project. But since I'm endeavoring to provide a solid framework for both games, some TL&C is required to get kotor 2 at least somewhat up to speed. I likley will be giving DarthOuroboros's GhidraMCP suggestion a shot to see if that can accelerate things more here. As a lot of the work to be done is mostly comparative reverse engineering, which I hope falls into the low-complexity class of problem that AI typically excels at. As always let me know if there are any questions or suggestions! P.S. @ajdrenter Galaxy map stuff would be pretty interesting, I've added an issue for me to investigate that at some point in the future. Thanks for the suggestion!

If it messes with timers, then I imagine anything related to OnHeartbeat events for placeables/modules/user defines would experience the sort of issues described.

Hi @Salk I know what your talking about! The load behavior of a main menu load, a hard load (load game menu in game), an autosave load, and a quick load all have subtle but important differences. This has actually come up in the speedrun world a few times. For example, the effect duration glitch (in which they last a long time) only happens if you have previously loaded a hard save in this session (as that messes up the global timers). There's a variety of other small differences, between these functions; most of which I haven't dug too deeply into. But I'm unsurprised you've run into this before. If you could provide an example of a specific script related issue that performs differently for different loads (to use as a reference point), I'd be happy to mount a bit of an investigation into it when I get the time. As mentioned above, it's a busy time of year so this may be backlogged a bit. I'd also be happy to field any other questions! Thanks, Lane

It's a complete alternative, yes.