@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

@KS @trysdyn This is somehow MORE FUCKED than I thought

Like I can sort of understand it if it's like a community thing where people refuse to adhere to good practices, but no, the original devs just created a cursed problem from the start? What

@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