mike/sst/src/kvsys.c, branch v0.18-BETASource Speedrun Tools: practice tools and handy features for Source Engine gameshttps://qdb.woz.blue/mike/sst/atom?h=v0.18-BETA2026-02-16T19:11:24+00:00Move to static trampolines and type-safe hooks2026-02-16T19:11:24+00:00Michael Smithmikesmiffy128@gmail.com2025-12-26T23:12:11+00:00urn:sha1:af370088fc178996a46ee508aaa1a2c46318bbf2
For some reason the DLL got a tiny little bit bigger again but that's
fine. This will make orig_ calls more efficient in the inline case, and
also make it harder to screw up and hook the wrong thing by mistake.
Self-explanatory-ish, apart from the fact it's a fairly large API change
of course. And it relies on some more bonkers assembler directive
hackery.
But it works!
The only complaint one might have is that the featsetup functions no
longer take an explicit string which occasionally yields slightly less
perfect error messages, but I've decided this isn't really a problem and
makes the API nicer to use. It's a tradeoff, innit.
Turn x86 stuff into a chunklet to help out SPT2025-11-24T03:23:22+00:00Michael Smithmikesmiffy128@gmail.com2025-11-24T03:19:49+00:00urn:sha1:508878ff0a9e4cd8528727c41819bc2d70b33dd0
Quick unused header cleanup pass while we're at it.
Add type-safety to virtual calls and accessors2025-04-17T19:02:18+00:00Michael Smithmikesmiffy128@gmail.com2025-04-17T00:39:10+00:00urn:sha1:8a669bc96ffdb9d0f6f54e464da11e3375c80a55
This probably should have been the design from the start.
It's still possible to use void pointers, and this is done in a couple
of places for simplicity, but wherever possible, we have actual structs
for things now.
Additionally, in places where vtables are fiddled with, e.g. vtable
hooks, we have actual struct definitions with vtable pointers so there's
need for pointer-casting horror.
Remove years from copyright headers2025-04-07T20:31:32+00:00Michael Smithmikesmiffy128@gmail.com2025-04-07T20:31:32+00:00urn:sha1:58b495650f7613cdebfe78fff9de2b99556f1998
They're legally unnecessary as far as I know, and kind of annoying to
maintain on a long-term basis.
This was done with the consent of all 3 other contributors, in case
anyone was wondering.
Use C23 void-argument-free prototypes2025-04-06T15:41:13+00:00Michael Smithmikesmiffy128@gmail.com2025-03-10T20:37:28+00:00urn:sha1:daa55cade14146f04814cf8a7ad2028becf4db66
In the future we can also consider moving to {} instead of {0} for
initialisers, but my old Clang (16) doesn't support this, so it might be
wise to wait longer on that one so people don't need too bleeding-edge
of a compiler just to build this thing.
Rewrite and redesign codegen and feature system2025-04-06T15:41:13+00:00Michael Smithmikesmiffy128@gmail.com2025-03-10T02:37:19+00:00urn:sha1:244fea664121acf12871ab5858a5fe95a2606b52
Also switch to somewhat proper C23 flags while we're at it.
This is a huge change. It took me forever, in between being really busy.
Sorry about that. But the good news is I'm now free to start integrating
the various patches that have accumulated since last release. Well, at
least in between still being really busy. Gotta manage expectations.
The main benefit of introducing GAMESPECIFIC() is that features
that don't apply to a particular game no longer show up *at all*, and
less time is wasted on init. It also enables a cool optimisation wherein
unnecessary REQUIRE_GAMEDATA() checks can elided at compile time
whenever the gamedata is known up-front to always exist in supported
games.
The DEF_FEAT_CVAR macro family meanwhile makes it easier to manage the
lifecycle of cvars/ccmds, with less manual registering, unhiding and
such.
Originally I was going to try and just hack these features into the
existing codegen abomination, but it just got too terrible. This rewrite
should make it easier to continue tweaking codegen behaviour in future.
It also has slightly better error messages.
Revise syntax macros and add a ton of branch hints2024-08-23T19:37:37+00:00Michael Smithmikesmiffy128@gmail.com2024-08-03T22:40:31+00:00urn:sha1:83da606072ce272eb053d4e1497d77e647cfecae
My new programming style is branch hints. All non-confusing branches
must be hinted when I can be bothered. It's faster, sometimes, maybe.
Also, start trying to use more signed sizes in at least some of the
places where it makes sense. Unsigned sizes are surprisingly
error-prone!
Deal with the stupid NVDTOR situation2024-05-21T20:25:19+00:00Michael Smithmikesmiffy128@gmail.com2024-05-21T20:25:19+00:00urn:sha1:29389a446859d0d92145ecb395a3b4bff2e0f8be
Bill suggested using abi.h for this. Not sure if it's 100% ideal to need
to pull in the whole header for this one macro but it's arguably better
than most alternatives and definitely better than just continuing to
duplicate it ad nauseam.
Fix compatibility with latest L4D2 update2024-05-21T20:09:44+00:00Willian Henriquewsimanbrazil@yahoo.com.br2024-05-19T20:14:55+00:00urn:sha1:2d0ac38fa0e023d29b32a867240df7fc38c5afaaPrune some comments and tidy up other minor things2023-06-10T15:51:02+00:00Michael Smithmikesmiffy128@gmail.com2023-06-10T15:44:19+00:00urn:sha1:1c4318331663b152b0b298bd2c9e5c971506a86b