Scenario Design
    Scripting Database

SHADOW MAGIC SCRIPTING
Scripting Database

Using Control Counter as a Workaround for Buggy Events

by Talon-Thorn

DOWNLOAD: sample scenario file

Outline:
A simple scenario showing how to use the Request event, how to set up a custom Quest, and how to control various events using the Control Flag event.

Scripts:
Control Counter is a very useful event that I've found essential when dealing with event bugs as a workaround. Using Request Reply with a Gold Reward event does not work properly, because for some unknown reason the Request Reply fires twice. To avoid this, a Control Counter is set, and then a Counter Change trigger is used to actually evoke the Gold Reward event.

Similarly, there is a problem with using a Change Terrain event with the condition Item Owned when an area is entered. It just doesn't work at all, even though the same trigger/condition works fine for showing messages. To get it to work, set a Control Counter event when the trigger/condition is satisfied. Then use a Counter Changed trigger to actually do the terrain change.

Side Note: terrain can not be changed to ice if on the surface level and the terrain has been elevated.

Setup:
See sample scenario file for details.

Details:

The scenario consists of an adventure where the player can pass through a teleport location (or go back), and is charged 100 gold each time he uses the teleport. The player has the option to refuse the teleport by turning down a Request Reply. Next, the player must find a certain item to get across a river. Once the item is found, a river hexagon is changed to ice, allowing the player to pass it.

For the first stage in the scenario, when a unit enters a "teleport" area, a Reply Request is sent. If the player responds "yes" then a Control Counter is used to add 1 to a counter (all counters are automatically initialized to zero at start of game). Another event has a Counter Change event, set to fire when counter = min/max 1. That trigger fires the Gold Reward event (for negative gold to charge for the teleport event).

Since the Reply Response trigger is firing twice (no idea why), it increments the counter twice. Once to 1 then to 2. The Gold Reward occurs on the first counter increment, but not the second. Another event is used to reset the counter back to zero (so that the teleport can be used again).

For the second stage in the scenario, the Change Terrain event does not want to fire when triggered by an Enter Area event that has condition AND Item Owned. For whatever reason, we don't care, since we are just going to use the workaround once again. Instead of triggering the Change Terrain event, the Enter Area event with condition AND Item Owned is going to evoke a Control Counter, adding 1 to it. Then a Counter Changed trigger set to go off at counter = min/max 1 will trigger a Change Terrain event to change a location to ice.

You should look at the actual working scripts in the sample scenario for more details.