mike/sst/src/xhair.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-BETA2025-11-24T03:23:22+00:00Turn 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.
Pass screen width and height into HudPaint events2025-04-06T19:59:36+00:00Michael Smithmikesmiffy128@gmail.com2025-04-05T15:41:32+00:00urn:sha1:7ac57c976d95bce5a7a98e0f269e4cd3d61f3055
This makes it unnecessary to call hud_screensize in basically
every handler.
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.
Hide custom crosshair in menus/load screens2024-05-27T18:58:46+00:00Michael Smithmikesmiffy128@gmail.com2024-05-27T18:58:46+00:00urn:sha1:a3a7a637811d3e18506d82a72e634cdc978dd2ee
This isn't perfect logic - the standard crosshair has a lot more cases
where it's not displayed - but it's better than nothing and avoids
looking stupid as often.
In the process, also fix the IConVar virtual table being one entry too
small, which somehow wasn't a problem until it led to vtidx_IsInGame
here getting clobbered and causing hard-to-debug crashes. Woopsy!
Add a half-decent custom crosshair2024-01-21T21:01:00+00:00Michael Smithmikesmiffy128@gmail.com2024-01-21T21:01:00+00:00urn:sha1:506f095bcb528468f25a637977efcc408590ae67