Ol' Stinky Posted May 17, 2013 Posted May 17, 2013 I've been mucking around with the level editor, as well as getting the work of others over in the map forum, and figured it was time to see how they play in the "real thing". I'm noticing that the game tends to select one or two maps every tileset, though. However, random is random and all that! I guess I'm asking others if they've noticed the same. It could be that this isn't a problem at all. So: have you guys drawn the same couple of maps repeatedly (for light scouts, at least)? Quote
Gauddlike Posted May 19, 2013 Posted May 19, 2013 Not really related to the potential bud but did you try using the old quickbattle option to test your own maps? It forces the game to load up a specific map, outside of a campaign. If it still works it should allow you to test your own maps (or any other) individually. It means you won't need to play all the way through to battleships to test out your battleship maps and so on. Run the batch file in the xenonauts directory to access it and you can find info on how to point the config file to your maps here. Quote
flashman Posted May 19, 2013 Posted May 19, 2013 (edited) Quick battle is the best way to test maps if you readup how on wiki, though it can be a pain sometimes to get terror sites to load because you have to get the file in the correction type so I bung it in all of them. Also use the level setup text from the wiki if they don't load Otherwise I will remove all tiles except those I want to test and run a game with only the Custom maps. Then I burn through at high speed. Just don't do the two auto pop missions if you removed those maps. To properly cheat use a modified game with all tech unlocked and costs and buld timers reduced so you can create an unstoppable force that bums around the world. Edited May 19, 2013 by flashman Quote
Ol' Stinky Posted May 19, 2013 Author Posted May 19, 2013 Yeah, now use the quickbattle option to test out the maps. Back in 18.4 it'd have a 50/50 chance of CTD for me with a prompt telling me a critical error has occured - I guessed it was archive-related. (I haven't encountered it since Chris let us use 18.5. Bliss.) Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.