The moment when any (constant,decide,etc) combinator which has been set up to output launch condition is wired with silo, the below error happens.

Error while running event CircuitLaunchableRockets::on_tick (ID 0)
CircuitLaunchableRockets/control.lua:124: attempt to index field 'space_location' (a nil value)
stack traceback:
CircuitLaunchableRockets/control.lua:124: in function <CircuitLaunchableRockets/control.lua:27>

Fixed this!

When there are items in the silo,here comes a new one.

Error while running event CircuitLaunchableRockets::on_tick (ID 0)
CircuitLaunchableRockets/control.lua:221: attempt to index field 'value' (a nil value)
stack traceback:
CircuitLaunchableRockets/control.lua:221: in function 'get_rocket_destination'
CircuitLaunchableRockets/control.lua:142: in function <CircuitLaunchableRockets/control.lua:27>

And the "Zzz" icon only shows 【one time】 when suitably numbered platform isn't found.
It should show again to remind me I was wrong but it don't.

Then the silo randomly choose a platform to launch them. :(

Fixed that one too!

I'm not sure what you mean by "only shows one time." Are you sure your signal count is always greater than 1? If it gets a signal of 1 it will auto-launch.

EDIT: I think I figured it out. I had to make another quick fix. Please make sure you've got version 1.0.4.

Great mod and thanks for your fix.

However, there's still a little issue.
When signal count number is < 0 still activate the rocket, works like number = 1 does.

I think minus number shouldn't be the launch condition.

I added an option to version 1.0.5 called "Launch on negative." If the box is checked, the rocket will launch on a negative signal count. Otherwise it will not.

I still think negative number should be totally disabled since they all work at same condition like =1.
Otherwise, are you going to give negative number more feature in future update?

It's kind of you to add a option for it but I just can't help to wonder why.

Every change breaks someone's workflow! It wasn't really a problem to keep the old behavior as an option so I did that.