I built too many bricks and can't move them

[Nymethus]

Ah. Try this then, in the console.

Code: [Select]

function calcSaveOffset(){$LoadingBricks_PositionOffset = "0 0 32";}$LoadingBricks_PositionOffset = "0 0 32";

It worked! Thank you! Have some delicious stroganoff!

[Ad Bot]

[Chrono]

Alright, explains that calcSaveOffset just sets the variable based on some stuff, ah sehr interessant!

[Sleven]

Thank you! Have some delicious stroganoff!

Äckligt.

[Nymethus]

Äckligt.

är du socialdemokrat? men vad säger dina pappor?

[Bester Bageler]

är du socialdemokrat? men vad säger dina pappor?

Stop speeking Sweedish, Dutch, German, VichousKinid!

[ravencroft]

Why does everyone say duplorcate, instead of duplicate. :/

[Evar678]

Why does everyone say duplorcate, instead of duplicate. :/

oh god...
You are so uninformed...


Anyway, the duplorcator is a new mod made by plornt. It is 10 times loveier than the duplicator, but also, in some cases, 10 times laggier.
Found here: http://forum.blockland.us/index.php?topic=206615.0

[Conan]

If chrono could package that as an addon that would be nice

[Trinick!]

What kind of units are those?

Good question, cause this doesn't exactly leave room for plates.

Serious? They're Torque Units, normal bricks are half a torque unit wide and 0.6 torque units tall. 1x1 plates are 0.5x0.5x0.2. A 64x cube is 160 plates tall, multiplied by 0.2 torque units per plate, yielding 32 Torque Units as your Z offset.

[Operator¹]

oh god...
You are so uninformed...


Anyway, the duplorcator is a new mod made by plornt. It is 10 times loveier than the duplicator, but also, in some cases, 10 times laggier.
Found here: http://forum.blockland.us/index.php?topic=206615.0

there's an option to turn off the ghost bricks

[Trinick!]

Anyway, the duplorcator is a new mod made by plornt. It is 10 times loveier than the duplicator, but also, in some cases, 10 times laggier.

In no scenario is the duplorcator slower than the duplicator. It just isn't. You must be setting your preview brick count to ridiculously high brick counts, because as far as the actual duplication and planting goes, it's significantly optimized.

[Dglider]

-snip-
because as far as the actual duplication and planting goes, it's significantly optimized.

Did you actually test this?  In my experience the duplorcater will lag everyone out, while the duplicator (while still lagging an incredible amount) does not.

I have noticed that the regular duplicator's lag tends to be in massive spikes, with a few milliseconds in between.  So maybe, while being a bit slower, it actually gives the server time to respond, rather than letting everyone time-out.
While the duplorcator just does everything in a massive chunk, no matter how many people are accidentally removed from the server.

Idk this is just something I've noticed from experience.

[Trinick!]

Did you actually test this?  In my experience the duplorcater will lag everyone out, while the duplicator (while still lagging an incredible amount) does not.

I not only tested it, I helped Plornt develop it.

I have noticed that the regular duplicator's lag tends to be in massive spikes, with a few milliseconds in between.  So maybe, while being a bit slower, it actually gives the server time to respond, rather than letting everyone time-out.
While the duplorcator just does everything in a massive chunk, no matter how many people are accidentally removed from the server.

The duplorcator shouldn't ever cause freeze lag, the way it's set up circumvents it completely. You're doing something wrong if it does.

[Chrono]

Good question, cause this doesn't exactly leave room for plates.


Serious? They're Torque Units, normal bricks are half a torque unit wide and 0.6 torque units tall. 1x1 plates are 0.5x0.5x0.2. A 64x cube is 160 plates tall, multiplied by 0.2 torque units per plate, yielding 32 Torque Units as your Z offset.

Sorry, for some reason I was going by this post:

Before you load the build, try putting $loadOffset = 192; in console.

And assumed it was 192 plates tall.