[mjn.mixael]

This one is a bit more involved.. so I thought a new thread would be appropriate.

The Debug log is a pain (for me at least) to read. So, using my modding experience and the Lore of the Support Ninja thread, I put together a syntax to help make it more readable.

It will also help check for certain common errors. I'll go through what I did here. I tested this against a limited number of logs and since the types of log entries is near limitless... this may not be perfect.


Warnings and Errors are highlighted as such making them easy to spot at a glance. These should be things that the modder/creator needs to fix.


These lines are highlighted because The_E said they are important! If you don't see them.. oops!


Max texture size is highlighted because it's good to note it when doing support.


No log should have two of these.. this is to show the difference. Non-english language settings can be problematic and will be highlighted in red instead of green.


Freespace version and the -mod lines are picked out in blue. Good things to pay attention to when doing support.

Currently, number highlighting is acting super weird and I can't figure it out..

Install
Open Notepad++, go to the Language dropdown -> Define Your Langauge... then import the file.

DOWNLOAD LINK

[FreeSpaceFreak]

Nice touch including the checksum verification

[mjn.mixael]

I posted an update to this one. It should now catch ASSERTION in red and then mark a lot of new things in yellow. Generally yellow is 'you may want to take a quick look at this', while red is 'OMG FIX THIS NAO'.

So yellow, now inludes 'null moment of inertia' and 'potential problem found' which are not always things that need fixing, but often are.

[karajorma]

Any chance of one of these for the mission log file? It's a much simpler format than the debug log but I suspect there are a few people who might like one.

[mjn.mixael]

Yeah, I can whip one up soon.

[karajorma]

Cool. Having that would probably make it worth going back to using Notepad++

[mjn.mixael]

OK, this has been updated to do some stuff for the event log. Since the event log is also a .LOG, I decided it should use the same notepadd++ language so you don't have to switch all the time.

The event log's syntax is very simple in that I couldn't do much but highlight some keywords and section headers. It'd be handy if event headers began with 'Event: EVENT NAME HERE' instead of just the event name.  But oh well, this works fine enough. It highlights TRUE, FALSE, ALWAYS TRUE, ALWAYS FALSE, etc... as well as numbers and a few other little things to help readability.

NOTE: I discovered that the checksum highlighting for the retail VPs was not working properly, so it's been removed and replaced with a simple highlighting of retail VP checksums. You'll have to check them on our own!

[karajorma]

The event log's syntax is very simple in that I couldn't do much but highlight some keywords and section headers. It'd be handy if event headers began with 'Event: EVENT NAME HERE' instead of just the event name.  But oh well, this works fine enough. It highlights TRUE, FALSE, ALWAYS TRUE, ALWAYS FALSE, etc... as well as numbers and a few other little things to help readability.

That would take me about 10 seconds to fix. I'll implement it next time I'm coding.

[mjn.mixael]

Karajorma implemented a little bit of syntax to the event.log, so this update takes that into account.

[karajorma]

I forgot to post that I tried it out and it works just fine.