Updating Scripts - TTLG Forums

LarryG on 21/5/2011 at 22:42

Quote Posted by Telliamed

"Play" uses schema tags. "PlaySchema" uses schema objects. When you play a tag, the object's Schema\Class Tags property gets added to it (and some other interesting tags, like the mission number)

Sorry to be dense, but I'm still a little confused by this. My FireShadow has a Class Tag of CreatureType Guard. So this is saying that for CreatureType Guard, I need to provide an entry someplace in ENVSOUND.SPC or SPEECH.SPC for the tag "Event Launch" and a schema somewhere that references that tag, otherwise how is a sound associated with the tag so that it will play when the service is executed? What am I not understanding? :confused:

Telliamed on 24/5/2011 at 23:20

The launch event is for the emitter, not the emitted object. If you want there to be a sound effect when the creature is created. If not, just ignore it. (This wasn't part of the original script, it just seemed like a fun addition.)

So after wrestling with GitHub for half an hour, I got this weeks builds uploaded.
(https://github.com/whoopdedo/publicscripts/downloads)
(https://github.com/whoopdedo/lgscript/downloads)

New in Public Scripts are:

Code:

/**
* Script: FireShadowEcology
* Inherits: BaseScript
* Messages: TweqComplete
* Links: ControlDevice, Firer
* Properties: Tweq\Flicker
*
* Respawn a creature after it dies. A ``Tweq\Flicker`` fires to test if the
* creature needs to be spawned. The tweq flags can be set to only fire when
* the player is not looking at the spawn point. That way the creature will
* only appear offscreen. The creature archetype to spawn is linked to with
* ``ControlDevice``. When spawned, a ``Firer`` link is set from the creature
* to the spawn point. A new creature is spawned only when there is no ``Firer``
* link to this object.
*/
/**
* Script: FireShadowFlee
* Inherits: BaseScript
* Messages: Slain
* Links: CorpsePart
* Properties: Creature\TimeWarp
* Metaproperties: M-FireShadowFlee
*
* A creature that flees when killed. On ``Slain``, the creature drops its
* ``CorpsePart`` linked objects and gets the ``M-FireShadowFlee`` metaproperty.
* The creature speed is accelerated until it disappears from the player's
* view, or after 15 seconds. Then it is destroyed.
*/
/**
* Script: TrapProperty
* Inherits: BaseTrap
* Links: ScriptParams(??property??)
*
* Change the properties on linked objects. Sets the property when turned on,
* or deletes it when turned off. The link data is the short name of the
* property to set or unset. If the data begins with $$@$$ then the data is
* the name of an object and all properties from that object will be copied to
* the linked object when turned on.
*/
/**
* Script: PropertyScript
* Inherits: BaseTrap
* Links: ControlDevice
* Parameter: property(string) - Name of the property to modify.
* Parameter: fields(string) - List of property fields.
* Parameter: onvalue(string) - Value or list of values to set when turned on.
* Parameter: offvalue(string) - Value or list of values to set when turned off.
*
* Modifies the value of a property on linked objects. The property name is the
* short name of the property as listed by ``list_props``. Simple properties do
* not need a $$fields$$ parameter and the value parameter is a single string.
* If the property has multiple fields, then the value parameter is a list of
* comma-separated values. With the $$fields$$ parameter, only the named fields
* are modified and the value parameter is a list that corresponds to those fields.
* Fields that don't have a listed value are unchanged. If either $$onvalue$$ or
* $$offvalue$$ is omitted, then the property is not changed for that switch.
*
* Property fields are named with an abbreviated format. Take the original name,
* as displayed in the Dromed object editor, and ignore anything that isn't a letter
* or number. Match the first field that starts with the name given in the $$fields$$
* parameter. The parameter name can end with a number enclosed in square braces.
* This is the subscript and will match the n-th field that starts with the name.
* So ''A[1]'' will match the first field that has the first letter ''A'', and
* ''A[2]'' will match the second field that starts with ''A''.
*
* Values are either a string, number, boolean, or vector. Multiple values are given as
* a list of values separated by commas. Any value in the list can be enclosed in
* parentheses. A pair of parentheses with nothing in-between is a null value and indicates
* that field should not be changed. An empty value not in parentheses is a blank string.
* A vector is three number separated by commas. Because commas are used between values,
* a vector in a list must be enclosed in parentheses.
*/

The PropertyScript is just using the built-in field parsers for now. This means you have to type the values the same way they appear in Dromed's dialog boxes.

In LgScript I've put in functions for creating object & links as userdata, but don't yet have support for using them in functions. But you can use them as:

Code:

local aLink = lgs.link(link_id_as_number)
print(aLink.id, aLink.source, aLink.dest, aLink.flavor)
print(aLink:Get()) -- returns dest,source,flavor
print(aLink:GetData(field_name))
aLink:SetData(...) -- this doesn't work yet

local anObj = lgs.object(objid_or_name)
print(anObj.id, anObj.archetype, anObj.name)
print(anObj.position, anObj.facing)
print(anObj:Exists(), anObj:HasMetaProperty(mp), anObj:InheritsFrom(archetype))
anObj:SetName("IAmNotAnObject")

You get the picture. Suggestions are welcome. I'll probably add a Teleport method to objects. And make it so wherever an object is expected, you can pass either a lgs.object, a number, or a string.

PS. ''heap_dump_modules'' ;)

LarryG on 25/5/2011 at 01:32

Way awesome! Thank you. :thumb:

Quote Posted by Telliamed

OK, so the emitter can have a sound associated with emitting a Fireshadow. It does sound like a fun addition. What do I need to do to try it out? I still don't get that bit.

Telliamed on 25/5/2011 at 23:20

Just give the emitter class tags. Use a device type that already has an "Event Launch" schema, or make your own.

LarryG on 26/5/2011 at 04:21

Kayso ... I give my FireshadowSpawner Schema > Class Tags: AlarmType FS_Spawner, edit ENVSOUND.SPC to add AlarmType FS_Spawner, and set up a new schema based on the flashbomb_exp schema ('cause its a COOL sound):

//FIRESHADOW SPAWNER --- sound of spawn

//Emitting the Fireshadow
schema fireshadow_emit
archetype HIT_EXPLOSION
volume -1
flashbmb
env_tag (Event Launch) (AlarmType FS_Spawner)

Should work, yes? I'll let you know ...

LarryG on 27/5/2011 at 14:24

Could AIWatchObj links on the object with FireShadowEcology be replicated onto the newly created Fireshadow? That would allow emitting Fireshadows capable of more sophisticated patrolling.

LarryG on 30/5/2011 at 00:27

Well, I'm done testing the FireShadowEcology and FireShadowFlee scripts. They work pretty well, but there are anomalies:

* FireShadowEcology will occasionally spawn two FireShadows at once. I've seen it happen three times (out of dozens of spawnings). I suspect it is some kind of timing issue.
* The creatures seem to have no trouble spawning while I watch. I don't know if that is because I am testing with aiwatchobj on or not. In any event, I don't think it's bad. They tend to spawn half in the floor no matter the height of the FireshadowSpawner, so it looks like they are crawling up through the floor. Pretty creepy. Much better than just appearing out of nowhere.
* The dropping of the FireCrystal might be better off delayed until the FireShadow speeds up the first notch. As it is, the crystal is dropped before it starts fleeing and looks kinda dorky. If it was dropped as it fled, That might look better, and be placed more randomly about.
* And I still can't get the schema to play. I think that was such a cool idea, but I can't get it to work.

Edit: Here is another issue: It appears that the Spawner's FlickerState's Cur Time value is not getting reset when a FireShadow is slain. This results in the next FireShadow getting spawned any time between 1 and the Flicker's Rate number of milliseconds later. I tested this using a Rate of 60000 and a Cur Time of 59999, and regardless of the time of the kill, the next FireShadow was always spawned at the same number of seconds after a complete minute. (in my case 24 seconds, since that's when I started the spawnings.) I think Cur Time should be set to 0 when the old FireShadow is killed.

Telliamed on 1/6/2011 at 20:25

Quote Posted by LarryG

* FireShadowEcology will occasionally spawn two FireShadows at once. I've seen it happen three times (out of dozens of spawnings). I suspect it is some kind of timing issue.
* The creatures seem to have no trouble spawning while I watch. I don't know if that is because I am testing with aiwatchobj on or not. In any event, I don't think it's bad. They tend to spawn half in the floor no matter the height of the FireshadowSpawner, so it looks like they are crawling up through the floor. Pretty creepy. Much better than just appearing out of nowhere.
* The dropping of the FireCrystal might be better off delayed until the FireShadow speeds up the first notch. As it is, the crystal is dropped before it starts fleeing and looks kinda dorky. If it was dropped as it fled, That might look better, and be placed more randomly about.
* And I still can't get the schema to play. I think that was such a cool idea, but I can't get it to work.

1) Can't imagine how. Are you sure you aren't doubling the script.
2) Check the properties of the marker. The tweq should not have a "Sim" flag, just "Offscreen", and the marker needs to be physical and rendered, but with dimensions of zero so it isn't visible.
3) Meh, I doubt anyone will notice nor care. Thief Gold was the same way.
4) That's on me. It's supposed to be played as an environmental schema. Also, the "Launch" event is usually used on projectiles. Emitters get "Shoot", but I'll just go with "Activate" like most other devices.

