Author Topic: New Duplicator 1.6.2 | Now on BL Glass  (Read 235382 times)

Can't you just have them duplicate the bricks they want to own and delete the original?
this is possible but it's just much easier to have an admin do it like this, instead of exchanging trust and whatnot

this is possible but it's just much easier to have an admin do it like this, instead of exchanging trust and whatnot
set dup trust limit to none and let them dup it themselves, then set the pref back?

How come when I use the /fillwrench command, everything is greyed out?

You have to check the settings that you want to apply on the right.


Is there any way you can combine the features of copying events with The Selector into the duplicator?

No, but you'll be able to apply events at some point.

No, but you'll be able to apply events at some point.
Sweet. I guess I'll hold off on the Selector then.

I think I will be using this on my server. Nice!

You should add a feature where you type in a command and you can set the brick's BLID to a certain one and when you place the dup, the bricks are that BLID

This would be useful

Alright, this is getting extremely loving annoying as Blockland stops responding every single time I try to mirror bricks while it creates the brick symmetry table. At first it's fine but within seconds it progressively becomes increasingly laggy and eventually blockland stops responding entirely. This is probably partially due to the amount of datablocks I have (~6900) in my server, but this shouldn't be happening regardless. Yes, this is with the latest version (1.2.0), and has happened with a previous version. I tried doing a trace and nothing special came up before blockland stopped responding.
« Last Edit: January 19, 2016, 07:16:08 PM by QuadStorm »

Running trace is probably not the best idea because it'll dump thousands of lines, but does it stop at the same brick every time?

Running trace is probably not the best idea because it'll dump thousands of lines, but does it stop at the same brick every time?
It did stop at the same brick in three out of four trace tests, but for whatever reason the 3rd trace test I ran didn't result in blockland becoming unresponsive and worked successfully.

last brick datablock it got to before blockland stops responding

dump of that datablock

Does it finish if you just leave it running for a few minutes? Maybe you have insane high poly bricks that take forever to calculate symmetry.

If not, the next thing to try would be setlogmode(1);trace(1); This might lag horribly but it will ensure all lines are actually written to the log, your trace shows it successfully finishing a tick which isn't related to the problem. Look at the end of console.log after the game craahes.

Also I'm pretty sure you got the wrong datablock there, just do id.dump();
« Last Edit: January 19, 2016, 08:08:19 PM by Zeblote »

I let it run for nearly 10 minutes and blockland stayed unresponsive.

further tests...

datablock again, hopefully the right one
http://pastebin.com/WnLEE8R7
snip of console.log from just before blockland goes unresponsive, note that there was a blank line right under the last one in the console.log