Modifying Artifacts - Parse error?

[philly1919d]

Hey everyone! I am coming back to the game after a while, and wanted just to have some fun (a bit less frustrating I hope).

I went to modifying the artifact.txt, but when I do, I get a Parse Error in artifact line 1 column 1.

Any clue what I am doing wrong?

Thanks!

[Nick]

It's hard to say without knowing what modifications you made.

[philly1919d]

It is actually doing it if I make no changes at all, and just save the artifact.txt file.

I was looking to modify some of the drop rates and levels, but after experimenting a bit, it was clear that it was generating a parse error just by saving the file.

[Nick]

That's very odd. Is that in Windows? Could you indulge me by posting a file that is failing to parse, so I can try to find why?

[philly1919d]

Here is the file. I might be just doing something basic wrong, but I can't tell.

It is for 4.1.1

[Gwarl]

### IMPORTANT NOTES ###
# (1.) Any changes or additions to the file may have influence on randarts
# and may break savefile compatibility for old savegames with randarts. If
# using random artifacts, finish your existing game before making any
# changes to the artifact.txt file at all.
# (2.) Removing any artifact, or changing its "base" type (as defined by
# the tval and sval entries in the "base-object:" line), will break savefile
# compatibility for ALL savefiles.
# (3.) Adding a new artifact, WILL now affect savefile compatibility for all
# savefiles.

Is 1 still accurate?

[philly1919d]

That certainly is possible, but it doesn't even get to a point where it can load. It has the parse error immediately on boot-up.

[Sideways]

The format of the Angband part of the file is good, the problem is that there are 3 extra characters (EF BB BF, the UTF-8 byte order mark) at the very beginning of the file and they mess everything up. My guess would be that whichever editor you used put those extra characters there, and the problem wasn't immediately clear because the byte order mark is invisible in any editor that would put it there in the first place.

[PowerWyrm]

It is actually doing it if I make no changes at all, and just save the artifact.txt file.

I was looking to modify some of the drop rates and levels, but after experimenting a bit, it was clear that it was generating a parse error just by saving the file.

File is encoded as UTF-8. If you used an editor where the encoding was not UTF-8, your file will not be parsed properly.

[PowerWyrm]

Is 1 still accurate?

Yes and no. In the newer versions, all properties are stored on the object, so modifying randart generation won't change anything on your current game. However, it will influence future games, since modifying the base set will probably generate different randarts.