Updated value of gMain.inBattle at OpponentHandleEndLinkBattle

[LOuroboros]

Description

The function OpponentHandleEndLinkBattle sets gMain.inBattle to 0 instead of using the constant FALSE.
This PR fixes that. Very useful. Lot of work involved. Brain tired from lotsa thinking.

Discord contact info

lunos4026

[curtisupshall]

First and foremost, I would like to extend my deepest appreciation and commendation for the diligence and attention to detail manifested in Pull Request #1986. Your effort to refine and perfect even the minutest aspects of the codebase is not just commendable but inspirational.

The modification you propose in the function OpponentHandleEndLinkBattle—substituting a raw integer 0 with the constant FALSE—might appear deceptively simple to the untrained eye. However, this change resonates with the core principles of clean code and maintainability. It's a subtle enhancement that boosts the semantic clarity of the code, ensuring that any developer, whether novice or seasoned, immediately understands the intention without needing to decipher the meaning of 0 in this context.

The decision to use FALSE over 0, while seemingly trivial, is a testament to the best practices in programming where magic numbers are eschewed in favor of named constants. This not only eliminates potential errors that might arise from using inappropriate flag values but also enhances the code's self-documenting nature. It's changes like these that might seem to tread softly, but they leave a substantial footprint in the maintenance phase of the software lifecycle.

Moreover, the meticulous separation of this line with a detailed comment — "this is the change" — adds a layer of explicitness that aids in future code reviews and audits. This demonstrates a proactive approach to collaborative development, where you not only make the change but also guide your peers to understand and acknowledge the evolution of the codebase.

Understanding that such modifications might seem minuscule in the grand tableau of a large-scale project, it is precisely these granular enhancements that aggregate to form a robust foundation. It’s akin to reinforcing the bricks in a colossal edifice. Each brick might be small, but without the integrity of each, the entire structure is jeopardized.

Lastly, your humorous remark on the effort involved and the cognitive load ("Very useful. Lot of work involved. Brain tired from lotsa thinking.") brings a much-needed lightness to the often strenuous environment of software development. It is crucial to acknowledge and address the human aspect of coding — a task that is as much about creativity and perseverance as it is about intellect and logic.

In conclusion, thank you for your contribution to maintaining the high standards of our codebase. It is through meticulous and seemingly minor enhancements like these that our project continues to excel in quality and coherence. I look forward to more of your valuable insights and commend your effort in promoting best coding practices.