> @show me
Object: $character [3,346 bytes]
Parents: $admin, $programmer, $user
$npc variables matching "*":
stat_str: 20
stat_int: 13
stat_dex: 15
stat_will: 10
$user variables matching "*":
task_connections: #[[54965, $login_connection_23564]]
> @program $npc.will() +access=pub
– Programming public method $npc.will() –
arg @args;
if (args)
stat_will = args[1];
return will;
.
@eval me.will();
=> 10
@eval me.will(25);
=> 25
@eval me.will();
=> 25
> @grep +d .int $spells
Searching for ".int"…
$spells.invisibility(): 13 and 19
$spells.detect_invisibility(): 1, 4, 5 and 7
$spells.charm(): 6, 13, and 17
Guess you have a big 'guidelines bport guide' to address all these case you should avoid. I see a lot of wasted time from builders otherwise, unless they stay conservative in their building.
If a lot of your creators spend a lot of their time coding THE uber <whatever> of <something> that beats ANY <whatevers> then sure, you probably will have a lot of mediation to do.
I don't find this to be a particularly common habit of creators, but perhaps on some muds it might be, and in those cases it would probably make things smoother to have some overall guidelines of how people should be good code citizens.
-Crat
http://lpmuds.net