Suggestion: Warpto / Server Warp

[maximus_asinus]

Well I'm sure the subject doesn't explain my idea.

With the addition of the global playerlist, we're able to see when players on our buddy's list are online, even if they're on another server. My suggestion is that when you right click on the player on the playerlist when they're on another server, instead of the 'warpto' option on the shortcut menu, maybe a 'warptoserver' function so you can jump to the server that your friend is on. Of course every player would have the option to disable it.

[CheeToS2]

I like that idea, but instead of having a separate option, just re-use the "warpto" option (since it won't be of any use of the server you're on).

[talkingnoodle]

Good Idea.

[Tyhm]

And naturally your ability to warp directly to them on the target server would be a question of your access rights on said server...

[ApothiX]

Originally Posted by Tyhm

And naturally your ability to warp directly to them on the target server would be a question of your access rights on said server...

I think they are only referring to serverwarping to the server the player is on, not directly warping to them.

[jake13jake]

Well, warpto is there for staff
I'd think it would be good to have summon, etc. on there.

It would also be good for a server to enable an extra list of people for staff.
Ex. Events.
If (in event list)
Right Click + Summon
Right Click + Heal

[ApothiX]

Originally Posted by jake13jake

Well, warpto is there for staff
I'd think it would be good to have summon, etc. on there.

It would also be good for a server to enable an extra list of people for staff.
Ex. Events.
If (in event list)
Right Click + Summon
Right Click + Heal

For that to happen, I think the playerlist would have to be made into a Gui Script like it was before (in 3.1), but a lot of people complained about that :x

[jake13jake]

Originally Posted by ApothiX

For that to happen, I think the playerlist would have to be made into a Gui Script like it was before (in 3.1), but a lot of people complained about that :x

I don't think that would be necessary. Perhaps servers could make a .txt file with names of commands that can be triggered to the server and then distribute the text files to staff or players somehow on clientside. A lot of what would be needed is already in gscript. It would just need to pass the player object triggering the server, the description of the trigger, and the selectedlistplayers array which is already built into, at least, clientside gscript.