2BNB Essentials is for the members of 2BNB to include in their modpacks. This mod includes many custom config changes and other game enhancements and quality of life changes to make gameplay better for our members.
GNU General Public License v2.0
0
stars
0
forks
source link
Zeus - Curator object isn't initiating or existing on dedicated server #4
Description:
Sometimes the Zeus interface isn't accessible, and when someone attempts to use zeus, the Zeus key doesn't even ping any Zeus. This may be solved by 2bnb/2bnb-extras#163 if and when I fix that. Maybe not.
This issue appears in random missions, but will persist until all elements on a particular mission are moved to another mission and the mission is re-constructed. Sometimes it persists even after that, which leads to the belief that something in the mission causes the Zeus slots to break... but we have no idea what.
The issue appears only on dedicated servers.
Steps to reproduce:
Create a random mission
Load the mission on the server
Go into a Zeus slot, or don't and log in as admin instead
Try to open Zeus
If you're unlucky, you have no access to Zeus in certain or all slots... it won't even "Ping" a "Curator" object... almost as if there is no Curator object present!
Where did the issue occur?
2BNB Server
RPT log file:
Will add once a mission is found to have this issue again.
Arma 3 Version:
2.00
(stable) 2BNB Extras Version:7.0.1
(stable) 2BNB Modpack Version:3.3.0
Description: Sometimes the Zeus interface isn't accessible, and when someone attempts to use zeus, the Zeus key doesn't even ping any Zeus. This may be solved by 2bnb/2bnb-extras#163 if and when I fix that. Maybe not.
This issue appears in random missions, but will persist until all elements on a particular mission are moved to another mission and the mission is re-constructed. Sometimes it persists even after that, which leads to the belief that something in the mission causes the Zeus slots to break... but we have no idea what.
The issue appears only on dedicated servers.
Steps to reproduce:
Where did the issue occur?
RPT log file: