-
Notifications
You must be signed in to change notification settings - Fork 737
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
ACE_Explosives_fnc_scriptedExplosive #3621
Comments
The function is meant to be executed in unscheduled environment. Try replacing: |
Works great, thank you for the prompt response. would ask for this to be added and documented in the wiki as it's not immediately clear that it wont work in a scheduled environment. |
@C0RAX, scheduled environment is plain unreliable because, depending on the load your mission is having, the executed code may be interrupted at any moment. That's why ACE runs 95% of it's code in non-scheduled environment. Best practice would be to always call ACE API on non-sched (and the same for ACRE, TFAR, etc). You are right we should document that. |
@esteldunedain I think @C0RAX is referring to this wiki page: Yeah, it should be documented there or a better example should be used there. |
Reopening for #3633 |
make FUNC(scriptedExplosive) work in scheduled env, ref #3621
fixed in #3633 |
Arma 3 Version:
x.xx
(stable / rc / dev)CBA Version:
2.x.x
(stable / dev + commit hash)ACE3 Version:
3.x.x
(stable / dev + commit hash)Mods:
Description:
full script code:
"_ied = _this select 0;
"
Steps to reproduce:
Where did the issue occur?
Placed Modules:
RPT log file:
The text was updated successfully, but these errors were encountered: