Yes, Timbad. I forgot to look in SRC directory. Sure, it's a procedure command, not a personal data.
You can add a new enclave using the same template but not the data and still locked for non jedi player.
once the server build is correct. I needed to back to an older snapshot to avoid that invisible bug on build.
You can add a new building using those same templates and you won't get the "permission" message.
Fully silly. Now, my new "senate.iff" building Lua is working like a common building while "light_enclave.iff" has the walk denied. It was really strange when my new lua hadn't any Component active in the file...
Awesome to hear! Nice work. I know the pains of when you have it correct but messed up elsewhere, making you think what you did was actually wrong, which leads to questioning existence and the universe, because nothing makes sense anymore, haha.
Happy you managed to work it out in the end though. I sadly can't be of more help in general when it comes to Core3, as I'm purely a client guy.
Also, you can remove line 69, either by commenting (//) or just erasing the line, so that the system message doesn't display.
Basically, from what I can see it's a container component that just checks the buildingobject permission, returning true at the end will just make it always allow. But, I don't know if there will be a cell issue.
This is all assuming you even want the EnclaveContainerComponent set on your enclave building in Lua, if you want the other features it provides.