![]() Prvm_global : prints value of a specified global variable in the selected VM (server, client, menu) Prvm_edictwatchpoint : marks an entity field as watchpoint (when this is executed, a stack trace is printed) to actually halt and investigate state, combine this with a gdb breakpoint on PRVM_Breakpoint, or with prvm_breakpointdump run with just progs name to clear watchpoint Prvm_edictset : changes value of a specified property of a specified entity in the selected VM (server, client, menu) Prvm_edicts : prints all data about all entities in the selected VM (server, client, menu) Prvm_edictget : retrieves the value of a specified property of a specified entity in the selected VM (server, client menu) into a cvar or to the console Prvm_edict : print all data about an entity number in the selected VM (server, client, menu) Prvm_breakpoint : marks a statement or function as breakpoint (when this is executed, a stack trace is printed) to actually halt and investigate state, combine this with a gdb breakpoint on PRVM_Breakpoint, or with prvm_breakpointdump run with just progs name to clear breakpoint Note that sv_cheats 1 prevents bots from spawning in the campaign (should you decide to put it in your autoexec.cfg and later wonder why the campaign is broken). With sv_cheats 1 (takes effect next match), you can drag them around (default key V or 'drag object' in menu). You can prevent bots from firing with bot_nofire 1 or stop them completely with bot_cmd * pause (unstop them with bot_cmd * continue). +cl_allow_uid2name 0 avoids an annoying popup.+name tester avoids the nick selection dialog.you can set any cvar or run any command on start with +cvar_name value.use -userdir (e.g./all run -userdir ~/.xonotic-testing +name tester +cl_allow_uid2name 0) to get a clean config (if you delete the dir before each use).use -sessionid (e.g./all run -sessionid testing) to keep your config.If you need 2 players for debugging, you can launch another client locally: You can draw text anywhere on the map using debug_text_3d(world_coords, message) from common/debug.qh. Type con_notify and press to see descriptions and more options (or use apropos con_notify). Use con_notify 4 together with LOG_INFOF("my_var: %s", my_var) ( %s string, %f float, %d integer, %v vector) to see debug output without opening the console. ![]() To test the QC menu program, you just have to restart the menu by executing menu_restart in the console. To test the QC client and server programs you don't need to restart Xonotic, you just have to start a new game with map (depending on how you launch Xonotic you may need to use fs_rescan map ). If you want you can run make all -j4 to enable csprogs.dat compression. Where -j4 is an option that lets you use up to 4 CPU cores for the compilation (it's enabled by default in. You can do so by running this command from the xonotic-data.pk3dir directory: ![]() ![]() Server and menu code produce progs.dat and menu.dat respectively.Ĭompiling the Xonotic game code without trying to compile the engine code reduces compile time a little bit, in the case you aren't interested in changing the engine code. A compressed csprogs.dat is only useful to increase download speed of such file if you host an online dedicated server. You can use QCCFLAGS_WERROR="" to let the build succeed even with some warnings and ZIP=: to skip compressing the resulting csprogs.dat (client gamecode) into a pk3. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |