Skip to content
This repository has been archived by the owner on Mar 31, 2021. It is now read-only.

[BUG] MissionWhitelist #110

Open
Addi995 opened this issue Jan 23, 2021 · 3 comments
Open

[BUG] MissionWhitelist #110

Addi995 opened this issue Jan 23, 2021 · 3 comments

Comments

@Addi995
Copy link

Addi995 commented Jan 23, 2021

Describe the bug
It is not possible to declare a MissionWhitelist with the Mission selector override. Arma doesnt start because the parameter missionWhitelist exists twice.

Screenshots
Missionwhitelist 1
Missionwhitelist 2

The only war to declare a Whitelist: you must edit the ServerCfg in Faster and save. But when you change anything and press save, you need to change the ServerCfg in Faster again.

To delete this "Bug" you only need to delete the Line 810 in Models/ServerCfg.cs and then you can declare a missionWhitelist in the mission selector override.

Maybe you can add a fiel to add a missionWhitelist.

Thanks for the great tool.

@Foxlider
Copy link
Owner

The mission selector override is not designed to have mission whitelist in it.

To add mission whitelist, you must edit the output directly.
As this is not a heavily required feature, it might not be added (yet) for I have many features to add
(currently getting rid of steamCMD to deal with different mod downloading techniques)

@Addi995
Copy link
Author

Addi995 commented Jan 23, 2021

I know that a need to change the output directly. But when i save the profile in Faster again, Faster will delete my changes in the output. So i need to declare every time a new whitelist when we change any values in faster.

Maybe it is possible to delete line 810 in the Models/ServerCfg.cs to get a workaround to use the mission selector override for a mission whitelist.

I know the mission selector ovveride is not build for that, but it will be nice.

@Foxlider
Copy link
Owner

I might look into it.
The biggest issue is : FASTER regenerates the whole cfg whenever a setting in the UI is changed. It allows for realtime changed in the cfg files. So if you change a setting in the output directly and then change a setting in the UI, your changes will be overridden. There is not much I can do for that.

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

No branches or pull requests

2 participants