Home
Here are some great topics to help you get started.
- Setting up development environment
- Using FPlayer/FPlayers
- Using Faction/Factions
- Listening to Events
- Creating Commands
- Existing Plugins
Developing for Factions can be a little frustrating. The internal API changes regularly between releases, and with no deprecation policy in place it's common for some methods to be removed or added without notice - causing your plugins to break instantly for some versions but work perfectly for the other. 😢
That sucks, and causes things to fall apart on your server.
(not quite like that - but similar, right?)
Factions Framework is best described as a middle man. It sits in-between your plugin and the Factions plugin you have installed.
The framework has it's own standard for creating commands, getting factions, using events, and other features required for Factions plugins. This means that you only have to create your plugin to work with Factions Framework. These are automatically routed into Factions, using the correct standard for your installed plugin.
In some cases, Factions Framework is more powerful than using the existing Factions API. We've extended on the features in events and other classes, allowing you to do more things easily.
Deprecation is another common issue, our deprecation policy is minimum 6 months notice, with an additional 4 weeks before it is removed. This means that there will be a notice when a method is being changed or removed and since it's still available during this time - your plugins won't break. Allowing developers a minimum of 7 months to update their plugins if something changes. 😄
Factions Framework supports Factions UUID and all versions of Factions 2.
