Damian Sirbu, xlibs and AlifePlus developer · 2026-04-05 · Subject: SISKI Nano by qkff99
ModDB: SISKI Nano
| Field | Value |
|---|---|
| Author | qkff99 |
| Format | Single file (siski_compact.script, 915 lines) + 1 LTX config |
| Git repository | None |
| Version control | None |
| License file | None |
| Attribution to xlibs/AlifePlus | None |
SISKI Nano is distributed as a bare file drop: two files in a zip, no README, no license, no changelog, no git repository. Unlike SISKI ALIFE (which has a public GitHub repo), SISKI Nano has no version control history of any kind. There is no way to trace when the code was written, how it evolved, or what was added between versions.
For comparison, SISKI ALIFE's git history is what made it possible to identify the copied patterns (deleted AI plans in commit b026c90, the before/after callback comparison between 0.9.4.1 and 0.9.5). SISKI Nano has no such trail.
In plain English: SISKI Nano uses the same callback approach as AlifePlus and SISKI 0.9.5 — processing squads via squad_on_update instead of the older actor_on_update loop. This is the architectural change that SISKI adopted from AlifePlus in March 2026.
-- siski_compact.script :906
RegisterScriptCallback("squad_on_update", compact.on_squad_update)This is the only engine callback registered for gameplay processing. The entire mod runs through squad_on_update — the same design that AlifePlus uses and that SISKI 0.9.4.1 did not have (it used actor_on_update).
In plain English: When a mod takes control of a squad (sends it somewhere), it sets specific engine fields. The particular combination and order of fields used here matches xsquad's pattern rather than other Anomaly mods that do the same thing differently.
squad.scripted_target = name
squad.rush_to_target = rush == true
squad.assigned_target_id = target_smart.id
squad.current_action = 0se_squad.scripted_target = smart_name
se_squad.assigned_target_id = smart_id
se_squad.current_action = 0
se_squad.task_target_id = nil
se_squad.current_target_id = nilIndividual fields like scripted_target are standard engine usage. The specific combination — scripted_target, assigned_target_id, current_action set together with additional field clears — mirrors the xsquad and siski_ap_bridge pattern rather than the Warfare approach (which uses __lock, sets fields in a different order, and uses current_target_id).
SISKI Nano shares the same AI-generated code markers found in SISKI ALIFE, consistent with the author's admission that SISKI is "~95% vibe coded."
| Marker | Count | Rate | Detail |
|---|---|---|---|
_G. prefixed builtins | 12 | Lines 4-16 | _G.type, _G.tonumber, _G.tostring, _G.pairs, _G.next, _G.rawget, _G.time_global, _G.alife, _G.game, etc. Roblox/WoW addon pattern. STALKER Lua is not sandboxed — these prefixes are unnecessary. This pattern does not appear in any human-written STALKER mod. |
rawget(_G, ...) | 7 | 1 per 131 lines | Defensive global access pattern. Used where direct access is safe. |
== true redundant | 7 | 1 per 131 lines | Explicit boolean comparison where Lua truthiness suffices. |
time_global and time_global() | 1 | Line 92 | Existence check on an engine builtin that is always defined. |
Notably, SISKI Nano contains zero pcall wraps — unlike SISKI ALIFE (488 pcalls) and APS (67 pcalls). The other AI markers (_G. prefixing, rawget, == true) are consistent across all three mods.
SISKI Nano contains no license file, no README, and no attribution to xlibs or AlifePlus. The squad_on_update architecture and squad field patterns originate from AlifePlus and xlibs, which are licensed under the PolyForm Perimeter License requiring visible credit for derivative use.
For the full license analysis and the author's admissions regarding code copying, see the SISKI report.