FAQ
Search
If you use Linux you should be familiar with Makefiles. They just collect console-commands and check if something has to be done.
i.e. when you map you change your .map-file.
you can then do a
- Code: Select all
make vis
to compile the map with bps and vis.
then you can do a
- Code: Select all
make pk3 install
to pack everything up (automatically) and symlink it into your urban-terror-directory.
if you now do a
- Code: Select all
make light
make registers that you already have an up2date vis-file (map & bsp hasnt changed) and only compiles the light.
i extended it a little bit and included rambetters surface-sound-generator.
now i just map and i occasionally do a
- Code: Select all
make light surface pk3 install deploy
light -> compile bsp, vis, light
surface -> add surface-sounds from given file
pk3 -> package everything
install -> link it correctly
deploy -> upload it to my server
i have still room to expand ..
im planning a 'test' and 'testserver' command (launching urt with the map loaded either locally or connected to my server) and a 'changemap'-command doing a 'rcon devmap ut4_mymap_dev' on my server thus reloading.
i can then just do it all in 1 command and some time later my urt pops up and connects to my server.
No other manual steps required, thus no hassle.
best is: it copies your map before compiling so you can keep on working on your map while its compiling. Compilation is niced with nice-lvl of 20 so you can even play UrT while you compile.
It also supports NuLL's multimapper-diff/merge-tool for coorperative mapping, although this has some limitations. But when you talk on TS (or similar) and you dont interfere with others parts of the map you can map coorperatively quite well.
Im going to pack that stuff and write a little tutorial on how to use it, if someones interested.
