okay so turns out the easiest way to attach the file was on discord if you check there.

@Nick I sent you the savefile in question. The self-downloading thing has been broken since versioning was added, I'll try and look into whatever else can be done.

Edited the title, bump this again if/when it happens in future

cleared.

Maybe make a thread for crashes?

Yeah it looks like what you've done here is to do for (frog?)composband what I did for whichever nightly version of angband I did my JS script for, the problem comes when all angbands have (sometimes) very similar but not quite the same formats, but DM has been working on it, I am looking for the time to do it. I have gotten a new PC and have been very distracted by the pretty 3D tank battles it lets me fight and have just been catching up on making new job applications.

I have chosen Eclipse to use as an IDE and have imported some angband-related projects which I also need to catch up on as I learn my way around Eclipse. Have also ditched windows and linux is so mind-bogglingly simple it's difficult to conceptualise my workflow with all the same clunky slow-moving parts I had on windows.

Ok very good but I think there's some confusion, now we have my prototype for a parser in node.js, DavidMedley's prototype in Perl, and now yours in Go. You (specifically you) can see the perl scripts in /home/angwiki/

As long as there's some sort of plugin-able template which describes a variant that any of our parser scripts can read then it doesn't matter which one we use, really.

for the minute I just want everything in tables in the MySQL dB, once we have that we can present the information any way we like and have SQL selects automatically to run searches against them, eg

List level 60-80 unique D's from every variant, show every monster marked DEMON in vanilla, etc.

Here's a typical file:

https://github.com/angbandplus/AngbandPlus/blob/10670ef50d7454d0a5d076b5dd529c281b940e05/lib/edit/monster.txt

I'm just saying we should establish a convention for writing templates for these structures so the parser knows what to look for.

We do to make any sense of them. Not everything is a name:value pair. How do we know which lines are name/value pairs and which aren't, and how do we know which names they have? We need a solution for all variants, not just angband 4.2.0. If we have to write new code for every version and variant we will remain small and incomplete.