Creating with Sidekicks: What Epic's Creature-Based Islands Stream Actually Teaches

Based on Epic's official "Creating in Fortnite" stream — Build Bonds with Creature-Based Islands, hosted by Dan Hutnick with Aiden (engineering lead for the sidekick NPC work), Bobby (director of product design driving the genre-growth initiative), and Alex Peace (animation department, supporting art lead). This is a VerseIsland synopsis of what the stream demonstrates, with deep links into the video for every claim. One honesty note up front: our verified API reference is currently synced to Release-41.10, which pre-dates parts of this feature drop — anything the stream shows that we cannot yet digest-verify is explicitly marked as pre-release below. No code in this article is presented as compilable.

What the stream covers

• Why Epic is pushing creature-based islands — the genre-growth initiative, and the July 23rd creature-games launch (~5:00)
• The new prop library — static meshes for pet props and collectibles, and the Collectible Object device workflow (~8:26)
• Farming assets — six crops, four growth states each, built for Verse-scripted farming sims (~14:48)
• Live demo: cosmetic sync + squad control — the new Verse-driven cosmetic swap and a click-to-command follower squad (~20:26)
• Feature recap — the new Sidekick type on the NPC spawner, four new animations, and the control-rig release (~25:29)
• Under the hood: character definitions — how sidekicks layer onto NPC character definitions, plus customization and scaling (~30:56)
• Q&A — spawn limits, scene-graph workarounds, and why the wisp didn't ship (~37:04)

Why creature-based islands, and when

Starting around 5:00, Bobby frames the release as the first of several genre pushes: Epic wants games in the ecosystem that aren't, in his words, "so BR adjacent or so shooter specific." The creature toolkit — tools, art, and animation content — shipped in v41.0, but sits under a publishing hold that lifts on July 23rd, when creature-based islands go live alongside a marketing moment with dedicated Discover rows. Two more genre pushes are planned later this year. Notably, your game does not have to use sidekicks to count as a creature game for the launch — custom creatures qualify too.

The new prop library: pet props and collectibles

From about 8:26, Alex walks the Content Browser through the new prop galleries (the "Plumpton" set, visible in the editor frames). Two things matter for builders:

They ship as static meshes, which means they slot into any device that accepts a custom static mesh. Alex demonstrates the flagship case: dragging a prop into the Collectible Object device's custom-mesh slot, turning any of the new props into an in-world collectible — the frames at that timestamp show the device's Interact Prompt and reward settings alongside the swapped mesh.

The set is themed around three design principles — nurture, partner, and master, as Alex and Bobby explain. That gives you pet food ("these would work with the current sidekicks and future sidekicks"), pet toys, nurture items like scale polish, health spray, and nail clippers, a grip-strength trainer ("not all of the sidekicks are animals"), and elemental charms themed fire, ice, and water — which Bobby calls out as ready-made hooks for assignable gameplay buffs. The supporting architecture kit takes a softer, 16th-century-European look aimed at cozy life-sim islands rather than the default Fortnite silhouette.

Farming assets: crops with four growth states

At roughly 14:48, Alex shows the farming set: six crop types, each authored in four distinct states — sapling, fully grown, wilted, and final produce — plus ground mounts and empty crates. The stated intent is direct: "within Verse, you could script things so that you can have these different things grow as your game goes along, and then you'll basically have a little farming simulator." Nothing here is a new API — it's mesh-state content deliberately shaped so that a Verse loop swapping meshes over time (or on watering, on timers, on player actions) reads as crop growth. Pair these with the collectible-device workflow above and the harvest loop practically designs itself.

The live demo: cosmetic sync and a command-able squad

Around 20:26 Aiden switches to his test-bed island for the stream's centerpiece.

Cosmetic sync (pre-release — verify before you build on it)

At 21:00, Aiden shows what he calls "this brand new feature called cosmetic sync — through a Verse API function, you can swap a cosmetic of the sidekick to be the one... that matches whatever character is playing." In the demo he shoots a ray cast at a placed dinosaur sidekick, and it transforms into his own equipped sidekick cosmetic (a dragon). The design intent he describes: there are about 30 sidekicks exposed to creators today, but IP sidekicks like SpongeBob aren't in the creator-facing list — with cosmetic sync, a player who owns one brings it into your island themselves.

