Raising priority due to a changed behaviour.

Thank you for the report, I believe this is not meant to be a support ticket.
Will convert it to a bug report instead.

Right, this isn't a bug then though. The Personal rank is to be used within a faction, it's meant to secure it from other faction members.
Any faction signature will stop an outsider from using that entity, putting it on personal wouldn't change anything in that behavior.

Duplicate, merging tasks.

Nothing to add.

Caused by fix attempts in T1466, merging tasks.

Ok, just wanted to update this.
Reloaded the server that didn't help.
Mongoon was the only faction listed with me attached to it saying own:
I decided to see what would happen if I simply created the old faction with the same name.
Well when I did that actually allowed me control back of the station and the faction block.
It now shows both factions on the faction list.

I understand what Jeryia is saying. If there in no faction block on the ship anyone can just take the ship, you need to place the faction block add you faction then set it to owner, but you can only do this when in a faction. so basically if you are not in a faction you can not use the faction block and in turn you can not lock your ship. yes you can make a faction of 1 person and then do this to lock your ships but if you don't want a faction ect ect, then you can not lock your ships. I just tried it with my brother. if I build a ship and then exit the ship he can just take it, if I use a faction block then he can not take it. its pretty simple really

Merging with other task.

Thank you for the report, this task is caused by the fixes for T823 and T1570.
Merging the report, not putting this one on private though since it's not needed.

Unsure how much it affects FB init w/ macOS...but in older releases, forcing FB on w/ the hotkey caused no crash-related issues that I experienced, and dramatically improved performance.

Nothing to add, great report.

Thank you for reporting this issue but that was already noticed in T2044. It only happens in the Pre-release candidates (0.199.491/0.199.492)
Merging tasks and updating info.

Perhaps I'm misunderstanding what you're trying to say, but the Personal rank is only useful within your faction. For anyone outside your faction, they can't control your entity anyway no matter what the faction rank is set to.
I don't see how it could work if you're not in a faction?

Unfortunately MacOS did not provide backwards compatibility from core 3.2. That means that it's impossible to request a context without forward compatibility, which removes fixed function pipeline. This is used by the current text rendering library, and in a few other places, since I always went with backwards compatibility over using the latest openGL without a fallback.

Thank you for the report.

Ah great,
you are using the pre-release build for this.

Thank you for the report,
will merge it into the existing report about this problem, to add your information to it.

Can you please upload the launcher.log from your launcher directory, right after trying the new launcher, and also the logstarmade.0.log after trying the old launcher.

Thank you for the report on this,
will merge it into the existing report about this.

Thank you for the report on this,
will merge it into the existing report about this.

It appears that any despawn command attempting to remove something with a space in it fails.

Still crashes on launch, same error as reported earlier, see T2317

The current bug with the power being placed in rows doesn't change with the camera movement. The state of the blocks that won't allow placement doesn't change until I set a block on the nearest blocks to the ones that won't work.
In short I put down a row of 100+ another 100 blocks.
At about block 170 and above I can't attach anything else to them.
So I connect a block to 169. That triggers the system to look at what else is attached and initialize blocks 170 to 200.
I can now connect to the blocks 170 to 200. I can set it so that I am 1 block away from these blocks when I place them down and it still happens.

The range test is only for the build mode focus, and allowing a defined sphere of influence. Plus limited total amount of those purple boxes.