0ad/binaries/data/mods/mod/gui/incompatible_mods/incompatible_mods.js

/* eslint-disable prefer-const -- Mods should be able to change it */
let g_IncompatibleModsFile = "gui/incompatible_mods/incompatible_mods.txt";
/* eslint-enable prefer-const */

export function init(data)
{
	Engine.GetGUIObjectByName("mainText").caption = Engine.TranslateLines(Engine.ReadFile(g_IncompatibleModsFile));
	return new Promise(closePageCallback =>
	{
		Engine.GetGUIObjectByName("btnClose").onPress = closePageCallback;
	});
}
Make incompatible_mods.js a module Refs: #8081 2026-07-27 03:23:43 -07:00			`/* eslint-disable prefer-const -- Mods should be able to change it */`
			`let g_IncompatibleModsFile = "gui/incompatible_mods/incompatible_mods.txt";`
			`/* eslint-enable prefer-const */`
Do not allow to start pyrogenesis with incompatible mods Fixing following problems: Issue number one: Enable mod with a23 compatibility in a23b. Save configuration. Start a24. Better result: Mod will be enabled and invisible in mod selection screen producing various errors. Worse result: Game will crash and refuse to start. Issue number two: Mods can silently set loaded mods without restarting the engine, so mods can unlist themselves from compatibility detection. Solution: Enable necessary mods instead if running with gui and open mod page. Open information window on top of mod page to infom why mod page is showing up. On mod page show mods which failed in compatibility check and color the resposnible ones. Disable start button without enabled mods. Show non existed mods if they failed in compatibility check. Else just log to mainlog and close. Another fixes: Display in enabled mods really enabled mods as current logic confuses players about which mods they have enabled and is not helpful (ref #4881) Note: this will not solve issue with mods claiming being compatible with engine version while in fact being incompatible. Comments by: @vladislavbelov, @Stan, @Imarok Tested by: @wraitii Differential revision: D3592 Fixes: #6044 #4881 This was SVN commit r25410. 2021-05-09 06:53:25 -07:00
Make incompatible_mods.js a module Refs: #8081 2026-07-27 03:23:43 -07:00			`export function init(data)`
Do not allow to start pyrogenesis with incompatible mods Fixing following problems: Issue number one: Enable mod with a23 compatibility in a23b. Save configuration. Start a24. Better result: Mod will be enabled and invisible in mod selection screen producing various errors. Worse result: Game will crash and refuse to start. Issue number two: Mods can silently set loaded mods without restarting the engine, so mods can unlist themselves from compatibility detection. Solution: Enable necessary mods instead if running with gui and open mod page. Open information window on top of mod page to infom why mod page is showing up. On mod page show mods which failed in compatibility check and color the resposnible ones. Disable start button without enabled mods. Show non existed mods if they failed in compatibility check. Else just log to mainlog and close. Another fixes: Display in enabled mods really enabled mods as current logic confuses players about which mods they have enabled and is not helpful (ref #4881) Note: this will not solve issue with mods claiming being compatible with engine version while in fact being incompatible. Comments by: @vladislavbelov, @Stan, @Imarok Tested by: @wraitii Differential revision: D3592 Fixes: #6044 #4881 This was SVN commit r25410. 2021-05-09 06:53:25 -07:00			`{`
			`Engine.GetGUIObjectByName("mainText").caption = Engine.TranslateLines(Engine.ReadFile(g_IncompatibleModsFile));`
Use @stylistic/brace-style for eslint Up to now `eslint-plugin-brace-rules` was used to enforce a common brace style for JavaScript code. This plugin was however updated the last time over 9 years ago and will be incompatible with ESLint v10, as that [removes `context.getSourceCode()`][1], the plugin relies on. To keep the eslint config working with ESLint v10, this replaces `eslint-plugin-brace-rules` with the [`@stylistic/brace-style`][2] rule from `@stylistic/eslint-plugin`, a package we already use. While `@stylistic/brace-style` doesn't offer an option to format braces in exactly the same way as before, the "allman" style seems to be the one closest to the existing code. [1]: https://eslint.org/blog/2025/11/eslint-v10.0.0-alpha.0-released/#removed-deprecated-rule-context-members [2]: https://eslint.style/rules/brace-style 2025-12-30 00:57:37 -08:00			`return new Promise(closePageCallback =>`
			`{`
Return a promise from most page-inits Adopt the new interface by all pages which close themself. (Not thous using `Engine.SwitchGuiPage`.) 2024-09-21 11:24:36 -07:00			`Engine.GetGUIObjectByName("btnClose").onPress = closePageCallback;`
			`});`
Do not allow to start pyrogenesis with incompatible mods Fixing following problems: Issue number one: Enable mod with a23 compatibility in a23b. Save configuration. Start a24. Better result: Mod will be enabled and invisible in mod selection screen producing various errors. Worse result: Game will crash and refuse to start. Issue number two: Mods can silently set loaded mods without restarting the engine, so mods can unlist themselves from compatibility detection. Solution: Enable necessary mods instead if running with gui and open mod page. Open information window on top of mod page to infom why mod page is showing up. On mod page show mods which failed in compatibility check and color the resposnible ones. Disable start button without enabled mods. Show non existed mods if they failed in compatibility check. Else just log to mainlog and close. Another fixes: Display in enabled mods really enabled mods as current logic confuses players about which mods they have enabled and is not helpful (ref #4881) Note: this will not solve issue with mods claiming being compatible with engine version while in fact being incompatible. Comments by: @vladislavbelov, @Stan, @Imarok Tested by: @wraitii Differential revision: D3592 Fixes: #6044 #4881 This was SVN commit r25410. 2021-05-09 06:53:25 -07:00			`}`