#no_ x events not blockable
13 messages · Page 1 of 1 (latest)
So you want to basically undo the nolock A ?
This is working as intended. Block just blocks that event from occurring, it doesn't undo existing calls of that event. So in thise case if you called nolock a AFTER the block nolock a it would not trigger
Currently though there is no opposite version of nolock nobullets etc to turn it back on again
should I add matching events like
canlock canbullets canmissile etc?
Yes that would work
ok, will do
What is the full list you want?
nolock, nomissile, nobullet
any others?
noreload ?
got it, implementing now for next build
note there is a fake build v1.431 which is just an update to the app preview for Apple but this will be in one after taht