Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix monster load with forceLoad #4424

Merged
merged 1 commit into from
Apr 24, 2023
Merged

Conversation

MillhioreBT
Copy link
Contributor

Pull Request Prelude

  • I have followed [proper The Forgotten Server code styling][code].
  • I have read and understood the [contribution guidelines][cont] before making this PR.
  • I am aware that this PR may be closed if the above-mentioned criteria are not fulfilled.

Changes Proposed

This change adds a reset of the monster info, in case the forceLoad = true. Otherwise, some containers will at best maintain duplications, such as loots and voices.

Before this option did not exist in configManager, so this was not necessary info = {};, it is assumed that this line was the first time that a monster was created on the map.

Thanks @joseluis2g for repoting this problem.

Issues addressed: Nothing!

@EPuncker EPuncker merged commit 7056722 into otland:master Apr 24, 2023
@MillhioreBT MillhioreBT deleted the fix_monsters branch May 14, 2023 01:26
EPuncker pushed a commit to EPuncker/forgottenserver that referenced this pull request May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants