administrators

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.

@archenoth good catch!

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.

oh, no problem then, please continue with your and David's, no need to reinvent the wheel here Did not noticed that you have some working scripts

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.

Alright, made some code to start with.

My main idea is to define all structures and be able to fill them up .txt files directly, some of information that is found in source codes only take from external files or hardcode them in for now. Just as an example I looked through r_info.txt file and made some structures. This is all not 100% done, of course, just my rage code

I don't see much of a problem to parse files in /lib/edit, just see some different ways how to avoid hardcoding in a lot of stuff. One way of making it more universal would be ability to read our own txt-alike files that have info found only in source code files. In example above I hardcoded a bit spell types and colors.

If we able to read .txt files and fill defined structures from them we can output it to whatever format we desire. I did that in Go since I just like it very much

Hmm.. From cell phone some sections requires more tweaking and color change.