-
Notifications
You must be signed in to change notification settings - Fork 401
-
Notifications
You must be signed in to change notification settings - Fork 401
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
Monsters spawned in swarms have same loot #13768
Comments
Regalis11
changed the title
[Unstable] monsters spawned in swarms have same loot
Monsters spawned in swarms have same loot
Apr 12, 2024
Note that this happens consistently if the level's seed is 32 characters long or longer. Easiest to repro in a campaign level that takes place between two locations, because those have the longest seeds. |
Pushed a quick and simple fix straight to spring-update (#13768), more robust fix here: https://github.com/FakeFishGames/Barotrauma-development/pull/5175 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discussed in #13761
Originally posted by SomeRandomNoobKekeke April 10, 2024
Disclaimers
What happened?
I killed a swarm of ~10 husked crawlers and they all got husk stingers, and i think probability to have stinger is 1/11, very suspicious
And then i checked different monsters, and yes all monsters in some swarm always share same loot
If you spawn them with spawncharacter inventory is randomised as intended
Reproduction steps
quickstart at 100 difficulty to make swarms bigger
find some monsters, kill them and check their loot
I think you have to encounter them naturally
I tried to spawn them with triggerevent but they seem to spawn with empty pockets
Bug prevalence
Happens every time I play
Single player or multiplayer?
Single player
-
No response
Version
v1.4.0.0 (unstable)
-
No response
Which operating system did you encounter this bug on?
Windows
Relevant error messages and crash reports
No response
The text was updated successfully, but these errors were encountered: