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

At the moment, it seems like dying just removes your ghost brick and such as part of the default building system. Perhaps what I'm asking for could be refined into a different sort of feature. What about a command that recovers the last duplication you had selected? That way if you lose it for any reason, including accidentally clearing it, you can bring it back.

An extra mile to take with that feature might be to make the recovery persist between client instances, so that you can recover the duplication if say you were to time out from the server. That might be taking it a bit too far, though.
« Last Edit: April 13, 2016, 06:46:24 PM by Pecon »

That's possible, but then I have to keep all the selection data around until you select something else. That could be several 100000 global variables, depending on how big your selection is.




So today I found a bug, where if you ctrl x on a bot hole when the bot is powered off, the bot hole is destroyed but the bot itself isn't.

So today I found a bug, where if you ctrl x on a bot hole when the bot is powered off, the bot hole is destroyed but the bot itself isn't.
This is caused when the add-on doesn't called fxDtsBrick::onRemove which just means that when the brick is removed randomly the bot doesn't delete (Map changers sometimes have this issue)

It's not possible to delete an object without calling onRemove.

How do I see the duplist? None of the commands are working

How do I see the duplist? None of the commands are working

/alldups or /ad

/alldups or /ad
ok nice, what about clients loading dupes from their server on others? what's the command for that?

I don't think you can do that at the moment but it could be a nice feature if made properly

weird because there's an rtb pref for clients to load dupes from their servers

ok nice, what about clients loading dupes from their server on others? what's the command for that?

You can't. Mainly because I don't want to deal with clients uploading specially crafted saves that *somehow* manage to crash the server - it expects a perfect .bls file and has almost no error checking.

weird because there's an rtb pref for clients to load dupes from their servers
you could just give them admin and have them load the save file manually - they just have to copy over the save from the newdup folder to their saves folder, then upload normally.

honestly though its easiest/most reliable if they just PM you the file separately; much faster than uploading ingame. though i understand its a lot more hassle than just ingame /loaddup stuff.