Game Balance Issue: Satellite Imbalance

Dear Author,

When my friends and I were playing HBM Nuclear Tech, we noticed a significant issue regarding satellite balance in survival mode. Specifically, there's no effective countermeasure for satellites, which creates a serious imbalance.

For instance, while we were building our base, my friend had already launched a laser death satellite. This left us completely powerless, as we had no way to use technology to destroy or counteract the satellite.

I even considered modifying the recipes to create a more balanced experience for our server’s players, allowing us to at least threaten each other with nuclear weapons and establish some level of balance. Unfortunately, recipe modification seems to have some issues—perhaps due to server differences or other technical problems—and the recipes sometimes behave strangely.

So today, I came up with two potential solutions:

1. Enhance Recipe Modification

• Replace the current HBM recipe modification system with a more robust and error-proof method.
• This change would ensure that recipe updates won’t break when HBM is updated and allow players to customize interesting recipes freely.
• You could consider implementing something like CraftTweaker, which uses functions such as:
  recipes.removeShaped
  recipes.addShaped
• This could work alongside the current JSON file system for organizing machine recipes.

2. Add Equipment to Destroy Satellites

• Currently, once a satellite is launched into space, there’s no way to counter it.
• We’re left at the mercy of whoever controls the satellite, digging diamonds or resources to secure our survival and protect our territory in Minecraft.
• Could the great Bob create a balance system for satellites?
  After all, missiles already have anti-missile systems, right? 😂

Thank you for considering this feedback!

Recipes persist when updating NTM, not sure what you're talking about there.
The SerializableRecipe model that's currently employed, when used right, works fine and shouldn't have any of these issues.
As for the satellite situation, Bob gets to make the decision there.

Recipes persist when updating NTM, not sure what you're talking about there. The SerializableRecipe model that's currently employed, when used right, works fine and shouldn't have any of these issues. As for the satellite situation, Bob gets to make the decision there.

If I modify a recipe and the author updates the files, the updated files might change the recipe that I modified. How does SerializedRecipe handle changes in this case?