Battledale_PRC8/_module/utt/jw_leaveac_trig.utt.json
Jaysyn904 7b9e44ebbb Initial upload
Initial upload.  PRC8 has been added.  Module compiles, PRC's default AI & treasure scripts have been integrated.  Started work on top hak for SLA / Ability / Scripting modifications.
2024-03-11 23:44:08 -04:00

123 lines
4.2 KiB
JSON

{
"__data_type": "UTT ",
"AutoRemoveKey": {
"type": "byte",
"value": 0
},
"Comment": {
"type": "cexostring",
"value": "The smart area transition is used for a long trigger to allow a PC to appear in a new area in the right place relative to where they left.\r\n\r\nFor example, if a transition runs from north to south and they are at the northern bit and click on it, they appear on the northern bit of the transition when they enter the new area.\r\n\r\nIt is suitable for long edges, eg forest areas where there is no boundary. It is better I think than having a large edge to an area where there is no boundary and simply nothing there.\r\n\r\nTo use it:\r\n\r\nFirst of all note that transitions sometimes do not appear properly in the client if they are on top of raised stuff, like grass, stones or trees. Use the erasor in the toolset to flatten the ground where the transition will be. In other words, keep on clicking erase until you get a flat, plain tile, rather than one with rocks, shrubs or trees.\r\n\r\nEven then, large transitions sometimes do not appear so I have made these so that they work if a player simply walks on them, even if he does not click them. That will be a little confusing at first, but they'll soon get used to it.\r\n\r\nNote also that it becomes even more important to make sure the two areas match. Eg if one has cliffs at the north and a river at the south, so must the other (assuming the trigger is running from north to south)..\r\n\r\nPlace a copy of this trigger on the ground. Give it a unique tag. Put a waypoint in the middle of the trigger but *away from the edge* with the name WP_(tag of this trigger). Eg if this trigger is called jw_forest the waypoint would be WP_jw_forest.\r\n\r\nThe waypoint should be on the opposite side of the trigger to the edge of the area. For an example, take a look at the area called in the depths of the forest. On the far eastern side is a long trigger running north to south. The waypoint is in the middle, as you go north to south, but to the west of the trigger, as the area transition is to the east. (There is also a map waypoint right in the middle - just ignore that).\r\n\r\nThen give this trigger a name which must be the TAG of the trigger it is going to.\r\n\r\nPlace your other trigger and do exactly the same thing, except of course this time the name would be the name of this trigger.\r\n\r\nObviously, this trigger should match the first one more or less in size and orientation.\r\n\r\nThat's it."
},
"Cursor": {
"type": "byte",
"value": 1
},
"DisarmDC": {
"type": "byte",
"value": 0
},
"Faction": {
"type": "dword",
"value": 1
},
"HighlightHeight": {
"type": "float",
"value": 0.0
},
"KeyName": {
"type": "cexostring",
"value": ""
},
"LinkedTo": {
"type": "cexostring",
"value": ""
},
"LinkedToFlags": {
"type": "byte",
"value": 0
},
"LoadScreenID": {
"type": "word",
"value": 0
},
"LocalizedName": {
"type": "cexolocstring",
"value": {
"0": "Smart area transition",
"id": 14759
}
},
"OnClick": {
"type": "resref",
"value": "jw_smarttrig_en"
},
"OnDisarm": {
"type": "resref",
"value": ""
},
"OnTrapTriggered": {
"type": "resref",
"value": ""
},
"PaletteID": {
"type": "byte",
"value": 3
},
"PortraitId": {
"type": "word",
"value": 0
},
"ScriptHeartbeat": {
"type": "resref",
"value": ""
},
"ScriptOnEnter": {
"type": "resref",
"value": "jw_smarttrig_ent"
},
"ScriptOnExit": {
"type": "resref",
"value": ""
},
"ScriptUserDefine": {
"type": "resref",
"value": ""
},
"Tag": {
"type": "cexostring",
"value": "jw_smart_trig"
},
"TemplateResRef": {
"type": "resref",
"value": "jw_leaveac_trig"
},
"TrapDetectable": {
"type": "byte",
"value": 1
},
"TrapDetectDC": {
"type": "byte",
"value": 0
},
"TrapDisarmable": {
"type": "byte",
"value": 1
},
"TrapFlag": {
"type": "byte",
"value": 0
},
"TrapOneShot": {
"type": "byte",
"value": 1
},
"TrapType": {
"type": "byte",
"value": 0
},
"Type": {
"type": "int",
"value": 1
}
}