Kaito / Katie Sinclaire @KS@is.a.qute.dog

@maples *headpats bnnuy*

@maples woof!

@socks @trysdyn when that doc was originally written it made a little more sense, as there was no concept of "creating an .apworld file" -- AP couldn't add additional worlds at runtime, to run a custom world at all either you'd be running from someone else's source directory or from a build that someone else compiled with that world in place

but it makes no sense to continue to encourage that behavior now and yet they still do so despite how many problems it causes

@socks @trysdyn yes, this is specified directly in its docs: https://github.com/ArchipelagoMW/Archipelago/blob/main/docs/adding%20games.md#world

of course, "for each new world fork the main AP repository" results in the obvious problem of "you can only make one fork", which people immediately worked around with "just make another branch!"

this completely breaks searching through code, and makes managing releases a nightmare, and yet still here we are

@socks @trysdyn it is not just common, this is the *preferred workflow* that AP tries to push people to use

@exa leap minutes!

@BestGirlGrace which is to say yes, doom is much more likely to keep its stable 35fps

back when i worked on the engine keeping software rendering running at a playable framerate was sometimes a chore, and i can't imagine it's gotten any easier in the time since!

@BestGirlGrace it's not the doom engine anymore, there's so much extra stuff stapled onto it that it's about like calling goldsrc quake