TheWalls2
TheWalls2
Simple, player-directed plugin allowing for Walls games to be created and managed easily.
Brought here by an update notification and can't find a newer version?
Go to this Dropbox page to look for the newest version (Warning: Not approved by BukkitDev staff)
Features
- Virtual mode (disables redstone, optional time notifications, configurable time until walls drop)
- Automatic update notification (since v1.3)
- Join a queue for the next game, teleporting you to the waiting area
- Leave the queue, teleporting you back to where you were before
- Separate inventories
- Optionally join team 1–4 (will be auto sorted into a team otherwise)
- Command to start the game, activate the redstone, and teleport players to their starting positions
- Block rule-breaking (such as breaking the walls, or doing anything before the game starts)
- All dead players will respawn at their previous locations
- 1 team can win the game
- The winner will receive a configurable prize (default: 1 diamond) and be teleported back to their previous location (Supports Vault for economy)
- The world will be automatically reset to its normal state when someone wins the game or an admin uses the command '/thewalls restoreworld'
- Automatically attempt to start games 10 minutes after the server starts and every 15 minutes
Step-by-Step Guide
Commands
- /thewalls - Display TheWalls2 help
- /thewalls join - Joins the game queue
- /thewalls leave - Leaves the game queue
- /thewalls team <1–4> - Joins a team
- /thewalls start - Starts a game
- /thewalls stop - Stops a game
- /thewalls restoreworld - Restores the world
Bold - Requires OP or permission node
Aliases
/thewalls - /tw, /twalls
Permissions
Configuration
To-Do
- Concurrent games
- Team chat
- TagAPI integration
- Compasses point towards enemy players
- Localization
- Suggestions please (Post in the comments or on GitHub)
Bug Reports
Please post these on GitHub or, if that's not possible, in the comments below. Please provide (at minimum) the following information:
- What the most likely cause of the issue was (such as what you were doing at the time)
- Any errors displayed in the console (Please use pastie.org for these!)
- The version numbers of the plugin and of Craftbukkit (Don't say 'latest'!)
- Any additional information you can provide, such as potentially conflicting plugins
Need Help?
- Make sure you have read the Step-by-Step Guide
- Post a ticket on GitHub
- Post a comment on this page
- E-mail me ([email protected])
Servers using TheWalls2 (follow the link for information on getting your server listed)
I also like Grandriver's ideas for the signs . I would like to place the lobby in my main world amusement park so players can go there then hit a sign to select a team then a player hits start game and there is a 1min countdown til game actually starts to give others a chance to join in.
@Hoot215
thanks for feedback :)
@tohosensei
Thanks, and it's weird that it works on your main server but not your test server, but at least you got it working :D
Sure, I'll add it to the server list now.
Having multiple lobbies seems to be a popular request, so I guess I'll have to add that to the to-do list officially, but it might take a little while considering all the refactoring I'll have to do.
@pure07
By highest I assume you mean lowest in the code. Bukkit's priorities are reversed. The idea of just cancelling the death event is a good one... but unfortunately it's not possible. I'd have to actually cancel the damage event that kills the player, and then I'd have to calculate if the player is actually going to die from the hit and so on. It gets pretty complicated, so unfortunately that's not really an option (or at least it would be very buggy). A solution I just thought of would be to teleport the players 1 tick later than usual, to ensure that they're spawned where they're supposed to.
Thanks for the offer to donate, I really appreciate it. I'll add a donation button right now.
EDIT: Here it is.
@Hoot215
With the deaths it happens everytime someone dies in thewalls2. I think it may be because multiverse is set to highest priority when handling the respawns on my server. Ive got them spawning in the lobby world by using /mvm set respawnWorld. Maybe try canceling the PlayerDeathEvent dropping the items and just teleporting them to where they joined if you havent already.
Ps anywhere to donate?
Hey Hoot, I actually got TheWalls2 working on my own official clan server. For some reason there was something wrong on my clan's test server, so I decided to move it over to my clan's server. For some reason, it worked... ._. , but anyway thanks for all your help, so far this is one of the best plugins I had in a while for our server. I'll keep on updating any bugs that can occur.
One last request, can you add my clan's server? Here is the information if you get the chance to add it :D (I'm not the main owner of the server, but I am one of the main server managers. If you need my IGN, its blackopseals)
Server Name: DeadlyCraft Owner: DGBrklyn IP: thedgclan.com
Cheers!
-Toho
P.S. One suggestion that I have is that can you make more than two lobbies of TheWalls2? If that is actually possible, I would gladly appreciate your decision.
@pure07
Really? That's unusual because in the latest version I make sure to load chunks before teleporting players to them. I'm not quite sure why that would be happening. I'll try to fix this issue, but if I can't, maybe you should consider using Spout for teleport smoothing.
For player deaths the only issue I can think of is that if the server is restarted and a dead player joins and respawns they won't be where they were before. Can you remember any scenarios where this happened?
@cotjones
I think I might have discovered an issue with the world reloading (although I'm not sure if it's related to this), but in your Multiverse settings, is the world spawn set to always be loaded? I'm not sure about this, but I think that if the world spawn is set to always be loaded the world can't unload properly. Try disabling that if that's the case.
@GrandRiver
I might implement some kind of add-on support and have add-ons for things like this instead, because I don't really think this is something vital to the plugin, although I'll definitely consider it.
@Hoot215
From a personal standpoint I would love to have The Walls plugin to handle the sign handling, but we'll give this a try with a command sign plugin, but would love if you can add the sign functionality to the plugin itself. :)
Please Help, I'm having a problem. I loaded the plugin and a map I got from the link into the server files, Then I used /mv import thewalls2 normal. It loads up fine, I can get into the map, I can start a game, but the world will not reset. It's throwing no errors, the spawns are correct, everything is correct cept no resetting. The map stays how it was last game.
Also tried the /thewalls restoreworld command. Same thing, no restoring.
Extra info: I'm using v1.5.1 of thewalls2 build 2358 of craftbukkit
I'm not positive I have it setup correctly But I followed the "step-by-Step guide"
Great plugin exactly what im looking for thank you so much. A few problems some people spawn below the starting block and fall through the world. Also the listener for player deaths doesnt seem to be catching everything as they spawn at their /homes sometimes.
@GrandRiver
Yes, it is a separate world, and yes, you can use "/thewalls join" from any world to be teleported to the queue area.
That sounds like a decent enough idea, but I believe that this could be accomplished with a command sign plugin. All you'd have to do would be remove permission to use the join command and use the command sign plugin to execute the command for the player. If you really think that I should add this in, I can, but I'd rather not when it can be accomplished using another plugin quite easily.
At the moment, it only supports one arena at the time (and it would likely take a lot of refactoring to change this) but multiple arenas are planned.
I'm a little fuzzy on how this plugin works on servers with standard survival or creative worlds and have a couple questions before I give it a shot...
Is it like the Survival Games where the arena is a separate world from the regular worlds? If so, how does one join a Walls game from the main world(s), just the /thewalls join command?
Is there the ability to set up a lobby in the main server world like the Survival Games and not simply use the command to join (we strive for realistic or themed transportation on our server, not just simply teleporting everywhere)? If not would you consider adding a feature like that (ie. click a sign to join an arena so it limits where players may join the game from)?
Also, does this support multiple arenas or only one arena at a time?
@rythar
Sure, I'll add it to the to-do list.
Can you please add some sort of disconnect timer I would like to give payers 30seconds or so to log back on if dced.
@tohosensei
That's... extremely unusual. I really have no idea why that's happening, sorry. It might be some option you have set in your Multiverse-Core config. Maybe you should ask the Multiverse team about it.
EDIT: Now that I think of it, do players actually have permission in Multiverse to teleport to the world 'thewalls2'? It's possible that you've somehow disabled permission to teleport to that world.
@Hoot215
yea so this is what happened. I update to the latest multiverse core dev build, same problem came again. thewalls2 map is listed under multiverse and what I realized that when i mvtp to thewalls2 map, it teleports me somewhere in my main world where I first typed /tw join
@tohosensei
It appears that we're using the same build, so I really have no idea why this is happening. Does 'thewalls2' appear when you do "/mv list"? If not, try importing it. Otherwise, you could check here for a newer dev build, but it probably won't make a difference.
Dropbox link: HERE
v1.5.1
Dropbox link: HERE
v1.5
Note: (Read changes for 1.4.1 as well)
@Hoot215
will do I'll give it a try
The latest i know is Multiverse 2.4AB. Is this the current or is there a version better or more latest than 2.4AB?
@tohosensei
Hm... then I can't imagine why it would be throwing that error. Maybe you could try updating Multiverse-Core to the latest build. Just so you know, I'm running build 2.4-b527.