Open the project folder
Choose your island project folder as the working folder in SentryEdit and pick Ask first.
Most first Verse projects start small. A player presses a button and receives an item. Here is how a change travels from your request to a live test, with SentryEdit editing the files and you making the decisions at 4 clear points.
Choose your island project folder as the working folder in SentryEdit and pick Ask first.
Write the task in plain words, for example a button that grants an item.
Read every proposed edit, accept the lines you want and reject the rest.
Build from the Verse menu, push changes to a live edit session and play.
project folder6 filescreative_device2 matchesreward_button.verse+18 linesreward_button.verse18 linesusing { /Fortnite.com/Devices }
using { /Verse.org/Simulation }
using { /UnrealEngine.com/Temporary/Diagnostics }
reward_button := class(creative_device):
@editable
Button : button_device = button_device{}
@editable
Granter : item_granter_device = item_granter_device{}
OnBegin<override>()<suspends> : void =
Button.InteractedWithEvent.Subscribe(OnPressed)
OnPressed(Agent : agent) : void =
Granter.GrantItem(Agent)
Print("Item granted")The device holds two placed devices in @editable fields. OnBegin runs when the game starts and subscribes OnPressed to the button's InteractedWithEvent. When a player presses the button, the item granter gives that player its item.
Looking for creation help with a Fortnite Creative map? Start with a plan, not code. In Plan only mode SentryEdit uses web_search and http_get to read Epic's documentation for Verse and your devices, then write_file saves a short checklist of 5 steps into your project folder, for example which devices to place and which Verse file to write first. Nothing in your project changes. Work through the list one step at a time, ask the agent to explain any word you do not know, and test after every step.
The first time your Fortnite UEFN map is published, a checklist helps. Ask SentryEdit to run grep for leftover Print lines, list unused @editable fields and read_file each device once more. You get a report of 3 or 4 items, and Ask first lets you approve each fix. Publishing itself happens in Epic's Creator Portal, where the island gets its island code, and Epic's Island Creator Rules apply. Read the diff, rebuild and test in a live edit session first.