Adding AIWatchObj links is straying too far from the original script. I wouldn't expect it to be used very often. Better to have some other script deal with it. I added a trigger when the spawn point activates, so you can CD link to other traps. The trigger is sent with the AI's object ID as extra data.

LarryG on 2/6/2011 at 01:06

Quote Posted by Telliamed

1) Can't imagine how. Are you sure you aren't doubling the script.

I'm sure. My theory is that because the Cur Time value is not reset, a second fireshadow is spawned before the link can get established to prevent that. It's a theory. Fix one, fix both, I hope.

Quote Posted by Telliamed

2) Check the properties of the marker. The tweq should not have a "Sim" flag, just "Offscreen", and the marker needs to be physical and rendered, but with dimensions of zero so it isn't visible.

My bad. I had specified Sim. But since I like the effect of the critter climbing up through the floor, I may keep it. PS. I made the marker not rendered, because despite the zero dimensions the marker showed up. Works fine not rendered.

Quote Posted by Telliamed

3) Meh, I doubt anyone will notice nor care. Thief Gold was the same way.

I noticed ... my memory is that you never really saw the crystal drop in TG, you just found it if you looked about ... but you're prolly right, no one (except ZB :laff:) will notice or complain about it if they do notice.

Quote Posted by Telliamed

4) That's on me. It's supposed to be played as an environmental schema. Also, the "Launch" event is usually used on projectiles. Emitters get "Shoot", but I'll just go with "Activate" like most other devices.

Whew, I could not figure out what was wrong with my setup.

Quote Posted by Telliamed

Adding AIWatchObj links is straying too far from the original script. I wouldn't expect it to be used very often. Better to have some other script deal with it. I added a trigger when the spawn point activates, so you can CD link to other traps. The trigger is sent with the AI's object ID as extra data.

I'll wait and see the documentation for that to see if I can figure out how to pass the id to another script & build the links.

Telliamed on 2/6/2011 at 21:44

Quote Posted by LarryG

I'm sure. My theory is that because the Cur Time value is not reset, a second fireshadow is spawned before the link can get established to prevent that. It's a theory. Fix one, fix both, I hope.

For that to happen, you'd need 1 + 1 to equal 1.
This is what I've been testing with. What are you doing differently? (http://whoopdedo.org/aashadow2.7z)

Quote:

I'll wait and see the documentation for that to see if I can figure out how to pass the id to another script & build the links.

One of NV's scripts probably munges message data in some unsavory way. Or ignore the data and just use "^FireShadow" or whatever it is that finds the nearest object type. Since the AI will be at the position of the spawn point when the trigger is fired, it'll always be the first one found.