There is a continuous spam of error coming from \scripts\server\patrols\manage_one_patrol.sqf..., line 62.
The variable "_grp", that isn't defined as private, seems to be nil after sleep.
for the moment i chose to add guarding and limiting the scope of the variable, but needs review over the sqf working
There is a continuous spam of error coming from \scripts\server\patrols\manage_one_patrol.sqf..., line 62.
The variable "_grp", that isn't defined as private, seems to be nil after sleep.
for the moment i chose to add guarding and limiting the scope of the variable, but needs review over the sqf working
The log uses the KP logging functionality instead of SQF spam, and assicure that the interruption is handled cleanly; also adding "private" to local variable to protect the scope of the variable and reducing error propagation area of the "new" (arma 3 2024/2025) parallel multi task systems
The log uses the KP logging functionality instead of SQF spam, and assicure that the interruption is handled cleanly; also adding "private" to local variable to protect the scope of the variable and reducing error propagation area of the "new" (arma 3 2024/2025) parallel multi task systems
Fastwind
marked the pull request as ready for review 2026-07-02 14:41:16 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
There is a continuous spam of error coming from \scripts\server\patrols\manage_one_patrol.sqf..., line 62.
The variable "_grp", that isn't defined as private, seems to be nil after sleep.
for the moment i chose to add guarding and limiting the scope of the variable, but needs review over the sqf working
So this is going to change the spam of errors of missing variable into a spam of "patrol group doesn't contain soldiers"?
The log uses the KP logging functionality instead of SQF spam, and assicure that the interruption is handled cleanly; also adding "private" to local variable to protect the scope of the variable and reducing error propagation area of the "new" (arma 3 2024/2025) parallel multi task systems
As in reference to the private messages, merging for production testing, at worst rolling back