Releases: SST-Systems/Configurators
Releases · SST-Systems/Configurators
Release list
3.1.3
3.1.2
3.1.1
3.1.0
Context-aware conditions — a generic sibling for every Condition type, alongside the existing context-free ones in the same files.
- Added
ICondition<TContext>/Condition<TContext>,ConditionData<TContext, THandler>,IConditionHandler<TContext>/ConditionHandler<TData, TContext>,ICompositeCondition<TContext>/CompositeCondition<TContext>, compositesAll<TContext>/Any<TContext>/None<TContext>/Not<TContext>, andConditionProcessor<TContext>. The context flows intoIsMet(TContext context), mirroring the Modifications module. IConditionManager/ConditionManagergained aResolveConditions<TContext>(ConditionProcessor<TContext>, Component)overload, backed by a pooledIContextConditionHandlermarker; composites are walked recursively with the same cycle guard as the context-free path.ConditionProcessor<TContext>evaluates viaIsMet(TContext)and keeps a per-subscriber context inSubscribe(TContext, Action<bool>), so a single processor can drive several contexts at once. The reactive change signal stays context-free.
Full Changelog: 3.0.1...3.1.0
3.0.1
Samples overhaul — clearer, self-contained examples. No runtime API changes.
- Renamed samples for clarity: Configurable Button → Instructions for Button, Object Configurator → Modifications for Object, Reactive Visibility → Conditions for Visibility, Currency View → Extensions for Config, Zenject Integration → Zenject For Configurators — folders, namespaces and assembly definitions updated to match.
- Modifications for Object: spawns 2D UI Images instead of 3D objects, spawning automatically every second;
Shapenow wraps a UIImage. - Conditions for Visibility: reworked around UI toggles (removed the timer/tick mechanism);
StateConditionController→StatefulWidgetController; added a ready-made two-stateDefaultStatefulWidget(Active / Deactive); sample instructions are nowChangeImageColorandSetTextLegacy. - Made each sample's configurators distinct, so importing all samples at once introduces no duplicate behaviours.
- Renamed serialized fields for clarity:
ExtensionProcessoronCurrencyConfig,modificationProcessoronShapeSpawner. - Docs: added English/Russian READMEs for the Zenject sample, rewrote the sample READMEs in plainer language, refreshed the sample table and fixed links in the main README, and tidied in-code comments across all samples.
- Fixed the sample links in the main README that broke on spaces in
Samples~/...paths (now URL-encoded). - Aligned the Modifications module example with the Quick Start — shared
Unitcontext andEnemySpawner, so the two sections read consistently (no API change). - Added a "Usage Lifecycle" section with a block diagram (
Documentation~/lifecycle.svg,lifecycle.ru.svg) to both READMEs, showing how to pick a module and the shared resolve → use → cleanup flow.
Full Changelog: 3.0.0...3.0.1
3.0.0
First public release under SST Systems.
Design gameplay rules in the Unity Inspector — no code. Modifications, Instructions, Conditions, Extensions: serializable, pooled, DI-ready.
Full Changelog: https://github.com/SST-Systems/Configurators/commits/3.0.0