QUOTE |
- Added the LoadConfig and ConfigFile properties to the spawner allowing them to read their configuration information from an XML file. This is similar to the [xmlload command except that it does not create a new spawner to replace an existing one. This allows updating of selected properties without having to respecify all of the properties. e.g. having an .xml file that just contains the spawn object definitions being loaded into an existing triggered spawner would allow that spawner to have dynamically configured spawns. The spawner property names are identical to those contained in the standard [xmlsave files. The dataset and table names have been changed to avoid any possible confusion as to what is intended to be a fully specified [xmlloadable .xml file and a partially specified config file. An example of several .xml config files are included in the xmlextras package. Several ways in which this could be used would be to have a switch or other object target the spawner with the TargetProperty string "/configfile/dynamicspawn.xml/loadconfig/true" or have a spawner do the same thing with a spawned SET command "SET/configfile/dynamicspawn.xml/loadconfig/true" and the target spawner as the SetItem target, even having a spawner reconfigure itself. |
QUOTE (ArteGordon @ January 11, 2006 12:06 pm) |
yes, you set the configfile property, and then set loadconfig to true (like with quest npcs). |