-
Posts
268 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by GR00VYJERRY
-
One last thing. I am running the script and have the file in the hooks folder. I get the pope up that says that certain planes are blocked and some aren't but all are still flyable. I can still enter the client aircraft that are supposed to be blocked.
-
Hi,
it may be that the setup you are currently using requires a small adjustment. Can you tell me which scripts you installed where in order to get selective (by faction) slot blocking to run? SSB should be in /Hooks, ssbClient should be inside your mission. And you MUST run the mission as server, or it won't work.
-
-
Question about your modified SSB script. We run 4 servers off one machine and use the gui to run them. if i throw Ciribob script in the hooks folder is it gonna interfere with other servers? Alos what happens to client aircraft that are being piloted if the base they took off from are captured?
-
Thank you for your message. SSB is only working on the server instance that is loading that /Hooks folder. It does not influence other servers, not even those that share the same /Hooks folders. All it does is control access to slots for the mission that runs in the mission instance on that server. SSB has no known side-effects on other servers, and (AFAIK) also comfortably coexists with 'slotblock.lua' used in the "Foothold" series.
Please be aware of an important distinction that I probably have not made clear enough. ssbClient is not a modified SSB script, it's a separate script that is meant to be run inside a mission, and that interfaces with (i.e. requires) SSB running on the server. So to work, you need to install both: SSB in /Hooks, and ssbClient inside the mission that uses it
So what happens to client aircraft whose originating base is being captured? Currently, the players find themselves booted from their aircraft. Depending on which version of ssbClient you are using (stand-alone or DML) there might be slight differences, but an overhaul of this somewhat silly behavior is only planned for the DML version
-