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

All units invincible, ACE Check PBOs + Medical Prevent instant death or Revive #2913

Closed
captainblaffer opened this issue Dec 2, 2015 · 7 comments
Assignees
Labels
Milestone

Comments

@captainblaffer
Copy link
Contributor

ACE3 Version: 3.4.0

Mods:

@CBA_A3
@ace

Placed ACE3 Modules:
ACE Check PBOs
ACE Medical Settings
ACE Medical Revive

Description:
If a mission features the ACE Check PBOs module with empty whitelist + either
-Medical Settings Prevent instant death: ON
-Revive module

all units are invincible.

Steps to reproduce:
1.Create new mission in editor.
2.Place NATO and CSAT dude.
3.Place module; ACE check pbo
4.Set module setting: whitelist, delete the brackets: [] , so you're left with an empty field.
5.Place module: ACE Medical settings.
6.set module setting: Prevent instant death: ON

7.Start mission. Attempt to kill the enemy.

Where did the issue occur?
SP

RPT log file:
http://pastebin.com/rhE1VncE

@bux
Copy link
Member

bux commented Dec 2, 2015

RPT or it didn't happen

@captainblaffer captainblaffer changed the title All units invincible, ACE Medical Prevent instant death & ACE Revive All units invincible, ACE Check PBOs + Medical Prevent instant death or Revive Dec 3, 2015
@captainblaffer
Copy link
Contributor Author

Sorry, updated the bug with RPT and more info. Turned out there was more going on than I initially thought

@PabstMirror PabstMirror added this to the 3.4.1 milestone Dec 3, 2015
@PabstMirror
Copy link
Contributor

Quickly reproduced this issue, but the core problem isn't medical?
Try changing Check PBO module to be [] instead of empty string and it goes away, I think the crash in common_fnc_map is the problem.

@captainblaffer
Copy link
Contributor Author

Yes I suppose the issue can only occur if the mission maker makes the 'mistake' of removing []

The thing is I loaded up my mission from before the patch and it didn't have these [] in the module. Possibly the default setting got changed in a patch?

PabstMirror added a commit that referenced this issue Dec 3, 2015
Fix #2913
Use splitString instead of call compile to convert string into an array
@PabstMirror
Copy link
Contributor

So there error was in checkPbo, and that cascaded and broke the "SettingsInitialized" event, which meant settingsInitFinished was never set, so ace_medical_fnc_setUnconscious failed to run.

Really interesting chain, thanks a lot for RPT and reproduction steps.

@jonpas
Copy link
Member

jonpas commented Dec 3, 2015

That's actually pretty amazing.

@PabstMirror PabstMirror self-assigned this Dec 3, 2015
@commy2
Copy link
Contributor

commy2 commented Dec 4, 2015

Fixed in #2911

@commy2 commy2 closed this as completed Dec 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants