'object.txt' format suggestion

[PaulBlay]

Suggestion: Add 'otion' (etc.) to the N: line.

It makes it more obvious that

N:433etection:rod
G:-:d
I:66:4:0

is a rod (not a wand) and it allows the 'name' line to be unique even without the number (does not apply to certain artifacts). The latter would come in handy if it is ever decided to re-order the list (between versions or between variants). It would also make it consistent with monster.txt where the monster name should be unique.

[zaimoni]

Eh...what would really be helpful when reordering the list, is obliterating the index number outright and just going off of sval/tval indexing. I'd be fine with changing sval to a textual representation as well, for readability (but I think that might be in V SVN already).

It's not that difficult a change (pushed through in Zaiband 3.0.9). Easy way to do it is to make the k_idx an internal detail handled when loading the file, that never reaches the savefile or the object.txt file.

[PaulBlay]

(but I think that might be in V SVN already).

Not when I downloaded it a short while back.

I think you're right about just using the tval and sval. If a single number is really needed you could just have TTTSSS (e.g. tval * 1000 + sval). That would allow easy ordering and a unique number while still preserving the tval and sval information.

[zaimoni]

Currently, the single number that is needed is an array index into the reference data for the standard objects. Eliminating this number from the object.txt configuration files was easy.

Eliminating this number from the monster.txt files: not so easy; I don't see a good hook for doing this. But that would also be very convenient.