Add all players that ever joined to the whitelist

This would allow all players that ever joined the server to be on the whitelist. A use case would be if the server i being spam attacked; or you wanted to host an event for your server regulars. It could draw the information from the player.dat files.

/freeze r[epository]

Disable the whitelist

This would allow you to disable the whitelist easily.

/freeze d[isable]

Add a player to the whitelist

Yes, I'm aware you can do this in vanilla. However it would be nice to have it implemented into the plugin.

/freeze a[dd] {player_name}

Multiple "pre-saved" Whitelists

This would allow you to have multiple "pre-saved" whitelists for different events or occasions. It would basically save the current whitelist like a schematic on worldedit.

/freeze s[ave] {whitelist_name}

To load up a whitelist, you would run the command.

/freeze l[oad] {whitelist_name}

To view a list of saved whitelists.

/freeze v[iew]

To delete a saved whitelist.

/freeze r[emove] {whitelist_name}

Please consider these features as many people I have spoken to believe that these features would make your plugin shine even more. Thanks for your time, and thanks for coding this in the first place.

I guess sorry to 'bump' this, it's just been a while and don't want to see such a good plugin die away ;p

Oh man...between school and iPhone projects and other stuff this has been at the bottom of my pile for awhile, especially since I was rewriting the command system to be easier to expand in the future. I might have an hour or two to work on this today, if I shove some other stuff off to tomorrow.
Sorry for the long wait :)

On Sep 21, 2013, at 8:29 AM, Electroid [email protected] wrote:

I guess sorry to 'bump' this, it's just been a while and don't want to see such a good plugin die away ;p

—
Reply to this email directly or view it on GitHub.

Quick update: I have a few things done, but I desperately need to rewrite the command handling, and well...thats time consuming, again school is in conflict. I will keep trying to do as much as I can, but I might not make significant progress until Thanksgiving break.

4 months later...(check the commit history!)...progress is being made!
I have added the saved whitelist management commands (although I named them differently for assorted reasons) and completely rewritten the command handling system.
I will publish version 0.3 on bukkitdev tomorrow morning, after I touch up a few things in the code and maybe the wiki.

Actually I had been working on the saving thing but, I have been really busy since like last December pretty much, with school and other projects, but I will definitely add all of those things as soon as I get the chance. That should be soon considering its summer and my vacations are over. Thanks for the suggestions.

-Arjun

On Jul 8, 2013, at 4:51 PM, Electroid [email protected] wrote:

Add all players that ever joined to the whitelist

This would allow all players that ever joined the server to be on the whitelist. A use case would be if the server i being spam attacked; or you wanted to host an event for your server regulars. It could draw the information from the player.dat files.

/freeze r[epository]

Disable the whitelist

This would allow you to disable the whitelist easily.

/freeze d[isable]

Add a player to the whitelist

Yes, I'm aware you can do this in vanilla. However it would be nice to have it implemented into the plugin.

/freeze a[dd] {player_name}

Multiple "pre-saved" Whitelists

This would allow you to have multiple "pre-saved" whitelists for different events or occasions. It would basically save the current whitelist like a schematic on worldedit.

/freeze s[ave] {whitelist_name}

To load up a whitelist, you would run the command.

/freeze l[oad] {whitelist_name}

To view a list of saved whitelists.

/freeze v[iew]

To delete a saved whitelist.

/freeze r[emove] {whitelist_name}

Please consider these features as many people I have spoken to believe that these features would make your plugin shine even more. Thanks for your time, and thanks for coding this in the first place.

—
Reply to this email directly or view it on GitHub.