Sign manipulation with items (Auto-offset-writing, copypasta...)
LadyCailinBot opened this issue ยท 18 comments
CRAFTBOOK-2456 - Reported by pmpmpm
Hi!
So, in order to simplify the creation of the offset (thing that can be particularly tricky when the IC is far from the center of the area), here's my idea:
Rather than immediately writing the offset on the sign, you would write [offset]. The, using a feather or another item, you would go to the block center of the detection, and then right-click on it. The offset is automaticaly written! If you left-click, you're immediately teleported in front of your IC (in order to continue the IC circuit).
You could too write [offset] on multiple ICs, then each of your click with the feather (or another designated item) would write the offset on one IC, in the order of their creation of course.
So, that was for the offset. Now, the copy/paste idea:
Always using an item, if you right-click on a sign, you copy it. Using another item (not the same as before), you right-click on the sign you want to paste the IC on, and it's done! You've created the IC without having to write 3 lines of parameters ... or offsets. May be particularly useful when you have to place dozens of mob spawners, for example.
So, that's all. Thanks for reading!
Comment by me4502
My idea for the auto offset, is using WorldEdit to select an area, and it automatically transfers that into offset/radius.
You'd select an area, and go to the sign.
You'd write it all, but where you'd usually write the offset you write[off], and where you'd write the radius you'd write [rad]. It would then auto change them.
Comment by pmpmpm
I don't perfectly see how it would work. What would be the center?
Comment by pmpmpm
I see what the use would be, yes. Hey, it's a gerat idea... So:
If I want to put my detection in a circle shaped room, I just have to select a wall then the opposite wall, it seems easy. On the sign, I'd put [rad]=[off]. Ok.
If I want to put my detection on a single block with an already set radius, I just have to put #=[off] (# being a number) on the sign, and click twice on the center of the detection. Ok.
How would the [off] and [rad] be written, exactly? Only automatically? Or could it be possible to use a command?
And what about the case where there is multiple offsets to write, like 10? It would be boring to add one IC, then select the area, then another IC, then another area... Would it be possible to write all ICs at once, with [off] and/or [rad] on them, and then use a command to complete them one by one by order of creation?
Comment by pmpmpm
I'm actually thinking about a way to make this offset/radius thing simple and yet usable for massive use...
Rather than using the center of the selection, I think it may be better to left-click with the wooden axe for the center, and right-click for the radius (this radius being the distance between the two points selected). It seems more "natural" to me, since you can precisely select the offset and "see" well the radius.
I think, from here, there should be two ways to use this:
- Putting [rad] and [off] on a sign would directly write the radius and offset from your WE selection.
- Putting [srad] and [soff] (s for Set) on a sign would write the radius and offsets only when a command is prompted by the player who made the sign(s).
What do you think about all that?
Comment by me4502
Um... How about if the selection is a cuboid, use the centre.. And if it is in circle mode, do what you said?
Comment by pmpmpm
Okay, but how do we go into "circle mode"? A World Edit command?
Comment by pmpmpm
Seems perfect! Maybe it could even be better: While we're speaking about cuboid detection, what about adding [cub]/[scub] on the sign that would use the cuboid region the player selects?
Comment by me4502
Okay, I've added [off]. It only works for cuboid regions at the moment, and I haven't added [rad] yet.
Comment by pmpmpm
When putting [off] on a sign after having selected an area, whatever or wherever the area is, it writes a buggy text:
&.0:.0:.0
Comment by me4502
I couldn't reproduce that bug, but for me the offset was inversed. I've fixed that now. Maybe try the latest build?