Inactive [TP/HOME/WARP] Waypoint v1.6.4(beta)- Teleportation points, home, spawn, and warp management. [1609]

I want those glasses... the wood paneling... and that coffee mug.
...maybe the chair...

[WP:WARP] is the correct setup.

/spawnadmin set

It's just an error saying that I'm trying to turn a true/false value into a string and use it that way. I'll make a note to fix it. It's not a severe problem. You can safely ignore it.

Another oddity I notice the more I started playing and experimenting with waypoint and teleporting is that some teleportation destinations will consistently/repeatedly create huge gaping world-holes every time I teleport to it, but if I keep playing with different locations in the same area, I will eventually find a spot that behaves as a nice destination.

Usually I just "float" out of the hole until I get to ground, leave the game and reconnect and the hole is gone.
...kinda cumbersome...

Is this a mod issue, server side issue, a mincraft issue, or are there certain precautions I should take when creating a warp destination?

I seem to have better luck if the destination is away from complex structures.

Comments? Suggestions?

-Joe

It's a chunk loading error. You might be running an out-of-date version of Waypoint. Because I know in the past couple beta builds he added a pre-fetching of the destination chunk so that wouldn't happen. If it continues to happen, just get Spout and it should fix your problem.

I didn't actually have it do any prefetching...I only added some code to force chunks to load. Which I'm not even sure if it works, because the big gaping holes still happen for me

Doesn't happen for me and I'm not running Spout anymore either o.o

Oh :3

1529

Can you try updating to at least CB #1609 and the copy of Waypoint from this link?

Quick question, did anything ever happen with implementing an override perm node for waypoint / warp limits (mainly waypoints in my case, but easy to do both I would assume) That either completly overrides the limit, or sets it to a different value per permission node.
Would be epic if it already is / almost is implemented.

He hasn't been working on any coding lately. So no :\

Actually, it is implemented. I did do some work. But I did it quietly.

Maybe you should not do it quietly so I can answer properly.

Can someone give me something to do or fix? I'm really bored and don't necessarily know what I have to fix or what features I need to add.

Well there are at least two:
#1
"It's just an error saying that I'm trying to turn a true/false value into a string and use it that way. I'll make a note to fix it. It's not a severe problem. You can safely ignore it."
(reference post 813)

#2
Since upgrading to the recent 1.1-R1-snapshot I noticed yesterday that when I tried to /tp a NON-OP'ed player to me it gave an error something to the effect that the player did not have permission to enter world vorlon (vorlon is the world name). I do not have the permissions mod. This was not a problem a week ago. I can TP to them, but I cannot TP them to ME.
I have added a couple mods in the last week and have not ruled out some type of conflict, but I figured you could test it, unless you want to test it on my server.

The newer versions of Waypoint, players need access in a world to be tp'd, even if it's in the same world.
waypoint.world.access.<world>

can this be done without using a permissions plugin?

Waypoint worked fine like 3 days ago for me..
I didn't switch versions or anything
But now it won't detect PermissionsEx as my permissions plugin
It just defaults to Op Only
I have
PermissionsEx version 1.17
Minecraft 1.1
Bukkit build 1772
Waypont 1.6.4 Beta
Ideas??
- rawr

No.

PEX 1.17
#1774
1.6.4
Works for me. Make sure you're running the Permissions layer also that comes in the PEX .zip

ok. so I bit the bullet and installed permissions... permissionsbukkit 1.2
Been playing with it for an hour, and tested basic minecraft general permissions. Behaves as expected.

Next, the goal was to make a teleport sign that a "default" new player could right click on and teleport.
I gave the default group every possible command and then created a warp sign.
/warp add overhere2
I then attempted to test it, both as an OP and DEOPed player. I intentionally left my name out of the config.yml file to simulate a new "default" player.

As long as I am an OP, the sign works fine. As soon as I DEOP myself, I get the error message (in RED):
"[Waypoint] You do not have permissions to access this warp." (and I made the warp sign)

I tried adding waypoint.*: true as well as each individual permission node (shown in example below).
I'm sure there is something I am missing or not doing or not understanding.

