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

wait, what? is there any example of a save not properly aligned to the brick grid??

how does such a thing even occur?
old duplicator causes it if the first brick isn't a multiple of 2 plates on every axis

what happens if you try to place a build unaligned with the brick grid in vanilla/without a fix? will it round/crash/actually load them off by some?

wait, what? is there any example of a save not properly aligned to the brick grid??

how does such a thing even occur?
all it does is not plant bricks that aren't aligned.

old dups seem to load fine now, thank u
they don't load near you though, not really a problem but just thought it was worth mentioning

old dups seem to load fine now, thank u
they don't load near you though, not really a problem but just thought it was worth mentioning
the way the new dup loads things is it regenerates the duplication you made where you saved it. given how you can use the dup to reposition the thing back at your position, this isn't particularly troublesome

Version 1.3.2
•  Performance improvements for loading and saving duplications
•  Fixed: Connections not loading properly until a duplication has been saved

Use the automatic updater if you can, otherwise download again from the first page.
If the updater does not show an update, run this command: Updater.checkForUpdates();

Posted a bunch of news about your progress Zeblote. Thanks for your work.

what happens if you try to place a build unaligned with the brick grid in vanilla/without a fix? will it round/crash/actually load them off by some?
Bricks will always align with the grid by 0.5 (moving z is 0.25 if I remember)

what happens if you try to place a build unaligned with the brick grid in vanilla/without a fix? will it round/crash/actually load them off by some?

Bricks will align themselves to the nearest grid position, though not always in the same direction for differently sized bricks. So as a result, half the save doesn't load.

Code: [Select]
case 2:
%m =      "\c6Your version of the \c3New Duplicator\c6 is newer than the server's! Ask the host to update it! ";
%m = %m @ "(Server Version: \c0" @ $ND::Version @ "\c6 | Your Version: \c3" @ %version @ "\c6)";
messageClient(%this, '', %m);

Can you please not do this. Slayer does this too and it's extremely obnoxious that players ask us to update it, and we won't since our copy of it is purpose-modified. Joining the server already triggers like 7 messages, and I definitely don't need another one for a tool that only my admins will be able to use outside of the game.

I'd prefer everyone stays on the newest version, and players constantly bothering the host is a very efficient way to achieve that. What did you have to modify that prevents you from updating it?

I've not done that with the duplicator, I only used the fact that I modified slayer as an example. Regardless, I still think it's a cheap tactic and automatically reduces the perceived quality of the server. It reminds me of those modded minecraft servers where when you join 6 different mods will all tell you that newer versions of themselves are available.

old duplicator causes it if the first brick isn't a multiple of 2 plates on every axis
which old duplicator? the blue one or the really old green one

reduces the perceived quality of the server.

This. I hate it when add-ons add join messages, it looks super tacky imo

This. I hate it when add-ons add join messages, it looks super tacky imo
"This server is running stuffface's low-quality mod!"