Add Armory engine to SteamDB

[rpaladin]

Hi @tong. I've noticed that Armory isn't included in the Steam Game Engines list. A pull-request can be conducted at the SteamDB repository to add new game engines to the SteamDB game engines list. They already accept other Haxe game engines, so I'm sure they'd accept Armory (they already accept the Blender Game Engine).

Haxe game engine examples:

• https://steamdb.info/tech/Engine/Lime_OR_OpenFL
• https://steamdb.info/tech/Engine/HashLink
• https://steamdb.info/tech/Engine/Heaps

The reason I'm pinging you is because you seem to be the most qualified for the job. Feel free to disagree and someone else can do it if they'd like.

[tong]

Not sure what qualifies me for that, but i can try :)

From what i know there isn't that much output to be sure it's armory.
Since there is an option to export json instead of arm files we cannot be sure such files to be included.

Another option might be one of these:

• brdf.png
• shader_datas.arm
• smaa_area.png
• smaa_search.png

I think (?:^|/)shader_datas\.(arm|json)$ might work.
@MoritzBrueckner @luboslenco right?

[MoritzBrueckner]

From all options you mentioned I think shader_datas is the safest, but even with that I see potential conflicts, the name might not be that uncommon after all... However, other engines/tools also seem to use paths that one might accidentally recreate, so perhaps we should just go for it. An alternative would be to include a dedicated file (e.g. ".armory-project"). If someone doesn't want to make their project recognizable by automated tools, they can simply remove that file (or we implement a setting for this).

In case we go with shader_datas, we should probably include .lz4 as a shader_datas file extension just to be safe, even though with the current code I think shader_datas is still exported as .arm even if compression is enabled.

[MoritzBrueckner]

One more thought: If we decide for a dedicated file like .armory-project, this will only work for projects using newer SDKs. I don't know for example what SDK version Offroad Mania is using, but I suspect it might be an older one that is modified to the developer's needs.

[tong]

I wouldn't add such file just for the sake of engine detection, but maybe we have some use for it (like: #2472 ähem).

[rpaladin]

One more thought: If we decide for a dedicated file like .armory-project, this will only work for projects using newer SDKs. I don't know for example what SDK version Offroad Mania is using, but I suspect it might be an older one that is modified to the developer's needs.

He still uses Armory 0.6 for some reason.

[rpaladin]

Hello @tong and @MoritzBrueckner (please excuse the pings). This topic came up on the Armory Discord. Any progress or plans on implementing Armory to the Steam database? I think it would really help people of the Armory community (past, current, and future) to see the power of Armory. Or at least that Armory is used and has a few, if not many games published on Steam.

EDIT: I'm in favor of adding some type of custom Armory named file. Legacy Armory won't be affected anyhow, so we might as well add the new format/name to new ARMSDK builds.

• If everyone is still confused on which regex expressions to use for Armory, perhaps leave it up to the SteamDB repository owners by creating a GitHub issue regarding Armory? It's how the BGE category exists (initially the category was named UPBGE, but the Godot GitHub owner renamed it).