13.02.2016, 16:28
@dusk: When you use the .set() method you actually store it in the Player's class instance. It will automatically be removed when it is not needed anymore.
I pushed an update that allows you to change the location even after the Checkpoint has been create / shown:
http://ci.gtaun.net/job/shoebill-api/213/ and http://ci.gtaun.net/job/shoebill-api/214/
If you don't store the Checkpoint in a variable you can call the player.getCheckpoint() method and you will get the current checkpoint. On this checkpoint object you can now call the setLocation() method to change it's location. The checkpoint will be automatically recreated at it's new location. I also added an convenient constructor if you want to use the CheckpointEnterEvent instead of the Consumers. https://github.com/Shoebill/shoebill...17d9a3d6265R61
I pushed an update that allows you to change the location even after the Checkpoint has been create / shown:
http://ci.gtaun.net/job/shoebill-api/213/ and http://ci.gtaun.net/job/shoebill-api/214/
If you don't store the Checkpoint in a variable you can call the player.getCheckpoint() method and you will get the current checkpoint. On this checkpoint object you can now call the setLocation() method to change it's location. The checkpoint will be automatically recreated at it's new location. I also added an convenient constructor if you want to use the CheckpointEnterEvent instead of the Consumers. https://github.com/Shoebill/shoebill...17d9a3d6265R61

