Skip to content
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

Unknown enum value: "PRONE" #406

Closed
mjc4wilton opened this issue Jul 14, 2024 · 3 comments · Fixed by #407
Closed

Unknown enum value: "PRONE" #406

mjc4wilton opened this issue Jul 14, 2024 · 3 comments · Fixed by #407

Comments

@mjc4wilton
Copy link
Contributor

Mods (complete and add to the following information):

  • Arma 3: 2.14 stable
  • CBA: 3.17.1
  • LAMBS_DANGER: 2.6.0

Description:

RPT and on-screen error caused by an unknown enum value

Steps to reproduce:

  • Unknown. Only received reports from others about it. Provable issue via bi wiki documentation.

Expected behavior:

Error does not occur

Where did the issue occur?

Dedicated Multiplayer

Additional context:

_unit setUnitPosWeak (["MIDDLE", "PRONE"] select (getSuppression _unit > 0.9));

BI Wiki

Log Files:
RPT error:

9:50:16 Error in expression <ll lambs_main_fnc_doAssaultSpeed;
_unit setUnitPosWeak (["MIDDLE", "PRONE"] sele>
 9:50:16   Error position: <setUnitPosWeak (["MIDDLE", "PRONE"] sele>
 9:50:16   Error Foreign error: Unknown enum value: "PRONE"
 9:50:16 File z\lambs\addons\danger\functions\fnc_brainForced.sqf..., line 55
 9:50:16 [ACRE] (sys_io) INFO: Pipe error: Read CreateFileA WinErrCode: 2

(I think the fix is replacing the enum with "DOWN" but I don't have time to read the full code context)

@jokoho48
Copy link
Collaborator

Wow, this has been in for 3 years, and nobody has noticed until now.

@nomisum
Copy link

nomisum commented Jul 23, 2024

funnily enough i encountered this the first time today as well

@dedmen
Copy link
Contributor

dedmen commented Jul 23, 2024

I did a big refactor on enum handling. Lots of places were missing validation. Like this one apparently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants