CraftBook 3

CraftBook 3

139k Downloads

Forward Slash breaks Item Syntax

LadyCailinBot opened this issue ยท 4 comments

commented

CRAFTBOOK-3092 - Reported by adw123

Using the forward slash ( / ) in item syntax causes item data to get stripped essentially breaking the item. I've verified that this occurs in CommandItems and in Custom Recipes though I imagine is present in all areas of Craftbook since this syntax is consistent with all craftbook functionality.

Below is an example recipe:

http://dev.bukkit.org/paste/11251/

When this is crafted it creates an item with a lore line that looks like this:

Durability: 900

As opposed to:

Durability: 900/900

From what I understand the use of the backslash ( \ ) is supposed to escape this anomaly but doesn't quite work the way it should. Placing a backslash in front of the forward slash returns a line that looks like this:

Durability: 900/900

Note that custom crafting seems to work fine at first after you create the recipe in game but once you restart your server something happens that causes this to break.

Not being able to use the forward slash in item syntax makes Craftbook incompatible with plug ins such as Item Lore Stats and any other itemization plugin that requires this character in the Lore field.

Please fix this so that either the forward slash is an acceptable character in item syntax or that the use of a backslash properly escapes this special character without displaying the backslash itself.

Thank you!

commented

Comment by me4502

To escape the character, use %

commented

Comment by adw123

Can you provide me an example for how it has to be formatted please? I've tried the following things thus far:

Durability: 900%/900 (Recipe doesn't load during start)
Durability: 900 %/900 (Recipe doesn't load during start)
Durability: 900%/%900 (Recipe doesn't load during start)
Durability: 900%/900 (Recipe doesn't load during start)
Durability: 900/%900 (Strips everything off after the /)

Thanks.

commented

Comment by adw123

Any update on this?

commented

Comment by me4502

Using / should work.