Oh definatly removable would be needed!
In most graphics apps, and 3D modelling tools you have a group/ungroup option.
You can even group groups.
Oh definatly removable would be needed!
In most graphics apps, and 3D modelling tools you have a group/ungroup option.
You can even group groups.
Hi Red, I think this would be a useful feature for everyone
Being able to make blueprints is great, but it would be even better if when creating said blueprint there was a checkbox to group objects. That way when it comes to remove the blueprint by hitting it with a pickaxe (for example) the whole blueprint is destroyed, as opposed to the current setup, where you have to destroy each individual component that makes up the object.
For example, I've made my own sconce, after a while I decide I don't like it's location, maybe I want it a little higher/lower (long after undo command has expired). Currently I have to remove each object component one-by-one.
Can we maybe please get this feature in the future
I haven't played around that much with this but will it be possible that admins can decide what a player can and can not do within a certain area? ie no fly / no destruction/ but able to open doors/chests? maybe it's already there but fully implemented yet?
Yes, with the new area protection you set a default permission file to it. When adding players (1+) to the area you can set individual permissions for each player.
Very impressive!
Also, hold down c to get the context menu up. Here you can change things like the rotation degrees.
Basically a UI for setl setp setr
Good to hear you sorted it out
You're welcome
Sounds like you don't have a permissions folder.
There should be one in there called: permissions.Example
You need to rename this folder to just 'permissions'
Or, as I did copy and paste this folder and rename the new one 'permissions' that way you always have the default one as a backup.
Tiny bug, the help text for the 'right click to reset construction colour' is in German in the English version.
Jackle80 ther's an option for this in the default permissions file.
Just port 4254 is open
Sorry, was only trying to help. I read the above and when someone says 'just', to me that means "one".
I second this.
Real hacking!
That's your problem. Query port is always -1
So if your server was on 5000 you also need to open up 4999.
Let me know if that doesn't make sense.
Open 4253 TCP
Port
The server port can be set in the server.properties file (see "Server_Port"). By default, the server uses port 4255 TCP and UDP. The query port (which is required for the server to show up in the server list) is always serverport-1 TCP (so when using the default server port, it's 4254 accordingly).
Leave the IP field in the configuration file blank.
Just a funny video from the new MR server.
Awesome