Freeze API

A Bukkit API that helps avoid the conflicting anti-movement protocols of different plugins.

This is the project logo.

This is the project icon.

Description

Have you ever had one of the folowing problems when trying to make your minigame plugin compatible with others:

Players were still somehow "frozen" from the last game from another plugin, and you don't know how to get that plugin to release them?
Players could still move when you "froze" them for a starting line-up?

If so, you need to use this API for your plugin. It is designed to help avoid these conflicts. It adds three events:

PlayerFrozenEvent: Thrown when a player is, for any reason, frozen.
PlayerUnfrozenEvent: Thrown when a player is, for any reason, unfrozen.
PlayerMoveWhileFrozen: Thrown when a player attempts to move while frozen, as requested by Geoneo97.

It has one big array to store all frozen players in. This helps avoid plugin "Freezing" conflicts. To add a player to the array, simply

Add the API jar to your build path, much like you had to for the Bukkit API;
Import Freeze.Freeze;
Add the following to your code (where p is the player you are trying to freeze) :

Freeze.freezePlayer(p);

It's that simple! To unfreeze a player, use

Freeze.unfreezePlayer(p);

You can now check to see if a player is frozen! Simply call

PlayerIsFrozen.isPlayerFrozen(Player p);

If your plugin uses Freeze API, PM me and I will add you to the list. Plugins that use Freeze API:

Source: Feel free to submit pull requests and such.

Donations:

I do not accept donations at this time. Please support me by reporting problems and other suggestions to the ticket tracker.

Milestones: