WatWhich API from the DragonAPI? As I really want to get Galacticraft working with monster.
WatWhich API from the DragonAPI? As I really want to get Galacticraft working with monster.
Which API from the DragonAPI? As I really want to get Galacticraft working with monster.
EDIT: the file located inside /mods/DragonAPI 1.6 v18b.zip Once this archive is opened, go under the folder micdoodle8/mods/Galacticraft/API/recipe and once under this folder inside the .zip file, locate and delete the "CompressorRecipes.class" file. Do this for both clients and server if multi-player.
Isent it better to make mitch fix these bugs rather than deleting mods?
Try using backupsBut very disheartning when a new update comes out that re-breaks your world after all the fixes and work arounds that were found and realizing that you may be stuck on the same version for a while unless the new bugged version can be fixed. @.@ it's really becoming a pain in the ass to have to keep regenning the worlds when it's one mod that corrupts and breaks other mods.
Try using backups
Backups of worlds before an broken mod than remove the mod then use the backup! easy as cheeseBackups of what? What good are backups when the world must be regenerated due to a faulty implimentation or a new update that requires the moon and thus eventually the whole of the map to be reset. Backups would have the same corruption from the first generation of the world. Please elaborate.
Backups of worlds before an broken mod than remove the mod then use the backup! easy as cheese
Both of the "bugs" discussed in this thread (thank you, Jocan) are issues in other mods, not in Galacticraft. More accurately, they are issues which ought to have been fixed by the modpack makers.TheUnknownPlayer said:Isn't it better to make mitch fix these bugs rather than deleting mods?
But here is where others can collaborate. We aren’t looking to complain to Micdoodle8, we are in fact looking to try to find quick and easy fixes in order to resume a game we all have come to know and love without having to "regenerate" our worlds due to mods not liking each other.Both of the "bugs" discussed in this thread (thank you, Jocan) are issues in other mods, not in Galacticraft. More accurately, they are issues which ought to have been fixed by the modpack makers.
If DragonAPI includes an old version of Galacticraft API code, that is nothing micdoodle8 has control over. DragonAPI loads before Galacticraft loads because Forge takes them from the /mods folder in alphabetical order. If DragonAPI includes the wrong Galacticraft API code, then Forge will not re-load the correct Galacticraft API code when it reaches Galacticraft-1.6.4.jar (or whatever). Result: compressors break.
Complain fiercely, but don't do it here: go complain to DragonAPI, or to the people who make Forge - if Forge was smart, it would be able to recognise API code which belongs to another mod, and would load that mod's own proper version of the API code out of preference.
Also to keep this type of issue to a minimum, a properly made mod should only include classes from other mods' APIs which it is actually using - which is probably not too many. That is why, anyone with DragonAPI in their mods folder can in fact fix the issue by editing the DragonAPI.jar to remove the parts of the Galacticraft API which it never needed to have in there. I think when something like that is in a modpack, the modpack makers ought to do this.
The same for CofH config files which Jocan mentioned, setting up configs for proper inter-mod compatibility is a part of what modpack makers should do.
So isent it better for the other mod authors to fix this?Both of the "bugs" discussed in this thread (thank you, Jocan) are issues in other mods, not in Galacticraft. More accurately, they are issues which ought to have been fixed by the modpack makers.
If DragonAPI includes an old version of Galacticraft API code, that is nothing micdoodle8 has control over. DragonAPI loads before Galacticraft loads because Forge takes them from the /mods folder in alphabetical order. If DragonAPI includes the wrong Galacticraft API code, then Forge will not re-load the correct Galacticraft API code when it reaches Galacticraft-1.6.4.jar (or whatever). Result: compressors break.
Complain fiercely, but don't do it here: go complain to DragonAPI, or to the people who make Forge - if Forge was smart, it would be able to recognise API code which belongs to another mod, and would load that mod's own proper version of the API code out of preference.
Also to keep this type of issue to a minimum, a properly made mod should only include classes from other mods' APIs which it is actually using - which is probably not too many. That is why, anyone with DragonAPI in their mods folder can in fact fix the issue by editing the DragonAPI.jar to remove the parts of the Galacticraft API which it never needed to have in there. I think when something like that is in a modpack, the modpack makers ought to do this.
The same for CofH config files which Jocan mentioned, setting up configs for proper inter-mod compatibility is a part of what modpack makers should do.
So isent it better for the other mod authors to fix this?
My bad, I didn't know FTB did not contain Galacticraft. So basically players who want to combine FTB and Galacticraft are going to have to "be your own modpack maker" here.
No noob hating on my part, just saying don't ask the impossible. The DragonAPI problem literally cannot be corrected by micdoodle8 or the Galacticraft team. Either DragonAPI must fix it and update, or modpack makers can do it (if DragonAPI and Galacticraft are in the same modpack) or it is something each player must do for himself with the help in this thread.