[Utilities] Starfield EZ Scripter

[Wolfe6900]

Starfield EZ Scripter

View File

---

Starfield_EZ_Scripter_v3:

 

What can you do?

 

TAB 1: AI Connect
- This is a tool with a built-in prompt so AI knows you're talking about modding Starfield. Example, instead of saying:
"I want you to design a script for the Starfield Creation Kit that disables on object"
You would instead just say "disable an object"
- This can attach to ChatGPT, Grok or DeepSeek's API if you have a full account.
(This is not fully tested, since I don't have full accounts with this ability to test them)

 

TAB 2: Script Helper
- This is a tool to help you build scripts from scratch as a Novice Modder:

- Assign a prefix: If all your scripts for your mod called "JohnnysMod" should start with "JH_"; this will apply it.

- Scriptname: Write a scriptname - if you name your script "DisableChair" with the prefix above, it would be called "JH_DisableChair"

- Categories: I've come to notice that I use 3 main categories in scripting: 
1. Triggers (a box the Player walks into and activates the script)
2. Activators (The Player uses an activator like a book or something)
3. Quest (The player speaks to someone, after it's finished, something happens).

- Dependent on the 3 categories above, you may get more options. For example, triggers: you may have a flag for it to only trigger once. That way, it doesn't keep triggering every time the player steps into the invisible trigger box.

- Quests: Quests have an "Add", "Duplicate", "Remove" button and allow you to assign the priority. For example, you wanted the script to:
1. Add an Item to the Player
2. Show a popup message to the Player
3. Unlock a door
You could now do this, so an example of it running would look like:
1. Give a medpack to Johnny (the Player)
2. Tell Johnny, "YOU HAVE A MEDPACK!"
3. Unlock a Door for Johnny to go through

- These can also be in different sequences: For example, you can have 2 sequences in one script. A good example of this is if you'd like a single script to lock and unlock doors, but you would want to call it differently. You could use one dialogue fragment to unlock a door and a different dialogue fragment to lock the door, but all in one script. Additionally, this tool would provide both dialogue fragments needed to call this.
For an example: you could talk to an NPC and say either:
"Lock this door!" - call the lock function
"Unlock this door!" - call the unlock function
These would both be in the same script.

-Edit/Debug flags: These let you edit the script to how you'd like it and make it so the script always shows debugs. This is good for testing because Debugs can show you where something failed, especially in a sequence. For example, you:
1. Give a medback
2. Display a message
3. Unlock a door
This would say "Medpack given", "Message Displayed", "Could not open door due to XYZ" letting you know some parts worked, but some didn't pinpointing errors.

- Cull: This removes anything in the script that is not needed for the script to function. A lot of modders like to add little notes, extra spaces, etc., to their mods. This serves to eliminate them and show you what you need to get the mod to function, and nothing more. A good tool to clean up a heavy worded script or learn what is actually needed.

 

Tab 3: Useful Fragments:
When using scenes and dialogues to make things happen, these fragments are often used. This is just a quick copy/paste tool instead of writing and remembering the verbiage when calling.

 

Tab 4: Script Editor:
This allows you to pull entire scripts and edit/save them. This is more for an advanced modder, but also a useful tool if shortening scripts and etc.

---

• Submitter
  Wolfe6900
• Submitted
  09/06/2025
• Category
  Utilities
• Requirements
  None