[{"_1":2,"_192":-5,"_193":-5},"loaderData",{"_3":4,"_24":25,"_161":162,"_183":184},"root",{"_5":6,"_19":-7,"_20":21},"publicEnvVariables",{"_7":8,"_9":10,"_11":8,"_12":13,"_14":15,"_16":10,"_17":18},"VITE_SITE_URL","https://thunderstore.io","VITE_BETA_SITE_URL","https://new.thunderstore.io","VITE_API_URL","VITE_COOKIE_DOMAIN",".thunderstore.io","VITE_AUTH_BASE_URL","https://auth.thunderstore.io","VITE_AUTH_RETURN_URL","VITE_CLIENT_SENTRY_DSN","https://788172c9ed4c013a8dda3b01277af451@o578525.ingest.us.sentry.io/4509032431157248","currentUser","config",{"_22":8,"_23":-7},"apiHost","sessionId","p/packageListing",{"_26":27,"_52":53,"_84":85,"_151":157,"_160":-7},"community",{"_28":29,"_30":31,"_32":33,"_34":35,"_36":-5,"_37":38,"_39":40,"_41":42,"_43":44,"_45":-5,"_46":47,"_48":49,"_50":51},"name","GTFO","identifier","gtfo","short_description","GTFO is a hardcore cooperative horror shooter that throws you from gripping suspense to explosive action in a heartbeat. Stealth, strategy, and teamwork are necessary to survive in your deadly, underground prison. Work together or die together.","description","Mod database and API for downloading GTFO mods","wiki_url","discord_url","https://discord.com/invite/rRMPtv4FAh","datetime_created","2021-02-28T23:37:33.263865Z","hero_image_url","https://gcdn.thunderstore.io/live/community/gtfo/gtfo-bg-1920x620.webp","cover_image_url","https://gcdn.thunderstore.io/live/community/gtfo/gtfo-cover-360x480.png","icon_url","community_icon_url","https://gcdn.thunderstore.io/live/community/gtfo/gtfo-icon-192x192.png","total_download_count",5231377,"total_package_count",1031,"communityFilters",{"_54":55,"_82":83},"package_categories",[56,62,66,70,74,78],{"_28":57,"_58":59,"_60":61},"Rundowns","slug","rundowns","id","43",{"_28":63,"_58":64,"_60":65},"Client Mods","client-mods","44",{"_28":67,"_58":68,"_60":69},"Rundown Mods","rundown-mods","45",{"_28":71,"_58":72,"_60":73},"Dev Tools","dev-tools","46",{"_28":75,"_58":76,"_60":77},"Modpacks","modpacks","47",{"_28":79,"_58":80,"_60":81},"Libraries","libraries","48","sections",[],"listing",{"_86":87,"_89":31,"_34":90,"_91":92,"_45":93,"_94":95,"_96":95,"_97":95,"_98":99,"_28":100,"_101":102,"_103":104,"_105":106,"_107":29,"_39":108,"_109":110,"_111":112,"_140":141,"_142":143,"_144":145,"_146":95,"_147":148,"_149":150,"_151":152,"_155":156},"categories",[88],{"_28":67,"_58":68,"_60":69},"community_identifier","Allows Rundown Developers to place Shuttleboxes (aka Dumbwaiters, like from R7B1, R8E1, and R8E2) and give them a number of possible features","download_count",14,"https://gcdn.thunderstore.io/live/repository/icons/JarheadHME-ActuallyUsableShuttleboxes-1.0.0.png","is_deprecated",false,"is_nsfw","is_pinned","last_updated","2025-10-29T03:04:54.406579Z","ActuallyUsableShuttleboxes","namespace","JarheadHME","rating_count",2,"size",1099221,"community_name","2025-10-29T03:04:53.944617Z","dependant_count",1,"dependencies",[113,122,128,134],{"_89":31,"_34":114,"_45":115,"_116":117,"_28":118,"_101":119,"_120":121},"My cool library mod for plugin developers","https://gcdn.thunderstore.io/live/repository/icons/Amorously-AmorLib-1.0.5.png","is_active",true,"AmorLib","Amorously","version_number","1.0.5",{"_89":31,"_34":123,"_45":124,"_116":117,"_28":125,"_101":126,"_120":127},"BepInEx pack for GTFO. Preconfigured and includes Unity Base DLLs.","https://gcdn.thunderstore.io/live/repository/icons/BepInEx-BepInExPack_GTFO-3.2.2.png","BepInExPack_GTFO","BepInEx","3.2.2",{"_89":31,"_34":129,"_45":130,"_116":117,"_28":131,"_101":132,"_120":133},"The premier in GTFO DataBlock editing ;^)","https://gcdn.thunderstore.io/live/repository/icons/dakkhuza-MTFO-4.6.2.png","MTFO","dakkhuza","4.6.2",{"_89":31,"_34":135,"_45":136,"_116":117,"_28":137,"_101":138,"_120":139},"Color the texture in real time","https://gcdn.thunderstore.io/live/repository/icons/GTFOModding-TexturePainterAPI-1.0.2.png","TexturePainterAPI","GTFOModding","1.0.2","dependency_count",5,"download_url","https://thunderstore.io/package/download/JarheadHME/ActuallyUsableShuttleboxes/1.0.0/","full_version_name","JarheadHME-ActuallyUsableShuttleboxes-1.0.0","has_changelog","install_url","ror2mm://v1/install/thunderstore.io/JarheadHME/ActuallyUsableShuttleboxes/1.0.0/","latest_version_number","1.0.0","team",{"_28":102,"_153":154},"members",[],"website_url","https://github.com/JarheadHME/GTFO-ShuttleboxPlugin",{"_30":158,"_28":102,"_159":-5},12182,"donation_link","permissions","p/tabs/Wiki/Wiki",{"_163":164,"_180":31,"_181":102,"_182":100,"_58":-7,"_160":-7},"wiki",{"_60":165,"_166":167,"_58":168,"_39":169,"_170":171,"_172":173},"2295","title","JarheadHME/ActuallyUsableShuttleboxes Wiki","2295-jarheadhmeactuallyusableshuttleboxes-wiki","2025-10-29T03:10:28.646803Z","datetime_updated","2025-10-29T03:10:28.652916Z","pages",[174],{"_60":175,"_166":176,"_58":177,"_39":178,"_170":179},"4243","json file documentation","4243-json-file-documentation","2025-10-29T03:10:28.650869Z","2025-10-29T03:10:28.650886Z","communityId","namespaceId","packageId","p/tabs/Wiki/WikiFirstPage",{"_163":185,"_188":189,"_180":31,"_181":102,"_182":100,"_160":-7},{"_60":165,"_166":167,"_58":168,"_39":169,"_170":171,"_172":186},[187],{"_60":175,"_166":176,"_58":177,"_39":178,"_170":179},"firstPage",{"_60":175,"_166":176,"_58":177,"_39":178,"_170":179,"_190":191},"markdown_content","# Creating the files\n\nInside your Rundown's MTFO Custom folder, create a folder called `ShuttleboxData`. Then, any .json files inside will attempt to be parsed into the relevant shuttlebox data, the format of which will be detailed below.\n\n

\n\n

\nAn example ShuttleboxData json file for spawning a single shuttlebox\n

\n\n### Below is an example filled out json file that will spawn a single shuttlebox using markers\n\nThe types of non-primitive, non-custom fields, or fields that are DataBlock IDs, are annotated\n\n```jsonc\n[\n {\n \"MainLevelLayoutID\": 0, // LevelLayoutDatablock ID\n \"Shuttleboxes\": [\n {\n \"DebugName\": \"NameOfShuttlebox\",\n\n \"ZonePlacement\": { // DumbwaiterPlacementData\n \"PlacementWeights\": { // ZonePlacementWeights\n \"Start\": 0.0,\n \"Middle\": 0.0,\n \"End\": 0.0\n },\n \"AreaSeedOffset\": 0,\n \"MarkerSeedOffset\": 0\n },\n\n \"DimensionIndex\": \"Reality\", // eDimensionIndex\n \"Layer\": \"MainLayer\", // LG_LayerType\n \"LocalIndex\": 0, // eLocalZoneIndex\n\n \"AbsolutePosition\": false,\n \"Position\": { // Vector3\n \"x\": 0.0,\n \"y\": 0.0,\n \"z\": 0.0\n },\n \"Rotation\": { // Vector3\n \"x\": 0.0,\n \"y\": 0.0,\n \"z\": 0.0\n },\n\n \"Decorations\": { // Dictionary\n \"StraightShort\": false,\n \"TurnShort\": false,\n \"StraightLong\": false,\n \"TurnLong\": false,\n \"DoubleTurnRight\": false,\n \"DoubleTurnLeft\": false,\n \"Backward\": false,\n \"Angled\": false,\n \"Base\": false\n },\n \"Colors\": {\n \"MainColor\": { // Color\n \"r\": 0.5,\n \"g\": 1.0,\n \"b\": 0.0,\n \"a\": 0.8\n },\n \"AccentColor\": \"#FFFF\", // Color\n \"SerialColor\": \"#FFFFFF\" // Color\n },\n\n \"LinkID\": -1,\n \"IsClosedAtStart\": false,\n\n \"ValidInsertItems\": [\n {\n \"ItemID\": 0, // ItemDataBlock ID\n \"ActionOnInsert\": \"None\", // enum - `0 = \"None\", 1 = \"Transfer\", 2 = \"Consume\", 3 = \"ConsumeAndRemainClosed\"`\n \"Events\": [ // \n {\n \"Type\": 0,\n \"Trigger\": \"OnStart\" // What fill this with is important, see \"Event Triggers\" section\n }\n ]\n }\n ],\n\n \"SpawnedItem\": {\n \"ItemID\": 0, // ItemDataBlock ID\n \"IsAvailableAtStart\": false,\n \"IsWardenObject\": false,\n \"ChainedObjectiveIndex\": 0,\n \"ShowOnTerminalList\": false,\n \"Uses\": 0\n }\n }\n ]\n }\n]\n```\n\n

\n\nThis template will generate if the `ShuttleboxData` folder is not present \n\n# General Layout\nEach file contains a list. The type of this list only has two fields:\n* `MainLevelLayoutID`\n* `Shuttleboxes`\n\n`Shuttleboxes` is the list containing the actual Shuttlebox data which will be detailed below, and `MainLevelLayoutID`, as the name would imply, is the `LevelLayoutDataBlock` ID that, when the currently loading level has this as its Main Layer data, then shuttleboxes will start to be placed.\n\n# Shuttlebox Information\n\nFirst up, which doesn't connect with anything else in particular, is `DebugName`. The primary use of this is to label which shuttlebox is which in your files, however it does serve two other important functions.\n1. It's also used when printing errors in the console. If anything is *detected* as an error, then it will be printed, and `DebugName` will be included to specify which shuttlebox had an issue.\n2. It also determines the name of *World Event Objects* attached to it which the developer can use to interact with the shuttlebox via Events. This will be detailed further down in the [Interaction Events](#interaction-events) section.\n\n## Placement Data\n\nThere are two different ways that you can spawn shuttleboxes in: Absolute, and Marker. You decide which you want to use by setting the `AbsolutePosition` field to either `true` for Absolute, and `false` for Marker. \n\nShuttleboxes are placed at the end of the (first) `LG_PopulateFunctionMarkersInZoneJob` step of building a zone, so no matter what, if a level does not contain a zone that matches the specifications of the shuttlebox's Global Zone Index (specified by `DimensionIndex`, `Layer`, and `LocalIndex`), then the shuttlebox will not spawn, even when in Absolute mode.\n\nWhen in Marker mode, then all other fields are used to randomly select and use markers similar to how most normal level generation functions work. `ZonePlacement` functions similarly to the parts of [TerminalPlacementData](https://gtfo-modding.gitbook.io/wiki/reference/nested-types/terminalplacementdata) which are not specific to terminals themselves. To summarize:\n* `PlacementWeights` has the fields `Start`, `Middle`, and `End` which help determine which area of the zone is selected\n* `AreaSeedOffset` offsets the seed used to determine which area of the zone is selected\n* `MarkerSeedOffset` offsets the seed used to determine which marker inside the area is selected to spawn the shuttlebox.\n * ^{Just as a note, shuttleboxes look for markers in the room that could have Disinfection Stations.}\n\nWhen in Absolute mode, only `AreaSeedOffset` is taken into account, and this, in conjunction with the Global Zone Index, determines under which Course Node (room) the Shuttlebox and items inside it are in, which is important for pinging and culling purposes. In this case, `AreaSeedOffset` is the Area Index of the room in the zone, i.e 0 = area A, 1 = area B, 2 = area C, etc.\n\n^{I'm reasonably sure the shuttleboxes won't actually cull, so it's mainly for the items in it, and for knowing what GameObject the shuttleboxes get placed under.}\n\nFinally, the `Position` and `Rotation` fields do roughly what you probably expect, but do function slightly different depending on if you're in Absolute or Marker mode. \n\nWhen in Absolute mode, then `Position` is taken as the actual coordinates. You can use F2 in CConsole to get coordinates where you want. As a quick summary:\n* x: negative is West, positive is East\n* y: negative is Down, positive is Up\n* z: negative is South, positive is North\n\nWhen in Marker mode, then it's relative to the marker (local position). The following descriptions summarize which way it moves when you're looking at the front\n* x: negative pushes it to the right, positive to the left\n* y: negative moves it down, positive up\n* z: negative pushes the shuttlebox backwards, positive will bring it forwards\n\nFor `Rotation` when in Absolute mode, the front of the shuttlebox is facing North when it's set to 0, 0, 0. All of these descriptions will be describing the changes made as though you're looking at the front of the shuttlebox\n * x: negative tilts the top of the shuttlebox backwards (away from you), positive tilts it towards you\n * y: negative twists the shuttlebox to the right (hole will turn West), positive twists to the left\n * z: negative tilts the top of the shuttlebox to the left (East), positive tilts to the right\n\n# Visuals\n\nThere are two types of visual modification you can do to the shuttleboxes. The first is Decorations. These are additional little pieces that get added on to the shuttlebox. If you set a specific decorate's field to `true`, then it will be made visible. The template above in [Creating the files](#creating-the-files) has a comprehensive list all that are available, and they go inside the `Decorations` field as key-value pairs. \n\n

Here is a list of the names of each decoration and what they look like

\n\n

StraightShort

TurnShort

StraightLong

TurnLong

DoubleTurnRight

DoubleTurnLeft

Backward

Angled

Base

\n\n

\n\nYou can also change the colors of the main shuttlebox body, and the terminal serial. These go under the `Colors` field, which has 3 more fields of its own: `MainColors`, `AccentColor`, `SerialColor`. All of these are the `Color` type, and can be input in one of two ways. First is with a Hex code, such as `#D96B00C0`. This can follow any of the following formats:\n* #RGB\n* #RGBA\n* #RRGGBB\n* #RRGGBBAA\n\n

You can also define a color with a json structure, such as this.

\n\n```json\n\"AccentColor\": {\n \"r\": 0.8,\n \"g\": 0.7,\n \"b\": 0.65,\n \"a\": 0.8\n}\n```\n\n

\n\n# Spawning with an item\n\nShuttleboxes can spawn a single item with them. To do so, the `SpawnedItem` field is used. Inside, you can provide the following:\n* `ItemID` - The ItemDataBlock ID of the item you want to spawn. \n * If it's any `InventorySlot` other than `ResourcePack` (4), `Consumable` (5), `ConsumableHeavy` (6), `InLevelCarry` (8), or `InPocket` (7), then it can't be spawned. \n* `IsAvailableAtStart` - `true` or `false`, if `false` then the item will be hidden away until the Summon event is executed (see [Interaction Events](#interaction-events)), otherwise it will be ready and waiting in the shuttlebox.\n* `IsWardenObjective` - As it sounds, if `true` then this spawned item will be considered a Warden Objective item. If the objective itself isn't set up for this, then it just makes the objective progression noise when you interact with it.\n* `ChainedObjectiveIndex` - If you know what chained objectives are, you know what this is. Otherwise, leave this at 0.\n* `ShowOnTerminalList` - Only relevant if `IsAvailableAtStart` is `false`.\n * If this field is false, then the hidden item to be summoned later won't be visible on terminals, nor be Query or Ping-able. If it's a WardenObjective item, then it could still show up in the progression text in `[ALL_ITEMS]`. Outside of text formatted like this, the only place (I believe) it can show up is on the storing shuttlebox's Query text. Behavior will return to normal once it is summoned.\n * If this field is true, then the item will still show up on terminal lists, be listed as inside the same zone as the shuttlebox, however if you try to Ping it inside that zone, it will be out of range. Additionally, if you Query the item, then it will succeed, and show that it is a `Stored Shuttlebox Item`, with its location listed as `Inside SHUTTLEBOX_XYZ`.\n* `Uses` - This field is to determine how many uses a resource pack or consumable will have. If it's any other inventory slot, it doesn't do anything.\n\n# Functionality\n\nFirst, the two remaining trivial fields are:\n* `LinkID` - When two shuttleboxes have the same LinkID (and it's 0 or greater), then they will be the destination for each other (see the `Transfer` action below)\n * Only two shuttleboxes can share the same `LinkID`. Any subsequent shuttleboxes with that ID will function as though it's unlinked.\n* `IsClosedAtStart` - As the name suggests, this determines whether the shuttlebox is open or closed when the level starts.\n\nThe bulk of shuttlebox functionality comes from defining `ValidInsertItems`. This is a list of another type which has the following fields:\n* `ItemID` - The ItemDataBlock ID of the item that these actions will occur for.\n * If you leave this at 0, then it will accept all colored keys that spawned in the level.\n* `ActionOnInsert` - This is an enum which determines the main thing the shuttlebox will do with the item. The enum values are as follows:\n * 0 - `None`\n * This shuttlebox will not close at all, but the item will still be marked as valid to be inserted into the shuttlebox, and events can still execute (see [Event Triggers](#event-triggers))\n * 1 - `Transfer`\n * If this shuttlebox and another both have the same `LinkID`, then when this item in inserted (and the destination box isn't busy or full), both boxes will close, and the item will be transferred to the destination box.\n * 2 - `Consume`\n * When the item is inserted into the shuttlebox, then the box will close, then reopen with the item being functionally removed from the map.\n * 3 - `ConsumeAndRemainClosed`\n * As the name implies, it's the same as the `Consume` action, however the shuttlebox will not reopen on its own. (It can still be reopened with the Open event (see [Interaction Events](#interaction-events)))\n* `Events` - List of [WardenObjectiveEventData](https://gtfo-modding.gitbook.io/wiki/reference/nested-types/wardenobjectiveeventdata) to execute at the different triggers.\n\n## Event Triggers\n\nTo determine when you want events from a shuttlebox item insertion to fire, you need to set the `Trigger` field to one of the following:\n* 1 - `OnStart`\n * Fires the events as soon as the item is inserted into the box. Mostly for timing, but can be useful when using the `None` action.\n* 2 - `OnMid`\n * Fires the events when the shuttlebox finishes closing and most of the sounds from closing are done playing. This is to indicate that the item has been \"dealt with\" by the shuttlebox.\n * `OnMid` will fire from the *sending* shuttlebox when using the `Transfer` action. It will not on the destination shuttlebox.\n* 3 - `OnEnd`\n * This fires when the defined item is *picked up* out of the shuttlebox by the player. Potentially useful for, for example, starting an error alarm when the players have picked up an important item.\n\n# Interaction Events\n\nThe last way you can interact with a shuttlebox is with the three Interaction events. You trigger these by running a Type 15 (`AnimationTrigger`) event with a specific `WorldEventObjectFilter` based on the shuttlebox's defined `DebugName`. The following are the `WorldEventObjectFilter` names if the shuttlebox had a `DebugName` of `Example Name`:\n* Open - `EVT_ShuttleboxPlugin_ForceOpen_Example Name`\n* Close - `EVT_ShuttleboxPlugin_ForceClose_Example Name`\n* Summon - `EVT_ShuttleboxPlugin_SetPickupAlign_Example Name`\n\n## IMPORTANT!\n\n**`AnimationTrigger` events don't actually trigger the animation if the `Enabled` field on the event is not set to true! So if you're trying to use these interaction events, then make sure you set `Enabled` to `true` on your event!**\n\n# LiveEdit\n\nThe `ShuttleboxData` files will reload when you save them (with a 1.5s cooldown), however there are only four fields that will properly LiveEdit in level: `Position`, `Rotation`, `MainColor`, and `AccentColor`. (Note that `SerialColor` is not included, for a weird limitation that I didn't really understand. The actual `TextMeshPro` vanishes by the time you get into the level, so its color can't just be reset again.)\n\nWhen the files are reloaded, the full list of shuttleboxes gets reset, and when reloading everything, if the MainLevelLayout of the current level gets shuttleboxes added to it, it will run through the newly reloaded shuttleboxes and the current shuttleboxes in the level. If a level shuttlebox's `DebugName` matches a reloaded shuttlebox's `DebugName`, then that shuttlebox will get its `Position`, `Rotation`, `MainColor`, and `AccentColor` all updated.","actionData","errors"]

Log in to Thunderstore

Details

Categories

json file documentation