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

Limit golem spawns to gloomy caves and tomb of xinroch #418

Merged
merged 1 commit into from
Jun 19, 2018

Conversation

ryfactor
Copy link
Member

Fixes #417

@AquariusPower
Copy link
Contributor

AquariusPower commented Jun 19, 2018

this means the surprise will not happen? the bamboo gollem protecting the hidden chest on UT 1 or 2

also, despite I think it is good for new players, I got used to run away from them as they are quite bad to track us (not always tho). But I think in general it will be better w/o them so early.

@ryfactor
Copy link
Member Author

The surprise will still be there, only the monster spawner will be prevented from spawning golems in UT. Same with the surprises in the spider cave, they will still be there.

@jakwings
Copy link
Member

Too strict, maybe? Earlier, before that surprise was introduced, I could see dangerous monsters if I stayed in the UT too long. Was this feature also removed in a previous commit?

@red-kangaroo
Copy link
Contributor

I like that. Golems should not spawn that early.

@iology You will still see dangerous monsters other than golems.

@andrewtweber
Copy link
Member

Just to clarify, will they still show up in UT4 (the crystal level?)

@red-kangaroo
Copy link
Contributor

@andrewtweber The golems in UT4 and the one guarding the secret chest are pre-defined and will be generated even if we forbid golems from spawning in UT.

@andrewtweber andrewtweber merged commit 3fc9520 into Attnam:master Jun 19, 2018
@ryfactor ryfactor deleted the PreventGolemSpawnInUT branch February 26, 2020 20:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants