no, dude, don't turn right back around and pick your shit right back up, stop

(None of this should invalidate any of YOUR existing ghosts, because none of them use these obvious cheats like, say, setting kartdebugitem 2.)

It's not disruptive, but it looks a bit goofy since the "Map is now x" print is no longer directly printed either, so it's the only thing sticking around in the console :V

yes I'm an idiot for rushing things like this

No hasslope

See merge request STJr/SRB2!312

"PlayerQuit" Lua Hook

See merge request STJr/SRB2!127

Lua support for slopes

See merge request STJr/SRB2!307

Winsock error handling fixes

See merge request STJr/SRB2!303

General Lua improvements

See merge request KartKrew/Kart!86

Decided that being able to set a string and then have it return an integer when retrieving would ultimately be confusing, so let's just let the user handle the string functions.

Staff Attack improvements

See merge request KartKrew/Kart!79

Small Lua hud library improvements

See merge request KartKrew/Kart!73

Should probably be ported to vanilla

I thought about just exposing R_TextureNumForName and leaving it to the user, since that makes it obvious that this is still an integer field, but I also liked being able to just specify a string and be done with it. I'm not picky either way.

More optional fields, more careful eye placed on return values and other checks

Merge pull request #321 from GoldenTails/next-add-a-lua-variable-to-ultimate-mode-so-people-can-check-it

Add Lua Ultimate Mode global variable so people can use it.

# Conflicts:
#   src/lua_hudlib.c

* Make the maximum number of staff ghosts 99 instead of 100. It's a minor thing, and insignificant in the grand scheme of things, but it fixes a bugbear I haven't been able to get out of my head since originally starting to maintain this code. (In the case of 100, it'd do S00, which'd have some fucky effects on ordering. If we WANTED to start with S00, we shoulda used that slot in the first place.)