Author Topic: Max schedule quota?  (Read 1788 times)

Whenever I try to start my event build, I get "Shedule Quota Hit." even though my max it set to 9000000. Is there some limit that I don't know about?

OMG HAI WARREN

/fanboy

Have you checked ALL of the limits? There might be one set too low that you haven't checked.

(Or.. just raise the limit some more?)

I think my computer would explode before I hit 9 million.

How did you change it? You'll have to restart your server if you used the console.


If we come to a conclusion it will also help me :D


It seems to work for me when I do it.

Just go into the console, do the pref, make sure it's right, do not restart, et viola?

The problem isn't my limit, It's that I think there's a max limit.

There's two limit options. One for god knows what, and one for players.

I believe there is a limim for the "fireRelay" event, but I'm not sure.

Ok, this is irritating me. I keep getting Max Schedule Quota hit, and there aren't that many things happening. If this can't be resolved, then I can't finish my build that I worked on for a week.

Did you set the right one?  There's a max schedual for lan and for internet.  You may have set the internet settings.

As PJ said, make sure you have the proper quotas set.
Also, I've done two or three event builds that hit a schedule quota of 2,147,483,647.
It's just because the event build does too much at once.

Usually has to do with relays or hundreds of named brick.

I.e.:
onActivate -> NAMED BRICK -> setColor (Green)
onActivate -> NAMED BRICK -> setColorFX (Glow)
onActivate -> NAMED BRICK -> dissapear (3)

If you have, say, 150 of those NAMED BRICKs, then your schedule quota needs to be above 450 to operate.
3 events, 150 times, all at once = 450 schedules.

If you're using a complex relay system, there's some glitch that makes the schedules skyrocket.
It's happened to me before, and the only thing you can do is revise your system to use less.

It's best to check the quotas ARE set before re-doing your whole system incase thats the problem!

I've been as efficient as possible with my system. By the looks of it, the most events going at once on the build are 5096. I could be wrong though.