How to add create "incomplete" item for sequenced assembly?

[cerulean shore]

I haven't used kubejs for making any sequenced assembly recipes and cant figure out how to do so

[alpine stratus]

Once your ticket has been resolved, please close it with </ticket close:1054771505520717835> command!

[thick holly]

https://wiki.latvian.dev/link/72#bkmrk-sequenced-assembly

[cerulean shore]

is this the new 1.19 version or 1.18-?

[thick holly]

The code is 1.19

[cerulean shore]

thanks

[thick holly]

lemme know if you need help

[cerulean shore]

i dont see the place to enter the texture id

[thick holly]

Its your item id

like kubejs:uncomplete_example_item

[cerulean shore]

but how do i tell it which texture this is using?

[thick holly]

the texture name is the exact as the item

in you kube assets

like

incomplete_example_item.png -> kubejs:incomplete_example_item

[cerulean shore]

ahh i have to add the asset to kube too, not just able to link to another mod texture?

[thick holly]

You can make it link to another mod

just do mod_id:item_name

[cerulean shore]

see im trying to recreate the FTBStoneblock way of making the processors for AE and RS

[thick holly]

You could make your own incomplete item

[cerulean shore]

do you have to do "onevent ect" for each item or is there a way to list

[thick holly]

like what?

[cerulean shore]

i was on my 1.18 one instead of 1.19. itll be easier on the 1.19 since all the info is for it

[thick holly]

So what do you mean?

I'm lost

[glacial plover]

╰( ͡° ͜ʖ ͡° )つ──☆:・ﾟ˜”°•.˜”°• Many Help •°”˜.•°”˜*
Please provide a description of your issue with as much detail as possible. If you have an issue with a script provide the script. Explain what you can see happening and what you expect to happen. Be specific!

Tell us what is happening, we already know it "doesn't work".
Avoid using words like "it", tell us exactly what "it" is.
Don't assume anyone knows what you are talking about, be specific.

Provide screenshots or video of the issue if possible.

Provide the log.

[cerulean shore]

so the 1.18 and 1.19 coding processes are different and i got myself mixed up from looking at names and stuff.

so this is what i have right now but how would i go about telling it which texture to use for that

[thick holly]

Yeah, onEvent was removeed

[thick holly]

You need the mod id for the first part

The game knows what texture to use

[cerulean shore]

where abouts is that inserted

[thick holly]

towards the bottom

[cerulean shore]

so this would be correct right?

[thick holly]

no

Can you send me that code so I can make it better

and to work

[cerulean shore]

hahaha sure thing

[glacial plover]

Paste version of registry.js from @cerulean shore

[thick holly]

That is so wrong ;-;

Do you havehttps://www.curseforge.com/minecraft/mc-mods/kubejs-create installed?

[cerulean shore]

i do

[thick holly]

How many times does the user have to go thru the process

and what steps

If you look at https://wiki.latvian.dev/link/72#bkmrk-sequenced-assembly you can see how to

And it goes in server scripts btw

[cerulean shore]

thats not what the site says and not the way other packs have it... thats just the making of the "incomplete" item not the process recipe

[thick holly]

OOOHHH

[thick holly]

In here you would do

