-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Toggle True/False "Set return portal to origin" #76
Comments
Coincidentally I have already added this functionality in my test version (not yet released). That is, every portal you connect to, will also connect back to the portal you've just interacted with if it did not yet have a connection. So if you also use the "default portal" functionality, the workflow would be as follows:
So now your home portal will always connect back to your roaming portal. Does this adequately address your request? |
That's fantastic! Would you also be able to add the functionality, as a toggle, to connect portals back to the one you just intereacted with if they were already connected to another portal, as in my example? But I love the idea of your bullet points! Can't wait to see it in action. |
I think that's doable. Do you think it makes more sense to configure that per portal, or maybe as a global setting in the config file? |
Honestly, that's up to you in regards to coding (I wish I had the brainpower to do that stuff myself!). If it's possible to have:
So in essence, the way I'm imagining it, with the system toggled ON: Obviously, with the system turned OFF, Portal2 would never reconfigure to Portal1 and stay connected to Portal3. To me, since I don't know coding, I'm not sure what kind of a headache "per portal" would introduce to you to figure out. If you already have an idea and it's not a big deal then it would be amazing to have the Global/Per toggle as well. If not then maybe just the Global setting if the system is turned ON. Also, I'm just dreaming here. If you think coding-wise it's possible then the more options the better. Amazing work! I wish I could buy you a coffee but the link isn't working :( |
The coding isn't the biggest hurdle (although not a small one either); it's making it make sense in the UI, and keeping the concept understandable for other users, that makes it challenging. I'll give this some thought over the coming days :)
I had a strange issue with BuyMeACoffee where they suddenly decided to flag my account as fraudulent for no reason what so ever, so I now very strongly recommend against using their service. Alas, this leaves me without a donation service as I can't find any other that lets you use paypal without exposing your real identity. But where did you find the link? I thought I cleaned them all up 😅 |
Ahh good call, thanks for letting me know! |
Hi Spike!
In love with XPortal. I have noticed a few times, though, that when I'm thinking of my tasks to do I forget to set the return portal back to where I came originally came from and I wind up somewhere completely different.
For instance, I set a portal down beside a Mistlands Infected Mine (MST-IM02) and return to my base to gear/food up. Then as I'm thinking about going to said Infected Mine I walk back through my active portal at my base, only to teleport to MST-IM01, my first mine, because that's what my base was set to.
Idea 1: display a message in the center of the screen saying "Portal set to: XXXX" to remind where it goes (yeah, I know you can hover over the portal structure to see that already :))
Idea 2: set the return portal destination to where you just came from, like how non modded portals work. In my example, even though my last base destination was MST-IM01, I just came from MST-IM02 so the base portal would be automatically set to MST-IM02.
Both ideas would have a CFG toggle to True/False, of course, for people that don't like these ideas or want to daisy-chain portals, like Farm spots to go from XX-Farm1 > XX-Farm2, then XX-Farm2 > XX-Farm3, etc. without them being changed automatically.
Thoughts?
Thanks, much! <3
The text was updated successfully, but these errors were encountered: