AWE World Edit

remove the torches and replace them?

 

I...don't think you can do anything about this...not sure though.

 

Sadly there is nothing you can do. World edits clipboard copies position, not directional data. This problem is caused bc world edit does not record the redstones directional data, and it just places it in a set position. This is also the reason that things like trapdoors and angular log placement doesn't work. WE is a great tool, but awefly finicky. If you have any questions about redstone or world edit, let me know.

 

Sometimes using flips instead of rotate works... but sometimes it still glitches.
Vines are the worst, though.

¯\_(ツ)_/¯

 

You can manually rotate torches by doing a trick with //replace, like so:

Code:

//replace redstonetorch:0 sponge
//replace redstonetorch:1 redstonetorch:0
//replace redstonetorch:2 redstonetorch:1
//replace redstonetorch:3 redstonetorch:2
//replace sponge redstonetorch:3

Of course, this doesn't work too well if your torches are changing state while you do the worldedit or if you have torches adjacent to each other.

...what?


EDIT: what if we disabled physics while an AWE operation was in progress?

 

Phanta just gave me another idea.

An easier (maybe not quicker, but much easier) way would be to replace torches with a really visibly obvious block before rotate, then go back and manually place the torches.

An issue I've seen is that some torches disappear completely. At least this way you'll have torch locations marked.

 

Haha, basically speaking, when you copy paste, WE won't copy the direction of blocks like redstone. You can use hex codes to adjust the placement after you paste, but WE will not copy paste the direction. This is due to the virtual "clipboard" as it is called. The clipboard does not record the hex data attached to the redstone direction.

 

It does do directions. I can rotate and flip stairs no problem.

It's just buggy with torches and vines.

 

Of course it records "hex" data (which is actually called block metadata fyi). That's why wool colours persist and stairs are rotated during WE operations. I suspect sk89q just missed a certain case, or perhaps our WE version is outdated.

I'll check later.

 

Correct me if I am wrong, but it also struggle with redstone also correct? And I vaguely remember it bugging with stone slabs aswell? At least back when I used to build for servers I used to run into the problem of the redstone defaulting to its 4 directional phase, not the proper facing direction, and I think we had to reset any stone slabs positioned in the bottom half of the block hemisphere, but I don't remember for sure. I also noticed this issue with logs back when directional logs were new to the game, but that I assume was fixed pretty quickly.

As I said "the hex data attached to the redstone direction", obviously it has to record some hex data other wise things like wool would never retain their color. Not to mention most all items have some sort of hex data, or metadata as you stated its called, but I just use hex data because most people don't know what meta data is XD.

 

Redstone could be buggy as well. It's good to avoid redstone on the Build server because it causes lag.

Metadata is a term commonly used within the Minecraft community.

 

True that. When we have 100 plots with stupid little redstone circuits going, it is bound to cause some crazy lag. And I mean honestly how many players do you think are familiar with the term? Perhaps I am under estimating the amount.

 

Actually, I think I'm just used to talking to Build team people. Most of the community doesn't have a word for it, they just yell out "what's the id for [insert block here]"

Hex is usually specifically for hex codes. Meta data refers to any data describing data. For example, describing wool as red. 35 is wool. 35:15 would be red wool. Meta data for building includes hex, dec, and bit codes for minecraft.

I guess "data value" is the overarching term, so I wasn't completely right. Here:
http://minecraft.gamepedia.com/Data_values
http://minecraft-ids.grahamedgecombe.com/faq

Either way, doesn't really matter. I'm glad to see people interested in the more tedious aspects of building.

 

"Hex", "dec", and "bit" stand for hexidecimal, decimal, and binary respectively. They're all references to the block's metadata, which is a number from 0x00-0x0F (or 0-15 in decimal).

 

We're all arguing the same cause XD

 

What the hell is wrong with "stuff" {d3rgps31}

jk