StartupEvents.registry('item', e => {
    e.create('incomplete_raw_basic_processor')
    .displayname(Component.literal('Incomplete Raw Basic Processor')
})

for example

When you want to use the item, you do kubejs:incomplete_raw_basic_processor

[copper path]

StartupEvents.registry('item', e => {
    e.create('refinedstorage:incomplete_raw_basic_processor', 'create:sequenced_assembly').displayname(Component.literal('Incomplete Raw Basic Processor').texture('refinedstorage:incomplete_raw_basic_processor')
        
})

console.info('Hello, World! (Loaded startup scripts)')

so the name would be in a refinedstorage folder and the texture would be called incomplete_raw_basic_processor.png or something like that (if im not wrong)

[cerulean shore]

then why is that not in the example........

This is the process im looking for with each but with a press after the redstone deployer

[copper path]

ok

can you give me the names of the first 2 item of the deployers and tell me how many times it loops

[cerulean shore]

"processor_binding" "silicon"

[copper path]

ok

    e.custom({
        "type": "create:sequenced_assembly",
        "ingredient": {
          "item": "minecraft:iron_ingot"
        },
        "transitionalItem": {
          "item": "minecraft:iron_ingot"
        },
        "sequence": [
        {
          "type": "create:deploying",
          "ingredients": [
            {"item": "minecraft:iron_ingot"},
            {"tag": "refinedstorage:processor_binding"}
          ],
          "results": {"item": "kubejs:uci1"}
        },
        {
          "type": "create:deploying",
          "ingredients": [
            {"item": "minecraft:iron_ingot"},
            {"item": "refinedstorage:silicon"}
          ],
          "results": {"item": "kubejs:uci1"}
        },
        {
          "type": "create:deploying",
          "ingredients": [
            {"item": "minecraft:iron_ingot"},
            {"tag": "forge:dusts/redstone"}
          ],
          "results": {"item": "kubejs:uci1"}
        },
        {
          "type": "create:pressing",
          "ingredients": [{"item": "minecraft:iron_ingot"}],
          "results": {"item": "minecraft:iron_ingot"}
        }
        ],
          "results": [
            {
              "item": "refinedstorage:incomplete_raw_basic_processor",
              "count": 1,
              "chance": 1.0
            }
          ],
          "loops": 1
      })

that might work but im not sure cause it's based of 1.18.2 spelling... just tell me if it doesn't

[copper path]

this is server script btw...

[cerulean shore]

shouldn't the last result be raw_basic_processor

[copper path]

im not exactly sure test it without and then if it doesn't work add it...

[cerulean shore]

and that one goes in the "server_startup" right?

[copper path]

yup

[copper path]

that's why i wasn't sure it would work...

[cerulean shore]

that wasnt urs

you done the server script, Null done the startup i think

[copper path]

this is startup...

[cerulean shore]

is it after "literal"

[copper path]

ohhhhhh i see....

[cerulean shore]

is that right?

[copper path]

StartupEvents.registry('item', e => {
    e.create('refinedstorage:incomplete_raw_basic_processor', 'create:sequenced_assembly').displayname(Component.literal('Incomplete Raw Basic Processor')).texture('refinedstorage:incomplete_raw_basic_processor')
        
})

console.info('Hello, World! (Loaded startup scripts)')

like this?

[cerulean shore]

ahh i see

what now 😦

[copper path]

let me research cause im unsure...

where to start... i may have done some stuff wrong... (i have mainly used 1.18.2 syntax so that's why...)

first the startup script...

StartupEvents.registry('item', e => {
    e.create('refinedstorage:incomplete_raw_basic_processor', 'create:sequenced_assembly')
})

console.info('Hello, World! (Loaded startup scripts)')

that maybe is good... idk im not sure

[cerulean shore]

ok but that would have no texture

[copper path]

wrong if you do like what i mentionned here it would work...

[copper path]

normally...

[copper path]

wait what?

[cerulean shore]

wait thats the server script

[copper path]

uhhhhhhhhhh well yeah...

[glacial plover]

Paste version of example.js from @cerulean shore

[copper path]

what i thought (maybe)

[cerulean shore]

yea looks like the way its configured is very different now

[copper path]

trying to serch for an exemple that ressembles this...

[cerulean shore]

https://wiki.latvian.dev/books/kubejs/page/kubejs-create#bkmrk-sequenced-assembly

if you ignore the yellow

[copper path]

im looking at that but the way it's done is not the exact same...

[cerulean shore]

i think it lists the item steps then the procedure of doing so

[cerulean shore]

wrong

[copper path]

basically what is done is telling the results first and then the sequence... the input is just before the sequence

[cerulean shore]

any ideas?

[copper path]

im trying things but ain't sure...

[copper path]

what is done in the web site...

[cerulean shore]

i made this like on the site, but my startup isnt working so its not even getting to this part anymore

[glacial plover]

If you're working with KubeJS scripts, config files, or similar things, we generally recommend using an actual IDE rather than just Notepad++ and its various siblings.
In a lot of cases, it can help you find errors in your code faster and also gives you neat features like syntax highlighting, automatic formatting, etc!
We recommend Visual Studio Code, since it's lightweight(-ish) and works very well with JavaScript files out-of-the-box.

[copper path]

yeah yeah yeah we know that...

[glacial plover]

https://gnomebot.dev/assets/replyping.png

[copper path]

ok...

[cerulean shore]

i cant get past the startup script not working and idk why 😦

[copper path]

was the other thing working?

[copper path]

this

[cerulean shore]

thats the startup script

[copper path]

yes but what i mean is was that one working or not...

[cerulean shore]

gimmi a sec

its ok if i dont put the texture part in

but the recipe doesnt work anyway

i'll have to try .parentModel and see if that works, but its 03.30 and i should be in bed

1.19.2if that matters. but i think the main changes happened from 1.18-1.19

[copper path]

yes

[muted steppe]

I got some custom sequenced assembly recipes on my code
Ping me when you are up, i should be home by then

[cerulean shore]

@muted steppe you about?

[muted steppe]

still not home... but here is one of my recipes:

@cerulean shore

[glacial plover]

Paste version of knowledgebook_2.js from @muted steppe

[muted steppe]

this is on 1.20.1, server_scripts

[cerulean shore]

do you have the item creation script too?

[muted steppe]

oh, let me look

StartupEvents.registry('item', event => {
event.create('ItemID as String').tooltip(`Whatever description you want to add`).texture('ResourceLocation as String').displayName('Item`s Name')
});

i dont know if you can use the Resourcelocation of a Mod this way, but you can add your own in the assets folder of kubejs. eg. kubejs/item/ItemID as String

startup_scripts

hope this will work for you

[cerulean shore]

so there's no 'create:sequenced_assembly' after the itemID?

[muted steppe]

this only creates an item

the first script does the recipe

[cerulean shore]

hmm the other ppl included that part so was just checking

[muted steppe]

oh they did? hmm

[muted steppe]

i see, but does this work?

[cerulean shore]

does the displayname have "_" instead of spaces?

[muted steppe]

no

[cerulean shore]

whats the 'cop:recipes/knowledgebook_2' referring to?

[muted steppe]

cop:recipes/knowledgebook_2, cop is the modid, knowledgebook_2 the name of the json

basically it tells where to save the recipe

knowledgebook_2 is the recipe name in this case

[cerulean shore]

for refinedstorage raw basic processor it would be 'refinedstorage:recipes/raw_basic_processor' is that correct?

[muted steppe]

i think it doesnt matter, iirc you can use whatever recipe name you want

only the sytnax with modid:recipes/recipeid has to be right

you could use a modid that doesnt exist

its only important that there is no recipe id with that exact string

[muted steppe]

you still using the inter part?

[cerulean shore]

no i copied your stuff and editing the recipe now

[cerulean shore]

i dont understand you here though

[muted steppe]

you could go kubejs:recipes/incomplete_raw_basic_processor

this way you add that recipe to the modid kubejs, you could also go eg. newmod:recipes/incomplete_raw_basic_processor, then its saved under newmod

the modid doesnt have to already exist via a mod thats actually there to use it

[copper path]

this thing makes a Json...

kubejs has an addon to work with create...

[muted steppe]

jep, you can do it one way or another

[copper path]

use the simplest way... the addon...

[muted steppe]

whatever you prefer, the json way doesnt need the addon and i think its easier to look at existing assembly recipes and modify them

[cerulean shore]

then why didnt you say it last night 😛

[copper path]

i didn't think about it...

[muted steppe]

@cerulean shore did you get it to work?

[copper path]

this is a custom so how the mod registers its recipes...

[copper path]

look who talked about it before me...

[muted steppe]

both ways work fine

[copper path]

use the integrated method because way simpler...

[muted steppe]

[thick holly]

Just use the addon

[cerulean shore]

but how do you go about that.....

[copper path]

what im saying...

[muted steppe]

json way too confusing?

[copper path]

not exactly that but why tracing your own path when you can fallow an already made one...

[cerulean shore]

how do you use the addon tho

[muted steppe]

dude i dont care what way he uses,i just wanted to help

[copper path]

im trying to understand the 1.19.2 version because i work with 1.18.2...

[copper path]

yes it's fine...

    e.recipes.create.sequenced_assembly({
    "ingredient": {
        "item": "minecraft:iron_ingot"
      },
      "sequence": [
      {
        "type": "create:deploying",
        "ingredients": [
          {"item": "minecraft:iron_ingot"},
          {"tag": "refinedstorage:processor_binding"}
        ],
        "results": {"item": "kubejs:uci1"}
      },
      {
        "type": "create:deploying",
        "ingredients": [
          {"item": "minecraft:iron_ingot"},
          {"item": "refinedstorage:silicon"}
        ],
        "results": {"item": "kubejs:uci1"}
      },
      {
        "type": "create:deploying",
        "ingredients": [
          {"item": "minecraft:iron_ingot"},
          {"tag": "forge:dusts/redstone"}
        ],
        "results": {"item": "kubejs:uci1"}
      },
      {
        "type": "create:pressing",
        "ingredients": [{"item": "minecraft:iron_ingot"}],
        "results": {"item": "minecraft:iron_ingot"}
      }
      ],
        "results": [
          {
            "item": "refinedstorage:incomplete_raw_basic_processor",
            "count": 1,
            "chance": 1.0
          }]
    }).transitionalItem('minecraft:iron_ingot').loops(1)

this maybe should work if you have the addon installed...

[cerulean shore]

is that 1.19

[copper path]

it should...

[cerulean shore]

and where's that go

[copper path]

server

[copper path]

server= recipes
startup= registry of items and stuff like that
client= everything with jei and stuff like that

[cerulean shore]

"e" is not defined

[copper path]

does your entire thing looks like this:

ServerEvents.recipes( e => {

   e.recipes.create.sequenced_assembly({
   "ingredient": {
       "item": "minecraft:iron_ingot"
     },
     "sequence": [
     {
       "type": "create:deploying",
       "ingredients": [
         {"item": "minecraft:iron_ingot"},
         {"tag": "refinedstorage:processor_binding"}
       ],
       "results": {"item": "kubejs:uci1"}
     },
     {
       "type": "create:deploying",
       "ingredients": [
         {"item": "minecraft:iron_ingot"},
         {"item": "refinedstorage:silicon"}
       ],
       "results": {"item": "kubejs:uci1"}
     },
     {
       "type": "create:deploying",
       "ingredients": [
         {"item": "minecraft:iron_ingot"},
         {"tag": "forge:dusts/redstone"}
       ],
       "results": {"item": "kubejs:uci1"}
     },
     {
       "type": "create:pressing",
       "ingredients": [{"item": "minecraft:iron_ingot"}],
       "results": {"item": "minecraft:iron_ingot"}
     }
     ],
       "results": [
         {
           "item": "refinedstorage:incomplete_raw_basic_processor",
           "count": 1,
           "chance": 1.0
         }]
   }).transitionalItem('minecraft:iron_ingot').loops(1)

})

[cerulean shore]

didnt work but i know y

[copper path]

ServerEvents.recipes( e => { 

e.something('something_here')

)}```
what it does is define the e (it's event from scratch but you can change it to what ever you want so it could be g or t or anything else like that)

[cerulean shore]

you had the output as the incomplete version

[copper path]

ohhhh forgot to change that sorry...

[cerulean shore]

the first step?

[copper path]

kind of works that's a great start...

[cerulean shore]

True

idk why, the tag is correct

[copper path]

what tag?

[copper path]

wait ohhhhhh

[copper path]

now it'a the first it put on that doesn't work...

[cerulean shore]

what

you had it set to "tag":

should i try "item":

[copper path]

yes...

it will work im confident now...

[cerulean shore]

YAY

for another recipe does "e" need to changed

[copper path]

nope you define it once and if you put another recipe in the thing your good

ServerEvents.recipes( e => {
 e.here_you('have_the_first_one')

e.here('you_put_another_one')

e.another('one')

e.you_continue('and_on_and_on')
 )}```

[cerulean shore]

do you know the remove script?

[copper path]

yes...

in 1.18.2 tho...

idk if it'll work...

  e.remove({id: 'create_central_kitchen:crafting/dough_4'}) 

that's what i have...

[cerulean shore]

whats wrong here? i added the other 2 recipes and it crashes on launch

[glacial plover]

Paste version of raw_basic_processor1.js from @cerulean shore

[copper path]

why is your results different?

[cerulean shore]

cause theyre diffrenet items at the end

different processors

[copper path]

do like my thing for all of them...

[cerulean shore]

wym

[copper path]

what is your kubejs:uci1?

[cerulean shore]

...

[copper path]

should be like this...

[glacial plover]

Paste version of raw_basic_processor1.js from @copper path

[copper path]

test that out and tell me...

[cerulean shore]

nope

[copper path]

normally it should work...

[cerulean shore]

the uci1 one worked that you done before

[copper path]

what?

[cerulean shore]

this with the "tag" change

do you want the crashlog?

[copper path]

nope uh wait

logs in general and the code...

[copper path]

why uci1 tho? idk?

[cerulean shore]

it was part of the startup script cause i thought i could remove the created incomplete_raw_basic_processor

[cerulean shore]

idk, you sent it to me...

[copper path]

the tag thing chaged to item right?

[cerulean shore]

yes

[copper path]

ok... so was it working right after that?

[cerulean shore]

.

[copper path]

put the startup and server in here...

[glacial plover]

Paste version of raw_basic_processor1.js, registry.js from @cerulean shore

[copper path]

you still have the kubejs:uci1 in there...

[copper path]

should be this...

[cerulean shore]

yep and because it only works if its there

[copper path]

weird...

[cerulean shore]

im testing without the other 2 recipes

it does work, so does that mean i shouldnt need the startup script creation

[copper path]

you don't use the startup script item so idk...

[cerulean shore]

it mustve been using that as the uci1

[copper path]

the names aren't the same tho...

[cerulean shore]

idk but the recipe is there and working with it changed like you said

[copper path]

like what? this?

[cerulean shore]

yea but i removed the startup script and that worked

[copper path]

what is your server script?

[cerulean shore]

i have one for each recipe simply because it wasnt working with the exact one you sent but split it was fine

[copper path]

send the server script you have

[glacial plover]

Paste version of raw_basic_processor1.js, raw_improved_processor1.js, raw_advanced_processor1.js from @cerulean shore

[copper path]

wait gold ingot in the diamong one?

[copper path]

in the advanced processor thing the pressing...

[cerulean shore]

whoops

[copper path]

            {
                "type": "create:pressing",
                "ingredients": [{ "item": "minecraft:diamond" }],
                "results": { "item": "minecraft:diamond" }
            }

there you go..

[cerulean shore]

yea i got it

[copper path]

ok good

anything else?

[cerulean shore]

i want to remove the refined storage recipe but you said you werent sure

[copper path]

!tryitandsee

[copper path]

ohhh...

[glacial plover]

https://tryitands.ee

[cerulean shore]

i think it this.

e.remove ({mod: 'refinedstorage', output: 'raw_basic_processor'})

[copper path]

https://wiki.latvian.dev/books/kubejs/page/recipes#bkmrk-removing-recipes↑

[cerulean shore]

would that be right

[glad orchid]

that's all what you need

e.remove({ output: 'refinedstorage:raw_basic_processor'});

[cerulean shore]

and that'll be in server yea?

[copper path]

yes

[copper path]

every thing that is craft related is server...

[cerulean shore]

Can a block be created to drop something that isn't itself? Like the hammers from stoneblock

[glad orchid]

you can easy Modify Loot with LootJS like this i have added obsidian if i mine stone or you can remove something:

LootJS.modifiers((event) => {
  event
        .addBlockLootModifier("minecraft:stone")
        //.removeLoot("minecraft:cobblestone")
        .addLoot("minecraft:obsidian");
});

[cerulean shore]

also is it the .material that goes to the texture?

nvm

[glacial plover]

This seems pretty unrelated - are you sure that it's related to your original issue? For simplicity and everyone else's sake, please create a new ticket. This also helps others that try to help you, as they may know how to fix x, but your ticket is still called y. Don't rename it either, then others looking for y won't be able to find it! -> #1047320998199955458

[cerulean shore]

@thick holly i get that but id rather get a response from someone whos following it rather than relying on someone stumbling along the new thread

[copper path]

was there anything else you wanted?

[cerulean shore]

https://discord.com/channels/303440391124942858/1238906120115064862