Suggestion: Additional Option To Use With IndividualProgression.ExcludeAccounts To Disregard Stat Changes
Introduction
The IndividualProgression module is a powerful tool for World of Warcraft servers, allowing for a more immersive experience by implementing various checks and adjustments based on the game's progression state. However, one of the options available, IndividualProgression.ExcludeAccounts, has raised concerns about its impact on playerbots. In this article, we will explore the current implementation of this option and suggest an additional parameter to address the issue.
Current Implementation
The IndividualProgression.ExcludeAccounts option removes the account from many checks that the module implements, including stat changes such as HP, damage, and healing. This is great for playerbots, as it allows them to operate without being affected by the progression state. However, this raises concerns about the balance between playerbots and players.
The Problem
If the IndividualProgression.ExcludeAccounts option disregards stat changes, playerbots will be significantly stronger than players, regardless of level and state, until the WOTLK expansion. This is because the stat changes are not applied to the playerbots, making them more powerful than players who are affected by the progression state.
Proposed Solution
To address this issue, we propose adding a parameter to the IndividualProgression.ExcludeAccounts option that limits the impact of stat changes on playerbots. This parameter would allow playerbots to disregard everything except stat changes, ensuring that they are still affected by the progression state.
Implementation
The current implementation of the IndividualProgression.ExcludeAccounts option is managed in the IndividualProgressionPlayer.cpp file, specifically in the lines 89C4-L90C83. The stats outside of health are managed through the gearAdjustment.
To implement the proposed solution, we suggest changing the way stats are managed for playerbots. For example, we could modify the code to only consider the level range when calculating HP and stats, regardless of the progression state. This would ensure that playerbots are still affected by the progression state, but only in terms of their level range.
Example Use Case
For instance, if we have a Lv 60 bot, we could "lock" it in vanilla stats, regardless of the progression state. This would ensure that the bot is still affected by the progression state, but only in terms of its level range.
Benefits
The proposed solution would have several benefits, including:
- Ensuring that playerbots are still affected by the progression state, but only in terms of their level range.
- Preventing playerbots from becoming significantly stronger than players, regardless of level and state.
- Providing a more immersive experience for players by ensuring that playerbots are still affected by the progression state.
Conclusion
In conclusion, the IndividualProgression.ExcludeAccounts option raises concerns about the balance between playerbots and players. To address this issue, we propose adding a parameter to the option that limits the impact of stat changes on playerbots. This would ensure that playerbots are still affected by the progression state, but only in terms of their level range. We believe that this solution would provide a more immersive experience for players and ensure a more balanced game environment.
Future Development
In the future, we could consider further developing the IndividualProgression module to include more features and options. For example, we could add more parameters to the IndividualProgression.ExcludeAccounts option to allow for more fine-grained control over the behavior of playerbots.
References
Acknowledgments
Q: What is the current implementation of the IndividualProgression.ExcludeAccounts option?
A: The IndividualProgression.ExcludeAccounts option removes the account from many checks that the module implements, including stat changes such as HP, damage, and healing.
Q: Why is the IndividualProgression.ExcludeAccounts option a concern for playerbots?
A: If the IndividualProgression.ExcludeAccounts option disregards stat changes, playerbots will be significantly stronger than players, regardless of level and state, until the WOTLK expansion.
Q: What is the proposed solution to address the issue with the IndividualProgression.ExcludeAccounts option?
A: We propose adding a parameter to the IndividualProgression.ExcludeAccounts option that limits the impact of stat changes on playerbots. This parameter would allow playerbots to disregard everything except stat changes, ensuring that they are still affected by the progression state.
Q: How would the proposed solution be implemented?
A: The proposed solution would involve modifying the code to only consider the level range when calculating HP and stats, regardless of the progression state. This would ensure that playerbots are still affected by the progression state, but only in terms of their level range.
Q: What are the benefits of the proposed solution?
A: The proposed solution would have several benefits, including:
- Ensuring that playerbots are still affected by the progression state, but only in terms of their level range.
- Preventing playerbots from becoming significantly stronger than players, regardless of level and state.
- Providing a more immersive experience for players by ensuring that playerbots are still affected by the progression state.
Q: How would the proposed solution affect the balance between playerbots and players?
A: The proposed solution would ensure that playerbots are still affected by the progression state, but only in terms of their level range. This would prevent playerbots from becoming significantly stronger than players, regardless of level and state.
Q: What is the current status of the proposed solution?
A: The proposed solution is currently in the discussion phase and has not been implemented yet.
Q: How can I contribute to the development of the IndividualProgression module?
A: You can contribute to the development of the IndividualProgression module by:
- Reporting bugs and issues on the GitHub repository.
- Suggesting new features and options.
- Participating in discussions on the module's forum or Discord channel.
Q: Where can I find more information about the IndividualProgression module?
A: You can find more information about the IndividualProgression module on the GitHub repository and the module's forum or Discord channel.
Q: What is the future development plan for the IndividualProgression module?
A: The future development plan for the IndividualProgression module includes:
- Adding more features and options to the module.
- Improving the performance and stability of the module. Enhancing the user interface and experience.
Q: How can I stay up-to-date with the latest developments of the IndividualProgression module?
A: You can stay up-to-date with the latest developments of the IndividualProgression module by:
- Following the module's GitHub repository.
- Participating in discussions on the module's forum or Discord channel.
- Checking the module's website for updates and news.