Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mizipzor]

Im working on a python script that parse all found creature files to find the creature tags and checks what parameters they have. That part is almost done, now I want to export the rules to a file to be used later to validate created creatures.

Im a bit unsure as to how to make the file format. There are no other attribute parameter types other than digit and string, right?

But what about the digits? Are they all in the same range, 0-255?

If both the above the statements are true, which would be perfect, then I think I would do something like this:

[NAME:a:a:a]

For indicating that the NAME attribute takes three parameters (at least I think it does, was a bit long ago I actually checked the files myself), all alpha/characters.

Any comments? Just wanted to bounce some thoughts. 

[Untelligent]

Some of the digits are quite a bit larger than that, and the temperature-related digits are over 10000.

I remember the maximum temperature was somewhere above 60000, so the absolute maximum digit range would be 0-65535. Actually, I think it would be more than that; it's possible for some parameters, like the damblock (I think. I could be wrong about that.) to go into negatives, although I don't think there's any in the vanilla raws.

[Baneslave]

...like the damblock (I think. I could be wrong about that.) to go into negatives, although I don't think there's any in the vanilla raws.

Actually, vanilla elves have damblock -1.

[mizipzor]

Hmm, it seems indeed that the digit parameters vary between unsigned int and a signed int. Thats bad, since you cant tell which one it is by just looking at the file (assuming its inside the 0-32767 range). Do you think there is any point to try to really build a database on what tokens there is and how they work? I mean on the technical side, not the effect of the token, like what the numbers range is.

Maybe thats already in the wiki in the token section, ill dig around some. Thanks for the comments by the way.

[i2amroy]

so the absolute maximum digit range would be 0-65535. Actually, I think it would be more than that; it's possible for some parameters, like the damblock (I think. I could be wrong about that.) to go into negatives, although I don't think there's any in the vanilla raws.

You can technically set the damblock token to any number you want, one time for fun I gave a creature a damblock of over a million.

[mizipzor]

Im currently leaning to this:

<rule>
   TOKEN_NAME
   <str/>
   <byte/>
   <long/>
</rule>

Xml for the rule database file. This in turn implies, when parsed, that the token TOKEN_NAME needs three parameters, a string, a byte (0-255) and a long (like, a huge number).

How many tool coders are we in here? I would like to put something together that we all can use. If Im the first trying to do this or if no one else has any more comments/suggestions I just rampage on ahead! 

edit: Just had a quick chat with TheSpaceMan. He reminded me that the body and attack doesnt have a fixed number of parameters. And the spontaneous response to the problem was to add a <unbound> tag to the rule. If it is present, the above parameters would be repeated over and over. I.e no "number of parameters" check, just type check.

For example, attack:
<rule>
   ATTACK
   <str/>
   <int/>
   <unbound/>
</rule>

Since I have so little experience in actual modding myself, I will probably do quite a few of these kind of mistakes, hehe.