StarMade v0.19549 Faction Permissions, Player Protection, Streamlining, and Fixes

[Criss]

Okay, fine with that. I only wish it had been done a bit more graceful, not simply clobbering existing setups.

Apart from that, excellent update so far.

It was not intended to replace keybinds if the keybind config was already there. Consider it a bug.

 

[TomW1605]

and permission blocks that can work on non-adjacent blocks.

a question for the devs (going to tag all the ones that have posted in this thread as i don't know what ones this relates to: Criss, Lancake, Bench) is this likely to happen?
[DOUBLEPOST=1452994536,1452994433][/DOUBLEPOST]

It was not intended to replace keybinds if the keybind config was already there. Consider it a bug.

would it work to get around this bug to copy our current keybind config file to the desktop before we update and replace the new one with the old one after the update?

 

[Bench]

a question for the devs (going to tag all the ones that have posted in this thread as i don't know what ones this relates to: Criss, Lancake, Bench) is this likely to happen?

Not for quite a while, it's a limitation of some of the mechanics and would require a rework of the permission block systems and the way C/V linking handles its data.

 

[Ithirahad]

Not for quite a while, it's a limitation of some of the mechanics and would require a rework of the permission block systems and the way C/V linking handles its data.

DAMN! C/V linking would make the permissions a lot more usable. ATM adding proper rank permissions to everything would have screwed up half my designs and devices, and so I just had to set the homebase back to having permission for everyone in the faction.

 

[Bench]

DAMN! C/V linking would make the permissions a lot more usable.

Agreed, and we did discuss the possibility of adding it, however hit the data flow roadblock that would require a bunch of going and changing how existing systems work to make it viable. It's a similar data flow issue that is also one of the roadblocks preventing logic gates being able to control gravity modules. The current system was optimized in the manner it is to allow for minimal network bandwidth usage especially as it applies to large logic systems at the moment (which still takes a while for massive logic systems to all load up and calculate the connections). So it's bigger than just a simple change, hence why it's still the way it is.

 

[TomW1605]

Agreed, and we did discuss the possibility of adding it, however hit the data flow roadblock that would require a bunch of going and changing how existing systems work to make it viable. It's a similar data flow issue that is also one of the roadblocks preventing logic gates being able to control gravity modules. The current system was optimized in the manner it is to allow for minimal network bandwidth usage especially as it applies to large logic systems at the moment (which still takes a while for massive logic systems to all load up and calculate the connections). So it's bigger than just a simple change, hence why it's still the way it is.

is it possibly going to happen in the future?

 

[Bench]

is it possibly going to happen in the future?

Not ruling it out

 

[Ithirahad]

I'm guessing that all the link networks will need dynamic optimization to determine how much data has to be passed for any given connection or set thereof?

 

[AssIn9]

They can still use the ship if you use faction rank permission modules to exclude rank of course.

Testing using a small ship with faction module set to 1, added a faction permission module adjacent to the core. Other faction members cannot access the core.

 

[Lone_Puppy]

The new key binds are intended. They make more sense to new players and players of similar titles. You can change them if you want to in the options menu.

I don't have a problem with new bindings. I only have an issue with when I'm in flight mode and I roll left, I suddenly find myself in build mode. Not fun when I'm in battle or manoeuvring.

Are there other keys assigned to rolling left/right?

 

[NTIMESc]

I don't have a problem with new bindings. I only have an issue with when I'm in flight mode and I roll left, I suddenly find myself in build mode. Not fun when I'm in battle or manoeuvring.

Are there other keys assigned to rolling left/right?

Default flight controls for a new install are Q/E to rotate ship and Space/LCtrl to move ship up and down. Z is build/flight mode and X does nothing in flight mode. As they said, overwriting your config was not intended.

 

[Lone_Puppy]

Default flight controls for a new install are Q/E to rotate ship and Space/LCtrl to move ship up and down. Z is build/flight mode and X does nothing in flight mode. As they said, overwriting your config was not intended.

Thanks NTIMESc. I'm not concerned or worried about my config being overwritten. I just wanted to know the new key binds so I can start using them. Maybe I didn't look hard enough on the key list.

Now I can get back into it.

 

[NTIMESc]

I just wanted to know the new key binds

Well, if you didn't have a new install, your config was most likely merged with the new keys, like mine was. I also had Z rolling and changing ship mode, but Q/E was still down/up. I had to just rebind the keys, setting build mode back to NUMPADENTER where I like it.

 

[Valck]

It was not intended to replace keybinds if the keybind config was already there. Consider it a bug.

would it work to get around this bug to copy our current keybind config file to the desktop before we update and replace the new one with the old one after the update?

Nope, tried it.
My workaround was sorting both old and new keyboard.cfg and diffing them so I could have a nice list of changes, and then manually replacing the changed key bindings with my previous ones, after launching and exiting the new version once to get the changes. I didn't look into automating it since there were changes in the key binding names too ('break' has become 'brake' at last, triple huzzah!)
StarMade doesn't care what order the settings in keyboard.cfg are, however it does rewrite them in its own sequence, so any sorting is only temporary.

 

[Criss]

Are there other keys assigned to rolling left/right?

The new defaults are Q and E.

 

[Lone_Puppy]

The new defaults are Q and E.

Thanks Criss. NTIMESc mentioned the new bindings to. I'll create a completely new install so I can start to adapt to the changes.

 

[alterintel]

So hate to be the party pooper, but what happened to shared thrust? I have two new ships which got killed with this update. One ship went from 8K of thrust down to 300 thrust, and the other went from 5K thrust to 1.2K.

What gives?
Thanks

 

[godmars]

So hate to be the party pooper, but what happened to shared thrust? I have two new ships which got killed with this update. One ship went from 8K of thrust down to 300 thrust, and the other went from 5K thrust to 1.2K.

What gives?
Thanks

beforehand docked thrust was independent of the main ships thrust. it basically took the thrust of the dock and then just added it to the main ship. so you could get a higher thrust after a certain point with docks(this was considered an exploit). with the new update the thrust you get from docks takes into account the thrust that's already on the main ship

 

[alterintel]

beforehand docked thrust was independent of the main ships thrust. it basically took the thrust of the dock and then just added it to the main ship. so you could get a higher thrust after a certain point with docks(this was considered an exploit). with the new update the thrust you get from docks takes into account the thrust that's already on the main ship

So can somebody give me a very basic understanding of how it works now? How is the thrust from the mother ship accounted for in the new system? Also it seems rather odd, that it wasn't in the release notes. Makes me think that the result is possibly unintended and due to change .... again?

Thanks

 

[godmars]

Makes me think that the result is possibly unintended and due to change .... again?

Thanks

i went and double checked on a whim and it looks like you get less thrust from docks now than just sticking the thrust on the main ship. as far as i know previous value was not intended, no idea if its supposed to be like this though.

1.2 mass with 4 thrusters on mothership and 4 on dock, 2 cores and 2 dockers: 15.7 thrust

1.0 mass with 8 thrusters on the mothership, 2 cores and 2 dockers at 20.2 thrust

..so it looks like there might have been a mistake