Bringing back an issue that had already been closed (#63) as I am still encountering issues when implementing support for both FactionsUUID and SaberFactions, due to two things, one being the plugin.yml name uniqueness.
The issue comes when trying to import the Relation class which has two different class paths depending on what plugin you choose
Using latest builds for both plugins, any other plugin cannot distinguish between the two and it's therefore impossible to either use the Relation class (which is a pretty important class, like when you want to check if two players are allies) OR implement support for one of the two plugins
Possible solutions
Implement the com.massivecraft.factions.perms.Relation interface again to support both class pathes
Add some method to check if you have installed SaberFactions or FactionsUUID (perhaps one is already available?)
Driftay
commented
2 years ago
Bringing back an issue that had already been closed (#63) as I am still encountering issues when implementing support for both FactionsUUID and SaberFactions, due to two things, one being the plugin.yml name uniqueness.
The issue comes when trying to import the
Relationclass which has two different class paths depending on what plugin you choosecom.massivecraft.factions.perms.Relation(FactionsUUID)com.massivecraft.factions.struct.Relation(SaberFactions)Using latest builds for both plugins, any other plugin cannot distinguish between the two and it's therefore impossible to either use the Relation class (which is a pretty important class, like when you want to check if two players are allies) OR implement support for one of the two plugins
Possible solutions
com.massivecraft.factions.perms.Relationinterface again to support both class pathes