Search the Community
Showing results for tags 'permission'.
Bonsoir, Nous avons crée dans notre organisation et nous rencontrons quelque souci ce jour suite au déménagement. Esque quelqu'un pourrait nous aider en vocal, car au bout de 3h ont rage quelque peut. Donner moi votre discord, merci. ? Flo
To accomplish this some changes would be needed. The goal of these changes is to allow the automation of selling vehicles. To accomplish this permission should be able to be changed with Lua scripting. In order to automate selling a ship, the Lua scripting would change permissions once the buyer has completed the correct input (paying for the ship). On top of these changes there needs to be a permissions added that allows someone to fly and build on a structure but not be able to blueprint the structure. Otherwise you could spend hours designing a ship, sell one, and then watch everyone blue print hundreds of them without getting an in game dime. This could be accomplished 2 different ways. Method one don't allow blue printed ships to be blue printed. Only the original ship can be blueprinted. Method two add a second permissions type for blueprinting. Selling ships would be difficult and probably pointless without these features.
A list which lets us define who can not interact with an element. With only a permission list no combination of sensors can distinguish between: Only an authorized person is in range Both an authorized and any other person are in range For example, you can not have a door which automatically opens only when you're alone. It would also help attempts at starting civilizations, since it would allow having public spaces by default and banning particular people from interacting or building in them.