Nexus
Nexus Beta (0.4.10)
The Next-Gen Plugin
Highlights
26 commands w/ over 60 variations for complete control and vast flexibility. Player names are recognized w/ just a few letters instead of typing out every character. Multi-world support allows each world to have its own spawn point. Players can request teleports to others w/out the need of a mod or admin. Drag-&-drop installation w/out cumbersome config files. More than 15x smaller & less overhead than competitive plugins, such as Essentials. Disable specific commands that are not needed or conflict w/ other plugins. Powerful & layered permissions to fine-tune the capabilities of mods & admins.
Developer's Commitment
Many plugins are slow to update or cease development period, thus causing admins to seek alternatives and then need to learn new commands & permissions. As the developer of Nexus, my commitment to you is long-term support by constantly updating to the latest Minecraft/CraftBukkit versions and provide fast email responses. Each release is heavily tested striving toward a zero-error target & quick fixes to any known or reported issues. Nexus will always be less than 100 KB w/ next-to-nothing overhead. Seriously.
Features
- Administrative Commands
- Set Spawn, Player Homes, & Waypoints
- Time & Weather Management
- Player-to-Player Teleportation
- Private Messaging
- Item-Kit Integration
- Partial Name Recognition
- Multi-World Compatible
- Scalable Command List
- Language Support (coming soon)
Download the logo or wallpaper!
Other projects / plugins:
Shout, Slammer, Legacy
Comments, suggestions, or bug reports send email to [email protected].
@moose875
I have paused development as comments ceased and no one has emailed me about this plugin in some time. Now that I have someone interested, I am more than happy to unpause and continue forward. The "/time lock" command has proved to be a little more challenging than I originally anticipated as there are several ways I can implement this feature, yet I want to choose the most efficient method as to not be a resource hog.
I sure can add a /warn command. How would you like that command to work? Examples: "/warn (player) (message)" or just "/warn (player)"
Hello there, great work with the plugin. I've been using it on my server for months now and it's a really useful tool. I was wondering in the next update if you could fix the /time lock command and maybe also add a /warn command?
@reptile311
I fixed the /time command, yet I purposefully had the whisper.spy in two spots.
The /time [dawn .... stands under the inv clear with permission nexus.inv.edit The nexus.whisper.spy is double.
@reptile311
What is wrong with the command permission list?
Thanks for the new version. It seems, that your command and permission list is a bit messed up.
@DarthGizmo13
Read my "Deveoper's Commitment". It states "fast email responses". I pride myself on solving my customers' issues quickly. Let me know if you have any further questions.
@vioCode
okay Thanks for the quick reply some people take days.
@firecombat4
I currently do not have a method for changing command names, but that certainly is a good idea to add in the near future. I made the decision to use "tpr" as it makes more sense than "tpa". I made the switch from "warp" to "wp" as it flows nicely with the reset of my command name standards, plus its shorter.
If its really important to my customers, then I will be more than happy to implement changing the name of commands.
@DarthGizmo13
If you are using version 0.4.x do the following:
tools:
- 268,1
- 269,1
- 270,1
- 271,1
startingmoney:
- 266,25
Is it possible to rename commands?, none is really use to /wp set, and the tpa commands. Thanks
Hello Im a little new to the plugin community say one want to add another kit (in the kit config) How would one go about writing in the code for it. Default: tools: - 268,1 - 269,1 - 270,1 - 271,1
i tryed: tools: - 268,1 - 269,1 - 270,1 - 271,1 startingmoney:- 266,25
and : tools: - 268,1 - 269,1 - 270,1 - 271,1 startingmoney:- 266,25
please any help would be appreciated
Super awesome mod! Thanks for making this! Keep it lightweight! <3
@reptile311
I found the issue! The /kit command is relying on the /kick permission node. I obviously mistyped the correct permission. I shall release a fix in the next few hours.
I have a problem with the nexus.kit permission. I give the permission to the group user, but it don't work. It always say - you don't have the permission. All the other permission from nexus work. Curious is, the moderater group, who inherit from the user group can use the /kit command.
I also tested to give the guest group the permission nexus.kit. The user group inherit from the guest group. Both could not use the /kit command, but the moderator group could.
I use the cratbukkit 1.3.1-R1.1 Dev build, bPermission 2.9.12d and Nexus 0.43. It is a test server, that I use offline on my computer.
I post my server.log, bPermission group and user: http://pastebin.com/5FDxDBZ7
@reptile311
Thank you very much for the information! I actually did not catch that error so I will start preparing that code for the update. Also, I will ensure separate permissions as requested. I was unsure if anyone cared to have those separate so now that I know... I shall update soon!
Is it possible to seperate the permissions from kill and kill(player), so a player could kill himself, but no other player. The other is heal.
I know you will update, when there is a rb from bukkit, but Nexus 0.41 gives the following error (only to inform you):
@ownedoplos
I am currently waiting on a stable build of CraftBukkit before I release a 1.3 compatible version. I do have the plugin ready for the new update so once CraftBukkit has a Recommended Build, I will submit my compatible release. If you want a preview build, send me an email to [email protected].
why not make it for Minecraft 1.3.1 ?
@reptile311
I can work on that... but to be honest it will probably be one of the last things I do. The plugin is not setup to handle different languages so I have to go through my code adding the support for it. But your idea is a good one, so I will certainly work on that feature soon.