Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Beyond Our Worlds | ShellCore Command Mod

Create and run custom worlds with expanded built-in retro editors for ShellCore Command. · By FoeFear

[Canvas Trial] [Major] Strike Drone Shenanigans

A topic by MattSpeedy created May 18, 2025 Views: 83 Replies: 3
Viewing posts 1 to 2
(2 edits)

NOTICE: This wasn't a bug, it was me being a dingus. Please clear your item defaults before doing the Canvas Trial.


This bug report applies for the Canvas Trial custom world, on version Gamma 1.4.0 of Beyond our Worlds.

I tried to place Strike Drones(as instructed by the custom world), and instead I got some really odd cores.

To recreate, place down Strike Drones and set their faction to Crimson Infected, then test the world.

(I genuinely have no goshdanged clue how or why this happened, and not even the console had anything to say about it.)

Developer (1 edit) (+1)

Check the JSON of those strike drones. If there is a blueprint in it, remove it. This might be due to you putting a ship name or JSON code in the item defaults (there is a button called Change Item Defaults in Item Mode).

(1 edit)

There is a blueprint pre-baked into every strike drone when placed down, for some reason.

I haven't touched the item defaults at all since downloading the world.
Consider removing the item defaults(which may have been left over) in the next update to the world.

(unsure if that's how that works; I might be way in over my head, though fellow newcomers to world creation shouldn't have to deal with this in the first place)

Developer(+1)

Like what I said earlier, remove the JSON code from the item defaults and just leave it blank (refer to image below). Item or sector defaults that were changed from prior versions are kept in the later versions. That's what it looks like in your case. I tested this on another device using the latest version, and this bug does not exist.