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

Random spawn #2

Open
MrDragonorg opened this issue Jun 16, 2020 · 3 comments
Open

Random spawn #2

MrDragonorg opened this issue Jun 16, 2020 · 3 comments

Comments

@MrDragonorg
Copy link

MrDragonorg commented Jun 16, 2020

Add a new option to the logic_gamerules, which allows zombies to spawn randomly on info_player_zombie spawn.

Now it is very necessary for large maps, since with the current system, zombies spawn only on that spawn that is closest to the players. If zombies spawn everywhere, then on large maps the action will take place on the all entire map, and not just in one of its places, while in others there will be no activity.

As an example, I can cite the zs_xanthys_b2, which uses only one spawn outside the map with the teleport, which randomly determines where the zombies will appear, but because this system is very complicated, it doesn't allow you to make many spawns.
This feature would make life easier for mappers who make big maps.

This will be useful for all "tunnel" maps, for example, zs_prison_b2. Zombies always spawn at only one point closest to people, which creates a terrible spawn camp and super farm for humans, which leads to a boring round

@Caskoo
Copy link

Caskoo commented Jun 17, 2020

I agree with this proposal

@MagicSwap
Copy link
Collaborator

I suppose it could be worth a try, my only concern is that it may spread the zombies out so much, they'll end up having to travel a mile before seeing humans.

@MagicSwap
Copy link
Collaborator

Thinking about it a bit more, would probably be better as a separate spawn entity/key value to prevent logic_gamerules issues.

Also would probably need a guinea pig map that proves it's good before it becomes a public FGD entity, since if it turns out it isn't useful, reverting it will potentially cause obsolete issues...which I think already happened in the past a few times.

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

No branches or pull requests

3 participants