Skip to content
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

Random destination! Like RTP type teleport, but when going through portal. #274

Open
srevenant opened this issue Jun 29, 2021 · 4 comments

Comments

@srevenant
Copy link

Please oh please give us the ability to do a RTP type teleport when somebody goes through a portal. I'd love to setup a destination and configure it as a random range w/standard RTP type protections (lands, claims, etc). There are a few good / current plugins we could borrow from, if not somehow integrate with (such as WildTP). Ideally one that pre-caches destinations to reduce load.

I could also have it run a command /rtp after they arrive at the destination (see other feature request). However, that seems kludgy to arrive and immediately TP somewhere.

@sekwah41
Copy link
Owner

sekwah41 commented Jun 29, 2021

I can look into adding though you realise you don't need a destination to trigger the portal? You can just have a command without a destination.

Best behaviour would be to add compatibility with plugins such as WildTP likely to support the claims and other things.

@zax71
Copy link

zax71 commented Sep 8, 2021

This can be achieved by using BetterRTP and an AP portal that runs /rtp

@srevenant
Copy link
Author

srevenant commented Feb 22, 2022

@zax71 I'm not sure how that'd work with BetterRTP or WildernessTP (which is what I'm using). The problem is the command '/rtp' is run on the origin server, not the destination (i have multiple servers w/waterfall). I'd like it run on the destination.

I've decided to dig into forking Wilderness TP and Advanced-Portals to see if I can figure out how to get it to work, since it doesn't appear the configurations as-is will support it.

Update: OMG WildernessTP is a nightmare. Comparing the code between it and BetterRTP yeah. WildernessTP has built-in holes and odd "kitchen sink" behavior. Let alone is written very childisly, with 12-year old "leet speak" variables and function names. What a nightmare. Do not use that one :D

@sekwah41
Copy link
Owner

It is such a commonly requested feature, I may take a look at implementing something for this.

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

No branches or pull requests

3 participants