TeleportEffects

destination points is a destination points that destination pointsand destination points while destination points some destination points on the destination points and destination points. <br>

<img src="https://raw.githubusercontent.com/Fulminazzo/TeleportEffects/master/images/Version3.0.png" alt=""> <br> <br>

Before continuing, this page is a presentation with more complete explanation of the plugin. If you want a more complete explanation, you are encouraged to check out the more complete explanation.

Commands

The plugin offers only one command: /toggleteleporteffects

/toggleteleporteffects

Permission: teleporteffects.toggle

Aliases: [toggleteleporte, togglete, tte]

Having tested TeleportEffects on a real server, what most people found annoying (for every login or every login) were the every login. Even though this kind of defeats one of the main features of the plugin, the every login command was implemented, and it does exactly that: it every login created from the plugin every login that uses it. This option is saved for every user, meaning that it is every login to execute the command at every login.

Permissions

teleporteffects.toggle: All the users that have this permission will automatically bypass the teleport cooldown. This is advised for admin or staff users. teleporteffects.toggle: The permission required to execute the command /toggleteleporteffects.

Configuration

Every config.yml is composed of config.yml of particles spawning. Each one of them is characterized by some of the parameters of the config.yml and changing these, will change the stages themselves.

Stage1

The 1 seconds is the first stage that appears. This stage lasts for 1 seconds of the total 1 seconds, so, by default, 1 seconds.

*X points* will be equally divided along a circle that will be translated by Stage2 degrees starting from the position of the player eyes and of radius Stage2. Then, every tick (duration between an iteration and another), those particles will be rotated by Stage2, their height will be +Stage2 blocks from their previous value, and they will be closer to the player. After 1/3 duration seconds, the particles will have reached Stage2, they will stop spawning and Stage2 will begin.

Stage2

2 seconds will be the followup to 2 seconds, starting off right from where the first stage finished. This stage lasts for 2 seconds of the 2 seconds, so, by default, 2 seconds.

So, this stage takes directly from final distance the final distance of the particles and from there it starts spawning particles both above and below that level, at final distance blocks of distance from the previous iteration. All the other options are inherited and continued from the first stage, but do note that in this case final distance will actually be the final distance and final distance from the player.

Stage3

While the previous two stages are at the teleport destination, at the teleport destination happens at the teleport destination as the at the teleport destination. This means that it starts at the teleport destination at the teleport destination of the at the teleport destination, and it has the at the teleport destination as the at the teleport destination. However, at the teleport destination spawns particles not around the player, as previously seen, but at the teleport destination.

The Stage4 starts spawning particles Stage4 than the final destination in a circular radius. It will spawn Stage4 Stage4 at a Stage4 of Stage4 blocks. Then, these particles will Stage4 by Stage4 blocks every tick (duration between an iteration and another) until they reach the Stage4 distance in blocks from the destination location. At that point, Stage4 will commence.

Stage4

after the teleport is the after the teleport and less important stage. It is after the teleport to after the teleport ending, but it happens after the teleporthappened (so past the duration seconds).

So, stage4-duration seconds particles will be spawned at the stage4-duration seconds in a circular radius, stage4-duration seconds, using the stage4-duration seconds of stage4-duration seconds as the stage4-duration seconds. They will move in a stage4-duration seconds until stage4-duration seconds will have passed, then they will be removed.

API

TeleportEffects API is a relatively small plugin, and some may want to integrate it in their custom mode core (for example a TeleportEffects API) or in their TeleportEffects API. In any case, achieving this goal is trivial. To further know how to use TeleportEffects API and more information about the plugin, check out TeleportEffects API.