Need to either deprecate trade signs or look into storing additional blockdata, new signwidth and json data possibly opens more avenues.
drtshock
All 4 comments
Can you elaborate? What kind of features does this present, what kind of data would be stored?
SupaHam
on 22 Jul 2016
I believe I was talking about the ability to have extended item data on trade signs.
drtshock
on 22 Jul 2016
If we're talking about line length, I don't know tbh. A sign line's maximum characters depend on the characters present, which at times can be 15 maximum.
Sign events are a thing. We could maybe have an Essentials command (e.g. /createsign buy verylongitemname:withdata $123123) that constructs and inserts a command event in the sign.
SupaHam
on 22 Jul 2016
Closing this since it is not much of an issue in more recent versions of Essentials, due to the updated ItemDB. Short names for items generally exist (and if they don't, they are added). Metadata don't really fit on signs, and I think it would probably be awkward / confusing no matter how you'd try to implement that.
pop4959
on 28 Dec 2019
Related issues
rjohnson98126
路
3Comments
Castiella
路
3Comments
SkyLicks
路
3Comments
fieu
路
3Comments
MithrandirCraft
路
3Comments
Most helpful comment
Closing this since it is not much of an issue in more recent versions of Essentials, due to the updated ItemDB. Short names for items generally exist (and if they don't, they are added). Metadata don't really fit on signs, and I think it would probably be awkward / confusing no matter how you'd try to implement that.