#(MrCrash) Allowed to craft mirrored recipes
106 messages · Page 1 of 1 (latest)
Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.
You can block this bot if you don't want to see these messages, I won't mind.
<@&525394568410038282>
uhh
Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.
If not yet resolved, please reply below to tell us what you still need.
(Note that if there is no reply for a few days, this thread will eventually close itself.)
@late vigil
example:
okay that wasn't intentional?
nope
Click the pictures 
with the screen's example it's okay?
Help us help you by pasting your script to https://paste.denizenscript.com/New/Script and linking it back here.
Please post the script
https://paste.denizenscript.com/View/106215
start line 51
Content of Denizen Script Paste #106215: Unnamed Denizen Script Paste... pasted 2023/02/13 11:05:04 UTC-08:00, Paste length: 5508 characters across 219 lines, Content: amethyst_pickaxe: type: item
those screenshots seem like they're doing what you expect
I don't understand the issue
Like, you could make all of these recipes one item script
Is that what you're asking about?
look at the 2 recipes of 2 different items , both recipes give the same item result
you made them intentical
they're not the same item
there's just no way to tell them apart
they're both obsidians with the same name and a hidden enchantment
you can narrate them in your hand if you want to be sure
note the same name
oh
same problem
well
try removing drawer1, reloading, and then crafting it
see if that fixes it
if so, readd it and see if the problem comes back
If that doesn't work, could you please craft both items and hold both items in your hand and run a quick /ex narrate <player.item_in_hand> for both items?
!debug
If you need help with a script issue, one of the most powerful tools Denizen has to offer is full debug output. This is displaying in your console whenever scripts are running until you turn debug off. To share a debug log quickly and easily with helpers, simply run the command /denizen debug -r in-game to begin recording, then run through the part of the script you need help with, then run the command /denizen submit. This will give you a link to a paste of the debug log, which you can then copy/paste back to us!
Also don't forget to start the debugger while running it.
w8 item script have a debug?
debug the narrates
Technically yes, but I want you to debug the narrates ^
oh yeah obv
turn on debug, hold the first item, run /ex narrate <player.item_in_hand>
then do the same while holding the second one, and submit
Content of Server Log Paste #106216: Denizen Debug Logs From One-Dream | SkyBlock... pasted 2023/02/13 11:13:46 UTC-08:00, Paste length: 4232 characters across 43 lines, Content: Java Version: 18.0.2.1Up-time: 39m
interesting
Did you craft the two items with both crafting recipes?
Yes
Did you try a server restart?
Can you debug /ex narrate <script[drawer1].data_key[recipes]> and also /ex narrate <player.discovered_recipes[shaped].filter[starts_with[denizen:shaped_recipe_drawer]]> as well as /ex narrate <server.recipe_ids[shaped].filter[starts_with[denizen:shaped_recipe_drawer]]>
next thing i'd try otherwise is making a completely new distinct item with that recipe
that works too lol
Just to check if the script you've posted is on your server, what recipe the player learned and what item scripts got registered on the server
Oh also while you're on it, run /ex reload too.
So run the following:
/ex narrate <script[drawer1].data_key[recipes]>/ex narrate <player.discovered_recipes[shaped].filter[starts_with[denizen:shaped_recipe_drawer]]>/ex narrate <server.recipe_ids[shaped].filter[starts_with[denizen:shaped_recipe_drawer]]>/ex reload
Yeah i eat and i do that
Oh I can replicate that.
Thread is now a Bug thread. This indicates a core code bug that a developer must resolved, not an error message or other support topic. Please do not misuse the Bug label. Use </helpthread:1028674284870180883> to switch the thread back to a normal help thread if you are not 100% confident it is a code bug.
Oh so it's really a bug
can you specify the requirements? Like, does it work with any item
if so is it specifically this configuration?
this is a super weird bug
test_scripta:
type: item
material: diamond_sword
display name: MyScript
recipes:
1:
type: shaped
input:
- dirt|dirt|dirt
- dirt|dirt|dirt
- dirt|dirt|stone
works with any item, that's my test script ^
There was a thread about this a while ago iirc, Spigot/Minecraft have a weird thing where they basically mirror recipes (e.g. allow crafting them both ways)
Yeah, this one right? #1058423704180232284 message
Yeah
(MrCrash) Allowed to craft mirrored recipes
@late vigil seems to be a minecraft thing ^
should we just close this and leave the other post open
i honestly don't know what our policy for duplicate bugs is
You might be able to go around that by listening to the item recipes formed event and determine air if <context.recipe> doesn't match your recipe, if you don't want to allow mirrored recipes.
Or maybe feature request that to be an option in an item script container?
that's better for what i want to do
so it's a minecraft "bug"?
#denizen-contrib message relevant discussion
Ref that ^, it's a thing specifically hard-coded in by Mojang it seems
If you really want to block it for some reason, it might be possible to basically do our own recipe matching in a prepare craft event to check if it's mirrored or not
So @late vigil ^ generally this is vanilla behavior, if you really need to only allow crafting it the way it's in the recipe and not mirrored, I think it'll be possible to workaround in Denizen
Thread is now a Help/Support thread. A helper will check your thread when available.
Ref ^ this is a vanilla feature, if you really need to block it can probably use item recipe formed and check if it's mirrored or not
Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.
If not yet resolved, please reply below to tell us what you still need.
(Note that if there is no reply for a few days, this thread will eventually close itself.)
@late vigil