Exit Flags

I looked into this, but don't think I'll be taking it on at the moment. Although I fully agree with the fact that how exit flags are saved/loaded is absolutely ridiculous, the fact is with the inclusion of EX_HIDDEN to tbaMUD the saving/loading system is even more ridiculous. Thus there would be potentially 2 ways to fix this:

1) The "Bad Way": This would involve having to find some method of backwards compatibility with the current system as to not potentially corrupt world files.
2) The "Right Way": This would be just ditching the current system and using a more "De-Stupid" implementation and then provide some sort of script or direction on how to alter your world files to suit it.

Both these ways involve a large percentage of chance of human error, which then results in me having to spend an exorbitant amount of time on the forum answering the same questions over and over again. (Lesson Learned)

That said, taking a look over the patch you provided, I see no reason to concern yourself with write_to_q, or 128 bit arrays, or anything upcoming in future tbaMUD releases. Unless you are d/ling additional tbaMUD world files there is little reason to keep the backport code within your MUD current, which would seem to be the most confusing transition.

Looks good, only thing worth mentioning is that there should be no reason to swap the CLOSED & LOCKED, as that appears to just be a simple hack by the original snippet creator for the purpose of back-porting older world files.

Good job

Anyone still have the attachment destupid2.txt that WhiskyTest made? We seem to have lost it during an upgrade or server move.

Thanks, added to the Downloads->tbamud->patches as well.