Well I was converting the text strings in Someplace Else to a format compatible for the game_text entity. An odd bug with Hammer at the moment is that if you put in more than 127 characters in the "Message Text" field, Hammer will crash.

The text in Someplace Else was much longer than 127 characters, so I opened the .map file and pasted it more than 127 characters and compiled like normal, and it played like normal. But Hammer would always instantly crash when attempting to open .map.

So, technically reverse engineering is impossible unless:
- The bug is fixed in Hammer
- The map is opened in QuArK (but people who decompile aren't likely to use QuArK anyway)
- The decompiler-person actually goes into the .map file and finds the "Over 127 character" thing and deletes it. But like I said, if they decompile, they're not likely to know what to look for anyway, much less know about this bug.

So, they still can decompile the map, they'll just never really know how to open it. But I doubt anyone is really THAT protective of their work.

Either way, you'd still need the textures in your map that you're using. Unless they are mod standard I find it's better to have just a .bsp and not a .bsp and a .wad or more...why make it tougher than necessary?

I just got caught by my own booby traps (!)

Turns out to be a useful (if unorthodox) way of debugging my new code

(Fixed now)