Skip to content
This repository has been archived by the owner on Feb 6, 2023. It is now read-only.

Portals renamed when using Ward #13

Open
DaveJK opened this issue Mar 15, 2021 · 2 comments
Open

Portals renamed when using Ward #13

DaveJK opened this issue Mar 15, 2021 · 2 comments
Assignees

Comments

@DaveJK
Copy link

DaveJK commented Mar 15, 2021

Currently using version 1.0.4 on a dedicated server. When you use a Portal that is protected with a ward then the portal is renamed to the last portal that person traveled from.

1.) Portal 1 = Spawn
2.) Portal 2 = Home
3.) Travel from Spawn to Home
4.) Home is renamed to Spawn if protected by a ward

@CDK-Github
Copy link

I've got the same issue here. Would be great to work on a fix ! :)

@sweetgiorni
Copy link
Owner

Bug descriptions from Nexus:

We have found an issue with portals in the drop down list renaming themselves as a duplicate of another portal. This has happened numerous times. I checked the .cfg for V+ to see if there was a setting for this but nothing showed up, so cannot determine if there is a conflict there, but are not using any other portal mods. Has anyone else experienced this and if so, how did you fix it?

When you travel to another destination, where a guardian stone is active (you have no rights on this guardian stone) and you travel back, the portal where the guardian stone stands is renamed into your last portal you have named

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants