Vortex Scripting Core Mod FAQ

Open your inventory and look for the Vortex Scripting Core interface or keybind (check your controls menu). The in-game script editor will appear with code completion and hints enabled by default.

Server-side scripts control game logic, NPC behavior, and quest progression that all players see; client-side scripts handle visual effects, UI, and player-specific interactions. Most quest and NPC systems should run on the server to stay synchronized.

Yes, the mod supports glTF, GLB, OBJ, and Bedrock geo.json formats. Import your model through the asset manager or script editor, then assign it to your NPC in the dialogue/animation system.

Use the animation editor to set up state transitions with expression language triggers—for example, trigger 'walk' when the NPC moves, or 'talk' when dialogue plays. The mod syncs these states between client and server automatically.

Yes, use the asset manager tool to view and override client and server resources on the fly. Changes apply without restarting, making it ideal for testing custom content.

Use event listeners in your script to detect player actions (like right-clicking, entering an area, or breaking a block), then execute your custom logic. The mod provides built-in hooks for common player interactions.

Yes, the dialogue system supports multiple-choice branching. Each choice can trigger different scripts, set variables, or progress different quest paths—all managed through the interactive dialogue editor.

Create separate script files for different systems (NPCs, quests, cutscenes, events) and use the script editor's file management to keep them organized. Reference other scripts using the mod's import or function-call system to avoid duplication.