PneumatiCraft/OpenWarp — Issue #45: Prioritization of public / private warp name conflicts
Author: chris-leonard
Created: 2011-12-04 18:09:30+00:00
State: open

Heya Lithium,

If there is a public warp and a private warp with the same name, the public one takes precedence. This surprised me, since in other areas (such as java coding ) more specific namespaces generally take precedence over less specific ones. But I thought, hey, no problem, just different, move on.

However, there's one problem I can't figure out. If there is a public warp named Statue, and I make a private warp also called Statue, I can't figure out how to use, rename, or delete my private warp. Is there a way to do this? If not, namespace qualifiers would be nice. For example: /warp delete my.Statue vs. /warp delete public.Statue (assuming that's my public warp and I can do that).

The problem is this: if one player knows the names of another player's private warps, the first player could create public warps with the same names. Then the second player (a) could not use or delete their own warps, and (b) if they are at quota, can't create any others, (c) allowing the first player to be a total PITA.

Thougths?

Thanks again for your continued work on a really good plugin!