Sumsetting

+jhelp sumsetting

Summary settings should only be set on the bucket, and not the parent. If set on the parent, then it becomes a bucket setting and /sumset will not function on it (though +bucket/set will pick it up, as both formats are identical). A summary setting requires two attributes and has an optional third: ACCESS_ (required) PROCESS_ (required) ERROR_ If you need to see examples, refer to the TPS bucket's settings.

Continued in: sumsetting2

+jhelp sumsetting2

ACCESS_ : The ACCESS_ determines who can use /sumset on the. It is passed one argument: %0, which is the Player DB# being tested. It returns 1 if the player can access and 0 if not. Continued in: sumsetting3

+jhelp sumsetting3

PROCESS_ : This is the most complicated attribute. It requires: [setq(3, )][setq(1, )][] Optional: [setq(2, )] is the attribute to set on the job object if the input is accepted. is the data that is getting set (null will clear the attr). At the end of the two registers, you should test the input and return 1 if the input was acceptable, and 0 if it was not. Only if this returns 1 does get set to. Continued in: sumsetting4

+jhelp sumsetting4

ERROR_ If PROCESS_ has returned 0, then the code will generate an error message. If you set %q2 in PROCESS_, then error message attributes will be constructed like so: ERROR_ <%q2> In this way, you can display 'complex' errors that make sense, such as the classic: 'That is not a player.', 'That player is not approved.', and 'That player is not of the Ninja class.' See also: summary