02-03-2010 Turley:
Added: MethodScript support for mobiles
NPC: npcdesc.cfg MethodScript entry
Character: uoclient.cfg section "General" MethodScript entry
Wow!Turley wrote: Thu Jul 27, 2017 9:32 am Mmmh02-03-2010 Turley:
Added: MethodScript support for mobiles
NPC: npcdesc.cfg MethodScript entry
Character: uoclient.cfg section "General" MethodScript entry
items/multis in itemdesc.cfg per objtype
NPC in npcdesc.cfg per template
Character generally in uoclient.cfg
What is/was under discussion is to have a place to define at one specific spot all "default" methods independent of the objtype/template. Currently you have to add the right MethodScript to each item definition/npctemplate. It's a bit of work but with a few includes you can easily define default behaviour with specific overrides. (I personally used this for the tooltip pkthook to create in a fast way without dozen of objtype checks default and specific texts)
I just remembered about this idea the other day and felt i should document it in case someone feels a coder itch.
We have a tree for how objects in POL are abstractions of other thingsSo what if we had a Methods.cfg file.Code: Select all
UObject Account PolCore() DataFileElement | | Guild Script Datastore +---------+--------+ | | Array Dictionary Datafile Character Item | | AuxConnection Error String NPC | | Struct +------------------+--------------+-----------+ | | | | Package Equipment Lockable Map Multi | | | Packet +---+----+ +----+--------+ +----+----+ | | | | | | Party Armor Weapon Door Container Boat House | BinaryFile +----+----+ | | Spellbook CorpseThen if you have a corpse object in the script - you can call a method like corpse.MoveToJail();Code: Select all
Elem Corpse { MethodScript :pkg:xyz } Elem Container { MethodScript :pkg:abc }
Corpse's method script doesn't have this... so then the core goes to the next up, Container, its not there, so it goes up until the method is found. Lets pretend Item has it.
If the itemdesc.cfg methodscript has a matching function name - itll use that instead.. or could have an override like _method() for using core methods.
This would let scripts extend other things like Datafiles, Arrays, Dictionaries, etc.
Code: Select all
use os;
use uo;
include "include/arrays";
program Install()
return 1;
endprogram
exported function GetLevel( who )
var chardata := GetObjProperty(who, "chardata");
var charlevel := chardata["level"];
if (charlevel == error || !charlevel)
SetLevel(who, 0);
charlevel := 0;
endif
return charlevel;
endfunction
exported function setLevel(who, level)
var chardata := GetObjProperty(who, "chardata");
chardata.level := level;
SetObjProperty(who, "chardata", chardata);
return 1;
endfunction
exported function isClass(who, class)
var chardata := GetObjProperty(who, "chardata");
if (Lower(chardata.classe) == Lower(class))
return 1;
endif
return 0;
endfunction
exported function SkillList(who)
var chardata := GetObjProperty(who, "chardata");
var skill_list := chardata.Skills;
if (!skill_list)
skill_list := array{};
endif
return skill_list;
endfunction
exported function GetExp(who)
var chardata := GetObjProperty(who, "chardata");
var exppoints := chardata["exppoints"];
if (exppoints == error || !exppoints)
SetExp(who, 0);
exppoints := 0;
endif
return exppoints;
endfunction
exported function SetExp(who, points)
var chardata := GetObjProperty(who, "chardata");
chardata["exppoints"] := points;
SetObjProperty(who, "chardata", chardata);
return 1;
endfunction
exported function GetPoints(who)
var chardata := GetObjProperty(who, "chardata");
var attpoints := chardata["attpoints"];
if (attpoints == error || !attpoints)
SetPoints(who, 0);
attpoints := 0;
endif
return attpoints;
endfunction
exported function SetPoints(who, points)
var chardata := GetObjProperty(who, "chardata");
chardata["attpoints"] := points;
SetObjProperty(who, "chardata", chardata);
return 1;
endfunction
Thanks. I'll try it tonight and let you know of any problems.