Mods are loaded according to the usual hierarchy when testing a map from the editor.  The only thing to be aware of is that the editor's test function will save the map as "editorTemp.map" in the game's root, so any properties you've set for your map in defs/mapInfo.txt won't apply.  You can either manually save and load your map with the correct name and path instead of using the test function, or temporarily change your mapInfo.txt to point to "editorTemp.map" while working on your map.

As for cheats, I'd just bind their console commands, either to one key to enable them all in one press, or to their own keys so they can be easily toggled individually.  For example, "fly" and/or "noclip" are pretty handy to have on their own keys for quickly getting around a map, then switching back to normal movement.

It looks really fun 

.

More pictures of my little project because why not?








This area was pretty dope to work with.


And here's where I need to continue building.

Also, a short video I just put together.

Hope to play your map Coyote should be fun
 

It looks like that model doesn't have any ray trace detection on it at all, I never used that model yet. But yeah its going to happen on that model models/city_temple_large04.bin.

Gj sticking it out and putting them there, I assumed since you're new to it xD I think I have seen this before on a different model but its definitely more rare, not a common thing.

Honestly, this doesn't compare to the kind of shit I put up with when I vector anything on inkscape, now that's torture.

This is how I feel about sectoring.

Always be sure to turn ray trace on xD

Pics look nice, good job can't wait to try it out.

That's the thing, ray trace WAS on when I took that screenshot as well as when I built the sectors for the building.