Ideas?
Here is the current config.yml
(player1, 2, 3, 4 were changed so I didn't post my admins names)
Perhaps an eagle eye will spot the glitch...

Code:

users:
  player1:
      permissions:
      groups:
      - admin
  player2:
      permissions:
      groups:
      - admin
  player3:
      permissions:
      groups:
      - admin
  player4:
      permissions:
      groups:
      - admin
 
groups:
    default:
        permissions:
            waypoint.basic.add: true
            waypoint.basic.delete: true
            waypoint.basic.teleport: true
            waypoint.basic.invite: true
            waypoint.basic.invite.accept: true
            waypoint.basic.invite.decline: true
            waypoint.basic.list: true
            waypoint.home: true
            waypoint.home.set: true
            waypoint.home.set_on_bed_leave: true
            waypoint.admin.spawn: true
            waypoint.admin.spawn.set: true
            waypoint.admin.spawn.save: true
            waypoint.admin.spawn.load: true
            waypoint.admin.warp: true
            waypoint.admin.world.create: true
            waypoint.admin.world.import: true
            waypoint.teleport.teleport: true
            waypoint.teleport.location: true
            waypoint.teleport.here: true
            waypoint.spawn: true
            waypoint.warp: true
            waypoint.world: true
            waypoint.world.teleport: true
            waypoint.world.list: true
            waypoint.world.access.*: true
            waypoint.warp.access.*: true
            waypoint.warp.create: true
            waypoint.warp.delete: true
            waypoint.warp.list: true
            waypoint.sign.link.create: true
            waypoint.sign.link.delete: true
            waypoint.sign.warp: true
            waypoint.sign.link.use: true
            waypoint.sign.world: true
            permissions.build: true
    user:
        permissions:
        worlds:
            vorlon:
                  permissions.build: true
        inheritance:
        - default
    moderator:
        permissions:
        inheritance:
        - user
    admin:
        permissions:
            permissions.*: true
            waypoint.*: true
        inheritance:
        - moderator
messages:
    build: 'YO! You do not have permission to build here.'

Getting Waypoint and PermsBukkit to work perfectly almost never works lol. I'd suggest switching to PEX or bPerms. Perms3.1.6 is outdated but it still works. That's the only suggestion I can give you :\

Got a q, is there a way or will there ever be a way to have sign warps like xwarp. What we want to know is have one sign teleport different players to other places? So say we have a sign that says skyland we would create in the skylands 3 warps. each named skylandhome(something) and then set the owner for that skylandhome to each differentplayer so player1 would own skylandhome1 player2 would = skylandhome2 etc.

I think xwarp used to make it so that we could pretty much set there home somewhere. They could not use the /home command to get to it but when we put on a sign home. A player could click it and be teleported to there home. So if I clicked the sign i would tp to skylandhome1 and if another player clicked it they would be tped to skylandhome2 And such I think you get the drift.

So yeah that is basic of what we want. Know if that will happen? or a way for us to get to this. Thanks and awesome job so far on your plugin!

Basically what you're saying is you want a sign to use a command. Because when you link a sign to waypoint/warp it can only be linked to one position at a time. But having a command set to a sign (/home) it will work for anyone that punches or right clicks the sign, that's why multiple people can use it.

I'm not sure if Waypoint will get into sign commands, but it might happen.
You could make that a suggestion in a cleaner more formatted response I'll make sure miyoko takes a look at it.

yeah sorry was kinda saying it while my owner was tellin me lol.

Idea's

player 1 (p1) and player 2 (p2) Both have a place in the wild
p1 sets his warp as p1house
p2 sets his warp as p2house

In a town there is a sign. This sign says

[WP:WARP]
House

Or however you would edit the sign.

When p1 clicks this sign he got teleported to his house
When p2 clicks the sign he gets teleported to his house

I know mywarp has that:
'' PULLED from mywarp its no longer supported tho!
...is Intelligent
Sometimes, warps can be long and hard to remember. This is where MyWarp's auto-complete abilities come into play. It tries to find the most applicable match, and sends you there. It only considers warps you have access to, and will not send you somewhere unless it knows it's correct.
A few examples:
There are warps: {"Mob Spawner", "Farm", "farm", "tkelly's house", "joe's house"}
tkelly has access to: {"Mob Spawner", "Farm" "tkelly's house"}
joe has access to: {"Mob Spawner", "Farm", "farm", "joe's house"}
No matter who uses /warp spawn, they will be sent to "Mob Spawner"
If tkelly uses /warp house, he'll be sent to "tkelly's house"
If joe uses /warp house, he'll be sent to "joe's house"
If tkelly uses /warp farm or /warp arm, he'll be sent to "Farm"
If joe uses /warp farm, he'll be sent to "farm"
But if joe uses /warp arm, it equally matches both "Farm" and "farm", so will send him to neither.

http://dev.bukkit.org/server-mods/mywarp/
"

WE are tryin to get this and have it so that players can't just type /warp to go places they have to use a sign. But also want it so that we don't have 100 signs. Anyway that is the gist of it. Thanks for looking at this
Respectfully,
Irish

There's an easy and simple way to do what you want.
Only give them the nodes for /home and /home set so they actually have a home. Unfortunately those cannot be controlled with signs. Although, don't forget to give them the nodes to use signs. If I'm correct, they should have these nodes.
waypoint.world.access.<worlds> (required to use signs/commands/teleporting)
waypoint.warp.access.<group name> (set in the config file)
waypoint.home
waypoint.home.set
waypoint.sign.link.use
waypoint.sign.warp
waypoint.sign.world (if you want world warping through signs)

And the people who are creating the signs should have:
waypoint.sign.create
waypoint.sign.delete

As for the Farm and MobSpawner warps, those will have to be public warps which would be:
[WP:WARP]
Farm/MobSpawner
<description>
<description>

Ok so i am having a problem with this. In the config file under warp.permissions i added a group for every one i had in my actual permissions file. Was i supposed to do that? And then in my permissions file i only added the waypoint.warp.access.Member in my members group. But i didnt add that to each group. Should i and am i doing anything wrong?

If "Member" is the lowest group in your Waypoint, everyone should have that node (if they all don't inherit it already) because if Member is your default group, everyone is going to need the node to use all default warps.

Fixed in the development build found here.