Icons Command Console

[bearpounder]

Sorry to get all techie, but hoping someone (wink wink) might know the answer to this:

I am in Icon and running the command console. I have set the access level pretty well up there,
and I have found one particular command. "DumpParserStructs" I want to run which supposedly
dumps the text parsers to the console but when I run the command *NOTHING* happens.

Is there a trick to get these mysterious commands to work?

(That is not the only one that appears to do nothing BTW)

Oh and how do you clear the darn thing?

[Codewalker]

It does something. If you have the text console open (use /console 1 first), it causes the following text to be printed on it:

"Not using private parser heaps."

The command description from cmds* seems to indicate it has something to do with memory allocation, but the actual code path in the exe just prints that message. It's probably something that was #ifdef'd to only work in debug builds or something along those lines.

* Not that the command descriptions are very accurate, especially for developer (accesslevel 1-9) client commands... Many of them depend on server-side support, do nothing, or do something wildly different than what the name or description would suggest.

[bearpounder]

got this with the textparserdebug

7 zowies found                              (0.01)
Time to load game and get into a map: 102s


Not using private parser heaps.
setting up textparser defines & clearing old structs ..success
loading from test string ..success
writing test file ..success
reading test file ..failed!
comparing file to test string ..different!
getting precompiled result from .bin file ..failed!
comparing bin file to text file ..success
writing schema to disk ..success
reading schema from disk ..success
writing schema to disk again ..success
using schema to load text ..success
writing to disk using schema ..success
Finished!


Any idea where this "file" might have been written to?

[Codewalker]

If it's a debug command? Who knows. Those tend to strew crap everywhere, usually with hardcoded paths like C:\Game, C:\Cryptic, or even the root of C:. Best bet is to use process monitor to see where it's trying to write.