Required skills: Python

Difficulty: Easy

openage currently stores information about a game edition or expansion inside an Enum, e.g. media paths, support status, etc. We should store this information in an auxiliary file instead, similar to #1312. That would make updating and correcting game information easier as we no longer have to replace chunks of code.

The recommended appro

多实例（主要是v2ray多实例）需求，主要是两个场景，且难以用其它方式替代。请拨冗考虑，未来是否可以增加此特性。

场景1、代理链式转发

在 #742 中关于代理链式转发的讨论，使用proxySettings代理出站流量的方向是对的，但在实操中，结合机场的订阅，需要将机场的信息编辑到复杂路由的json配置中，当切换线路时非常的麻烦。

我现在的做法，是机场的代理提供一个本地socks5服务，比如端口为10801，v2ray中配置一个socks协议的outbound，作为vmess的proxySetting。整个链路大致是这样的:

  浏览器  -> 
  # 代理
  socks://127.0.0.1:1080 -> vmess outbound (proxySetting on socks)-> socks outbound -> 
  #

Conan can't work on OpenBSD.

ERROR: Invalid setting 'OpenBSD' is not a valid 'settings.os' value.
Possible values are ['AIX', 'Android', 'Arduino', 'Emscripten', 'FreeBSD', 'Linux', 'Macos', 'Neutrino', 'SunOS', 'Windows', 'WindowsCE', 'WindowsStore', 'iOS', 'tvOS', 'watchOS']

I believe that this implementation can be used for broadcast communication and also for games that want to hear a channel that is rolling a song for example.

Could you put a shortcut so you can start and end listening to a certain channel?
If you can have the implementation of a shortcut also to adjust the level of the channel. It will be perfect.

We are in the process of dropping Math.h and one of the more commonly used operation there is fequals, which checks if the difference between two values is less than the type's epsilon. The task is to write this as a free function, probably in a new file in the util directory and drop Math::fequals.

Bug Report

This happened on Windows with the Pro IDE. This is all I can see in the logs:

root ERROR Uncaught Exception:  Error: 2 UNKNOWN: error getting port list from serial-discovery: read |0: The handle is invalid.
root ERROR Error: 2 UNKNOWN: error getting port list from serial-discovery: read |0: The handle is invalid.
    at Object.callErrorFromStatus (c:\Users\kittaakos\Desktop\

Describe the feature you'd like
We should limit the miss angle to effectively be around 15 degrees.

Describe why do you think it is needed
Missing a target by 90 degrees just look stupid - a miss is a miss. Doesn't have to be that off 😁

https://www.reddit.com/r/warzone2100/comments/gy87wg/rookie_units_are_as_helpful_as_ever/