search

SE-Nexus / SeamlessClient

A Client side plugin to allow switching between servers seamlessly in a Nexus Server Network
MIT License
0 stars 1 forks source link

Issue with safezone differences between nexus sectors #8

Closed Thermi closed 3 months ago

Thermi commented 3 months ago

When switching nexus sectors that have differing safezone settings, the setting of the destination sector is not applied.

Casimir255 commented 3 months ago

Is this a game config safezone setting? If so I'm not finding any specific safezone setting

Casimir255 commented 3 months ago

Please add more detail with the issue and what specific safezone setting that is not applying

Thermi commented 3 months ago

These are the sandbox settings:

Sandbox.sbc PVE

    <MyObjectBuilder_SessionComponent xsi:type="MyObjectBuilder_SessionComponentSafeZones">
      <AllowedActions>Drilling Welding Grinding Building LandingGearLock ConvertToStation BuildingProjections</AllowedActions>
    </MyObjectBuilder_SessionComponent>

Sandbox.sbc PVP

    <MyObjectBuilder_SessionComponent xsi:type="MyObjectBuilder_SessionComponentSafeZones">
      <AllowedActions>All</AllowedActions>
    </MyObjectBuilder_SessionComponent>

What is not being correctly changed is the ability to shoot weapons. It impacts both weaponcore based blocks as well as the vanilla handheld weapons. my client allows me to "shoot" the vanilla assault rifles after moving from a sector where shooting IS allowed to a sector where shooting is NOT alllowed. However with "shoot" I mean I can click and it seems to consume ammunition, and I see a hit marker, but there is no bullet or bullet trail and there is no actual damage. Reconnecting via F5 fixes that.

When moving from a sector where shooting is NOT allowed to a sector where shooting IS allowed, the weaponcore based weapon blocks can not shoot. They can lock, reload, ..., but they can not shoot. Reconnecting via F5 fixes that.

EDIT: Info from admin:

In the game, it's named “Global Permissions.”

Casimir255 commented 3 months ago

Should be fixed on latest update