cncnet-yr-client-package icon indicating copy to clipboard operation
cncnet-yr-client-package copied to clipboard

[craterules] CrateMaximum is not respected when map spawns crates

Open ismail-doitbig opened this issue 10 months ago • 3 comments

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

ismail-doitbig avatar Apr 12 '24 16:04 ismail-doitbig

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

CnCRAZER avatar Apr 12 '24 18:04 CnCRAZER

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

ismail-doitbig avatar Apr 12 '24 21:04 ismail-doitbig

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

CnCRAZER avatar Apr 13 '24 00:04 CnCRAZER