Verification status — UPGRADED (Release-41.20 digest): the API the stream calls “cosmetic sync” is verified in the fresh digest as ApplyEquippedSidekickCosmetic(Agent : agent) — <transacts><decides>:void, i.e. a failable call (square-bracket it) that applies the player's equipped Sidekick look to a Sidekick NPC. “Cosmetic sync” was the presenter's description, not the identifier — a good reminder to always confirm spoken API names against the digest.

Follow behavior via ray casts and custom controls

The squad demo from about 21:50 is Aiden's own Verse-built behavior, not a shipped device preset — and that's the useful lesson. Clicking a sidekick designates it squad leader; clicking others adds them as followers ("they're all going to follow me now"); he then sends the squad to attack a target with a spread-out behavior so each follower picks a different victim, and recalls them with a bound key. The gameplay frames at 23:19 show his custom control HUD: Left Ctrl: Attack!, Space: Release!, plus Recall and Select bindings. He's explicit about the plumbing: "this is just using some basic hit traces". In other words: targeting is ray casting from the player, commands are custom input bindings, and the movement is standard NPC behavior scripting — all techniques available to you today on custom NPCs.

The demo also premieres the new animation set in action — a hurt reaction when the squad wanders into a damage volume, and a generic pounce "action" animation Aiden suggests reskinning as anything from a melee hit to a thrown fireball.

Feature recap: the NPC spawner's new Sidekick type

Bobby's recap at 25:29 is the cleanest summary of what actually shipped:

• Sidekicks as playable NPCs — "there's a new type on the NPC spawner that you can use to use sidekicks to do all the same things that a custom NPC could do". The npc_spawner_device itself is digest-verified in our reference; the new Sidekick character type on it is stream-shown. Note the stream teaches the NPC spawner here — not a creature-placer or creature-spawner walkthrough; those devices are never mentioned.
• Four new animations — eat, sleep, action/ability, and react, deliberately multi-purpose: sleep doubles as stunned or dazed, react as damage or surprise, action as attack, door-open, or chest interaction.
• Full customization — every shop-style option (base color, accent, quirk, gear), giving most sidekicks well over 100 permutations.
• Control rig — releasing in v41.20 on July 16th for the quadruped sidekicks first, so creators can author their own animations.

Under the hood: sidekicks are character definitions

At 30:56, Aiden opens the raw data: "sidekick is just a cosmetic modifier on top of an existing character definition" — the same asset that drives visuals and behavior for custom NPCs. Companion variant channels expose the customization (base, accent, details, and eye color, tactical gear), there's a scale modifier for toy-poodle-to-terrifying sizing, and — important limitation — these parameters are pre-configured, not yet settable at runtime.

One more forward-looking note, clearly flagged as unreleased in the stream: Aiden mentions a coming function to swap the character definition on an NPC spawner using Verse ("I won't comment on which release"), so you could recycle one spawner plus respawn logic instead of pre-configuring many. Shown in the stream; not yet in our verified API reference — treat as pre-release until the next digest sync.

Also confirmed: players and creators don't need to own a sidekick cosmetic to use the full library in an island.

Q&A: limits and workarounds worth knowing

• Spawn limit: same as normal NPCs — about 90.
• Scene graph: attaching meshes (hats!) to sidekicks works via scene graph, but asset reflection with sidekicks is a known limitation; Aiden suggests the progress-based mesh device as a swap workaround.
• Behavior parity: "anything you can do with a custom NPC you can do with these" — including path following; there's nothing special about sidekick behavior.
• Why no wisp/sprite: its behavior was too predefined; the suggested pattern is to hide the sidekick's mesh and swap in your own — angel, demon, fireball — and script the travel yourself.

The takeaway

The stream's real curriculum is a pattern, not a device: sidekicks are cosmetic skins over the NPC character-definition system you already know, commanded with ordinary Verse tools — hit traces for targeting, input bindings for orders, behavior scripts for movement — and dressed with a prop library built to make collect/nurture/farm loops cheap to assemble. Watch the squad demo twice; that's the piece worth rebuilding on your own island. And before you write a line against ApplyEquippedSidekickCosmetic or the spawner-side definition swap, wait for the fresh digest — we'll update this page the moment those symbols verify.