Fabricator 9000

What is this?

This Package provides a world entity and a frontend that lets you browse a list of user-set templates, and use resources to Spawn them.

Video demo:


How do I use it?

Simply interact with the Fabricator’s control console once it’s set up and in your game.

How do I get started?

Setup guide

Setting up the Player and User templates:

  1. In Advanced View, in the top right corner, search for “Player”
  2. Add fab_playerCarryScript, fab_playerInventoryView, fab_playerShopView as children of Player.
    It should look like this:
  3. Search for “User”.
  4. Add fab_userFabricatorUI and fab_userInventory as children of the User.
    It should look like this:

Setting up the Fabricator itself:

  1. Search for “Fabricator” in Crayta’s Community tab, and install the package you find.
  2. Drag the “Fabricator 9000” template in the game’s world
  3. Navigate to the fab_Controls entity in the item’s hierarchy (fabtest1 > input_mesh > fab_controls).
  4. Edit the existing shopBuyItem scripts attached to that entity so they show the items you want to generate. For each object that you want the player to be able to fabricate, do the following: replace itemTemplate with your desired object’s template, buyCurrency template with the currency that should be used to build it, buyPrice with how much of it will be required, and itemDescription with a description of it. Add more if needed.
  5. For each object, add each template to the Holograms list in shopScript; you may need to make a specific version of it to be used exclusively for this task, resized and positioned accordingly, depending on the complexity and shape of the template being used.

How does this package work?

This package relies a lot on modified versions of Crayta’s default Inventory and Shop packages. For more on those, check the following two links:

What do I REALLY need to pay attention to?

Few things.

  1. Do not edit the maxItems value in the player’s shop script.
  2. Do not put more than one item in each page. The system is set up so that each item gets its own page.
  3. The project’s troubled development process means it comes along with some past versions of certain templates and similarly named scripts. Please make sure the assets you put in your game come from the Fabricator 9000 package, and nowhere else. The correct assets should also be following pretty clear naming conventions.
  4. I had trouble uploading the package at the end; the current version may only work correctly if it’s placed exactly at 0, 0, 0 in the game world. No, I don’t understand it either. Hopefully this will be resolved soon. The description and comments may also be slightly off. If you’re a judge for the Jam, the correct package is Fabricator 9000 in the showcase. Apologies for the trouble.

Unfortunately, I wasn’t able to code around these limitations due to time constraints, and the fact that I was completely unable to upload . Mind, the package works perfectly if you just don’t mess with any of the stuff I just mentioned. Hopefully, by the next update, these warnings won’t be necessary. But for now, pay attention to the above.