Question changing osetval to be more dynamic?

Our mud has a few more values when it comes to objects and for some reason we cant seem to get osetval to apply to some of our gear. Is there something in the code that would prevent osetval for making brute force changes to the values of an object because nothing we do seems to get them all to set.

osetval 0 1
osetval 1 2
osetval 2 3
osetval 3 4
osetval 4 5
osetval 5 6



just curious!

ryan

First check structs.h for this bad boy:
#define NUM_OBJ_VAL_POSITIONS 4

In your example you'd need to have the definition set to 6 (includes 0).

yes ours is set at 7

Oh wait - in your trigger you should write it like this:
oset <number> <number>

Not osetval.
In game check out trigger 79 (tstat 79)
Is that it?