BlazeFly provides the ability to fly in survival mode at the cost of fuel. By default, Blaze Rods are used as fuel blocks and each Blaze Rod will last 60 seconds. However, both of these options are configurable meaning you could use wood and have each block last 15 seconds, or anything you would like really.
You will be given a warning when on your last block of fuel, and then again when 10 seconds remain, at this point it is advised that you make a landing.
Features
- Allow users to fly at the cost of fuel
- Use ANY block as a source of fuel
- Allow admins to fly for free with the blazefly.nofuel permission
- Prevent certain groups of users from flying by using a negative permission node of blazefly.use
- The speed of flying is adjustable (2x and 4x) via the /flyspeed command
- Prevent fall damage by leaving fly mode active even while not flying
Commands
- /fly - Enables & disables flight
- /flyspeed - Used to modify the speed of flight. Options are 1, 2 or 4, these will multiply the speed, for example, 2 will be double speed
Configuration
- fuelBlock - This is to tell BlazeFly which block you would like to use as fuel. Specify using the block ID
- fuelTime - This is to tell BlazeFly how long you would like each block of fuel to last. Specify in seconds
- allowSpeed - This sets whether or not /flyspeed can be used to adjust speed of flight
- speedFuel - This sets whether or not extra fuel should be charged for flying faster. Double speed = double fuel
Permissions
- blazefly.use - Allows the user to fly (Default: All users)
- blazefly.flyspeed - Allows the user to change their fly speed (Default: All users)
- blazefly.nofuel - Allows the user to fly without the need for fuel (Default: Ops)
TODO
- Rewrite this page!
- Add a /flyoff command and permission, which will allow an admin to disable flight for the give user
- Add a pvp option to config, if enabled, when damage is taken flight will be disabled
- Prevent any fall damage as a result of BlazeFly (including pvp disabled flight)
- Make empty message strings mean no message will be sent for the given event
Misc
Github: You can get the source for BlazeFly here
Bugs: Got a bug, request or just wanna show your support? Leave a comment and I'll reply as soon as I can!
NOTE: Please don't report bugs unless they are for the latest version of BlazeFly.
- 2 comments
- 2 comments
Facts
- Date created
- Jan 20, 2013
- Category
- Last update
- Feb 15, 2013
- Development stage
- Release
- Language
- enUS
- License
- GNU General Public License version 3 (GPLv3)
- Curse link
- BlazeFly
- Downloads
- 606
- Recent files
- R: BlazeFly v1.3.1 for CB 1.4.7-R1.0 Feb 15, 2013
- R: BlazeFly v1.2.3 for CB 1.4.7-R1.0 Feb 12, 2013
- R: BlazeFly v1.2.2 for CB 1.4.7-R1.0 Feb 05, 2013
- R: BlazeFly v1.2.1 for CB 1.4.7-R1.0 Feb 02, 2013
- R: BlazeFly v1.1.2 for CB 1.4.7-R0.1 Jan 21, 2013
Authors
-
- Manager
- Author
- Reply
- #81
bradicaljh May 24, 2013 at 04:20 UTC - 0 likesSo I can make sure I fix as many issues as possible with this next version, could anyone who has experienced something they think needs to be fixed with BlazeFly please reply to this comment with what exactly happened and if its related to another plugin what plugins I'll need to reproduce the problem.
If you're not running the latest version of BlazeFly please don't report bugs, upgrade first, and see if that fixes the problem, if not, report away!
Cheers!
If at first you don’t succeed, call it version 1.0
- Reply
- #80
bradicaljh May 07, 2013 at 08:41 UTC - 1 likeDue to a hard drive failure I lost the progress I had made on the next version of BlazeFly.
HOWEVER, thanks to the wonder that is GitHub, I can grab the code from the latest version and start working on it again! I have compiled a TODO list with the things I'm happy to add (based on your suggestions) and have cleared out the comments to tidy things up.
I'm currently studying, so can't give an ETA for the next version, but I'll try get it done soon. If anyone has any ideas that they would like to see on the TODO list, feel free to comment!
Cheers.