Ability to set mod priority

[skol101]

Is your feature request related to a problem? Please describe.
The issue is when an ACE mod (i.e. ace no medical) loads after Antistasi mod, the server can't start the mission.

Describe the solution you'd like
Ability to set mod order by moving up and down or setting priority number (from 0 to N).

Describe alternatives you've considered
Manually editing mod order list.

[defy93]

Having just spun up arma-server-manager ourselves and are using the antistasi mod & ace, are you sure this is your root problem? Mod order doesn't matter as much as it used to, I ask this question as we (not the devs themselves, my community) are running Antistasi & Ace no problem

[skol101]

I've tried manually running arma 3 server with the same order as in the manager -- and reported the issue here official-antistasi-community/A3-Antistasi#3476 (comment)

For me , it was the same situation until I've placed antistasi mod AFTER ace.

[AEhere]

I have also run into this, it affects antistasi ultimate in particular: any units placed by the mod are not declared to zeus and are stuck in place, while units spawned manually through zeus are functional.
I have tested the same mission on the server and hosted locally (same map and modset, not even a client restart) and the difference is immediately obvious.

EDIT: I tested loading the mods in order (cba, then ace, then antistasi) using the launch parameter line and that does not fix the issue, strangely.

[fugasjunior]

Just a quick note, this does not seem to be an issue with the Antistasi Ultimate mod, at least I was not able to reproduce it. By default, ACE is loaded before Antistasi Ultimate as the mods are sorted in alphabetical order by the manager. But even when I tried manually launch the server and load ACE after Antistasi Ultimate, there were no apparent problems.

However I'll try to reproduce this with the Antistasi Mod. Is this reproducible just by using ACE, CBA and Antistasi Mod, or is anything else required?

Edit: I see that ACE no medical is being used here, I'll give that a try. Off topic question out of curiosity, how is the "no medical" version working for you? I see that it was last updated in 2022.

[AEhere]

I believe the issue lies with the profiling branch of the Linux Arma server. I could reproduce the problem with just ace and antistasi ultimate on our server (Linux), but not locally (win10), so I jumped to the conclusion that the load order was at fault.

After switching the server back to the stable branch the problem went away.

EDIT: No Medical has worked ok for our group this run and last year when we last used it, if it breaks anything it is not something we have noticed.