DDOS Scenario Framework

1.0.4

New:
- Players: one target rule for all player steps, plus steps for waiting for players and tickets, setting tickets, respawn rules, respawning the dead, healing, observer camera and killing characters.
- Events: "Zdarzenie - czekaj" for deaths, wounds, vehicles, items, players, AI groups and destroyed objects, "Licznik zdarzen" for counting them, and named mission signals with a window button and #ddos fw signal.
- Data: typed variables with the Game Master window "Zmienne", templates in message texts, and getters for counts, time, state and math.
- Flow: reset with undo and a preview panel, "Reset kroku", "Powtarzaj", sets and "Dla kazdego" with up to 256 elements.
- Place: the field "Miejsce" in teleport, waypoint and spawn steps. Step waypoints are visible to Game Masters, who can move or delete them.
- Randomness: "Losuj galaz" with weights, Game Master choice and kept draws; random places that skip water and taken spots; random prefab variants; random set elements, order and numbers. One mission seed in setting 303 "framework.randomSeed", written to the server log.
Changes:
- Old integer-only variables are replaced by typed ones. "Undo On Reset" replaces the old reset fields. Classes and prefabs lost the "Fw" prefix.
Known limitations:
- Variables are not saved. A reset does not undo a living AI group, a message, a signal or a player action.
- The water and space test covers the spot of a group, so a soldier of its formation can stand in water or next to a wall. A random spot can land in an open building, and beside the sea the result depends on the wave.
- A repeated vehicle with a small random radius can stand inside the last one: use a larger radius or "Undo On Reset".
Update DDOS Lobby Core, DDOS Lobby and DDOS Scenario Framework together.

1.0.3

Fixes:
- World Editor: the "wx_two_owners" warning no longer appears for weather steps hung one under the other (for example PAR > Set weather > Weather sequence > Weather sequence). Such steps run one after another, so it is a normal queue.
- For two weather steps in different branches of one PAR the warning now says that they run at the same time and how to fix it (hang one under the other, put one behind a trigger, or remove one).
Runtime behaviour is unchanged. DDOS Lobby Core 1.0.7 and DDOS Lobby 1.0.9 are unchanged.

1.0.2

New:
- Smooth weather changes: clouds, rain and wet ground blend over the time you set (native engine transition, same for late joiners).
- All weather times are in REAL minutes; the game needs at least 10 game minutes per change (warned in the editor / log).
- Weather sequence step (1-8 states, each with change and stay time), weather trigger step, weather-to-variable step; Set weather v2 with wind modes.
- Setting "Automatic weather changes" (framework.autoWeather, on by default): off = the start weather holds and every weather step starts at once.
- Readable names for mission authors: classes and prefabs without "Fw" and abbreviations, Polish labels in Inspector lists and in the Game Master window.
Changes:
- The Game Master wins: a GM weather change ends a waiting weather step or sequence.
- Renamed author-facing classes and prefabs (map in the docs: framework-rename-map.md); old Set weather fields replaced by real minutes.
Known limitations:
- With automatic weather on, or right after a GM weather change, a step's change waits for the running transition to end.
Requires the matching version of all DDOS addons.

1.0.1

New:
- World values by right-click: right-click the step component in Object Properties > "DDOS: <field> = <value>" lists the values of THIS map - weather states of the map's weather manager (custom managers included), factions, task keys, variables, squads, slots and steps. Lists with several values get "+ value" and "(empty)".
- The chain check prints the known values of the map next to an unknown weather / faction / task / squad / slot.
Fixes:
- Fields that showed an empty dropdown arrow (weather, factions, task keys, variables, squads, slots, steps) are now plain text fields; a custom name can be typed.
- One click = one Ctrl+Z (an Act 2 template slot needs two: the re-bake is its own undo step).
Known limitations:
- A step with no step above it writes the picked value a moment later, when another step is on screen (the Log Console says "queued").

1.0.0