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

[craterules] CrateMaximum is not respected when map spawns crates #357

Open
ismail-doitbig opened this issue Apr 12, 2024 · 3 comments
Open

Comments

@ismail-doitbig
Copy link

ismail-doitbig commented Apr 12, 2024

When i add action to the map to spawn crates the pool becomes bigger by each spawn i do
e.g. max = 10
after spawning 1, there are 11, which is higher than 10

And it keeps being this way it never reduces anymore

@CnCRAZER
Copy link
Contributor

Trigger events do not check for maximum or minimum crate values before firing.

@ismail-doitbig
Copy link
Author

I mean afterwards the pool stays big, it doesn't reduce, every new spawn increases the pool permanently

@CnCRAZER
Copy link
Contributor

CnCRAZER commented Apr 13, 2024

I've noticed this as well. I've created a couple crate / luck based maps that have an excess of 200+ crates and had 4 triggers spawning crates for each players in a repeating trigger with an elapsed time at certain waypoints.

But in my case, I noticed when the triggers forced the total crate values to exceed 255(noted in the rulesmd.ini file to be the MAXIMUM amount) that the triggers would actually stop firing as if the tag was deleted. Even grabbing 100+ crates wouldn't enable the triggers to fire again. Only solution was to make sure you were constantly picking up crates to avoid ever reaching the 255 limit.

Just curious though, how is this an issue for you? You can just set the maximum crates allowed to 0 in the .map file, and only have the crates on the map be spawned via triggers

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

2 participants