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

Merge ACEX #8415

Merged
merged 15 commits into from
Oct 14, 2021
Merged

Merge ACEX #8415

merged 15 commits into from
Oct 14, 2021

Conversation

jonpas
Copy link
Member

@jonpas jonpas commented Sep 1, 2021

When merged this pull request will:

Idea of ACEX was good, but it still today isn't large enough to really warrant it being its own mod, it always felt like it added more work (maintenance, updating dependencies, doing another release etc.) than it was worth it.

Instead, after some internal discussion, this PR is opened as a proof of concept to merge ACEX and ACE3. All ACEX components come with settings to disable them, and any future components that would be deemed "out of scope for ACE3" and would instead go into ACEX, will be able to go into ACE3 either in this similar way (disabled by default) or optional, which we distribute separately on Steam and in launchable @mod folders anyways.

ACEX doesn't have the benefits it used to have, especially with CBA Settings, the way we now handle optionals in ACE3 and reduced workforce as Arma 3 is less and less interesting for the lack of a better word.


The idea to merge ACEX was approved by the ACE-Team, but this PR now needs some love from the community, testing it on old missions, verifying backwards compatibility is there and generally reviewing it.


Left to do after initial approvals/tests:

jonpas and others added 5 commits August 13, 2021 17:17
Backwards compatibility with XGVAR set of macros used on all settings and config entries
Public API functions not taken into account yet, many other things probably still missed
@jonpas
Copy link
Member Author

jonpas commented Sep 1, 2021

One internal worry that was brought up by @BaerMitUmlaut is a potential problem with the X family of macros. Other components referencing those variables could be easily mistaken.

I don't think it's a big issue, PRs should be tested anyways. But as an alternative idea, we could also change do ace_var = acex_var; on setting change (each time setting changes). That would just require the settings to retain ACEX-prefix for backwards compatibility, but all use of it could use the standard set of macros.

As for config entries, we could also just ignore backwards compatibility for them, I am not sure how many people used those in their own mods, assuming not many.

@jonpas
Copy link
Member Author

jonpas commented Oct 10, 2021

Note: Remove "Maintainers" part from README.mds as well.

@jonpas
Copy link
Member Author

jonpas commented Oct 13, 2021

Test on a missions saved with ACE3 and ACEX stable (right) and loaded on this PR (left).
image

@jonpas jonpas added this to the 3.14.0 milestone Oct 13, 2021
@jonpas
Copy link
Member Author

jonpas commented Oct 13, 2021

Merged ready open PRs from ACEX, acemod/ACEX#258 as I was not sure that was approved, it currently lives on https://github.com/acemod/ACE3/tree/acex-merge-pr-258.

jonpas added a commit to Theseus-Aegis/ACE3 that referenced this pull request Oct 13, 2021
Copy link
Member

@mharis001 mharis001 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No obvious issues when looking through the code. Just a minor discussion point in the suggestions.

addons/field_rations/XEH_postInit.sqf Outdated Show resolved Hide resolved
@PabstMirror PabstMirror mentioned this pull request Oct 14, 2021
* acex - handle old funcs

* replace thirst/hunger setvars to acex naming

fix macro

Revert "fix macro"

This reverts commit d807e5e.

Revert "replace thirst/hunger setvars to acex naming"

This reverts commit bafc607.

x
@jonpas jonpas added kind/added feature kind/feature Release Notes: **ADDED:** and removed kind/added feature labels Oct 14, 2021
@PabstMirror PabstMirror merged commit 6ca9d59 into master Oct 14, 2021
@PabstMirror PabstMirror deleted the acex-merge branch October 14, 2021 15:46
@Seb105
Copy link
Contributor

Seb105 commented Oct 14, 2021

fyi acemod/ACEX#258 was never properly reviewed to my knowledge.

@jonpas
Copy link
Member Author

jonpas commented Oct 14, 2021

fyi acemod/ACEX#258 was never properly reviewed to my knowledge.

And it was not merged either as I said above.

AndreasBrostrom pushed a commit to AndreasBrostrom/ACE3 that referenced this pull request Dec 3, 2021
* Merge ACEX - first attempt
Backwards compatibility with XGVAR set of macros used on all settings and config entries
Public API functions not taken into account yet, many other things probably still missed

* Resolve issues

* Switch to addSetting, backward compatible CfgPatches, missed XGVAR.

* Remove unnecessary backwards compat

* Convert ACEX Categorised settings to initSettings / Fix Intel items magazine

* Apply suggestions from code review

Co-authored-by: PabstMirror <pabstmirror@gmail.com>

* Remove maintainers from merged ACEX components

* Cleanup unused module and faction classes

* Sitting - Add more object configs by @Dystopian
acemod/ACEX#255

* Translations - Add Japanese by @classicarma
acemod/ACEX#259

* Kill Tracker - Add killtracker.inc public include file by @Freddo3000"
acemod/ACEX#251

* Add ACEX authors and sort authors file

* acex - final tweaks (acemod#8513)

* acex - handle old funcs

* replace thirst/hunger setvars to acex naming

fix macro

Revert "fix macro"

This reverts commit d807e5e.

Revert "replace thirst/hunger setvars to acex naming"

This reverts commit bafc607.

x

Co-authored-by: TyroneMF <TyroneMF@hotmail.com>
Co-authored-by: PabstMirror <pabstmirror@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/large kind/feature Release Notes: **ADDED:**
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants