Warzone 2100 Forums

Hi,

I make some tool to read output of js debug. (it is useful for windows, linux show it in console)
Its crossplatform desktop app.

Screenshot: Installation instructions: Linux:
nw wz_output_reader (sorry, not tested)

Windows:
nw.exe wz_output_reader

Set path to game executable.
Run game.

Repository:
https://bitbucket.org/Cjkjvfnby/wz_output_reader

He is any place where I can read about warzone command line avaliable params?
like --mod=<> and --debug

Command line params: http://developer.wz2100.net/wiki/CommandLineOptions -- I don't think it's a full list.

IIRC many of the command line params were deprecated or moved to the config file: https://warzone.atlassian.net/wiki/display/mod/config

update:
Rewrite it on coffescript.
Add game launcher/stopper
Add show common log.
Add path to executable input.

Download link https://bitbucket.org/Cjkjvfnby/wz_outp ... der_0.2.nw
Installation instructions:

Another update now all objects is inspectable.

Add new javascript for inspection code. (https://bitbucket.org/Cjkjvfnby/wz_outp ... ?at=master)

https://bitbucket.org/Cjkjvfnby/wz_outp ... 2-11-09.nw

Why not just:
As that will have same effect, no?

Also, does that work in WZ env or just Node? (I've no experience with Node...)

aubergine wrote:

Code: Select all

}).call(this);

Why not just:

Code: Select all

})();

As that will have same effect, no?

Yes same. It is CoffeeScript.compile

Also, does that work in WZ env or just Node? (I've no experience with Node...)

inspector.js works in WZ. (I check it in 3.1_RC3)

oh cool, didn't see this topic before aubergine mentioned it! this should help we getting the warning message that Per was talking about. Thanks Duha!
does this work on 3.2 as well?

I think yes.

I've added a link to this tool in the Notes section on this wiki page: debug()

aubergine wrote:I've added a link to this tool in the Notes section on this wiki page: debug()

Did game write js debug to log file on Linux or just to console?

I don't know for sure, but I heard that on linux it writes to both log file and console! I think that was problem Per was facing when thinking about making debug() always write to log file, that on linux it would result in two copies of the debug() going in to log file.

It does not automatically log to file on Linux, either. You have to ask it to do that using a command line option.