//cycler unable to cycle through blocks created using CTM
LadyCailinBot opened this issue ยท 3 comments
WORLDEDIT-2808 - Reported by killjoy1221
Using MCPacher or Optifine, you can have different textures correspond to different data values. Using this method, you can create new blocks (up to 15) for each block that is meta independent. Creating these blocks ingame is as simple as selecting the region then using //set id:meta or using the //repl tool. The //cycler tool currently cycles through meta data values and if there is only one, it will not change it.
I propose that the //cycler tool cycle through all meta values (0-15). The client/server's smart enough to know what to display and/or drop when destroyed.
To see this in action, look at ice and glowstone in The Voxel Box's Palceon pack. Be sure to use all of the damage values (So many colors).
Comment by wizjany
they're not real blocks as far as the server is concerned, and we have no way of detecting them as being such
Comment by sk89q
From the description, it seems as if they are "real blocks". It just uses the data IDs.
Of course, we'd have to make /cycler into a fairly 'dumb' tool that just cycles the data value of everything it touches but that it doesn't understand.