[YuGiOhJCJ]

Hello,

Since AMX Mod X 1.8.2, the amxmodx website is providing its own metamod version (metamod-1.21.1-am) because of the new steamcmd utility.
However, that was when metamod version was 1.19.
Now, we have metamod version 1.20.
Regarding the ChangeLog of metamod version 1.20, I don't see that it is now compatible with steamcmd.

Should I use metamod 1.20 or metamod-1.21.1-am with steamcmd and AMX Mod X 1.8.2?
Where is the source code corresponding to metamod-1.21.1-am please?

Thank you.
Best regards.

[Arkshine]

AM version is the most up-to-date.

Essentially, the changes with the latest official metamod version and AM are:
- OSX support
- Support of the new engine pfnCheckParm function
- Better support for newer compiler

https://github.com/alliedmodders/met...commits/master

[YuGiOhJCJ]

OK, thanks for the information.
But I am still wondering something: Is metamod 1.20 compatible with steamcmd and AMX Mod X 1.8.2?

OK, so the source code corresponding to metamod-1.21.1-am is corresponding to the "75ce273c55a6fad764b066b8076cd3348e7610dd " git commit [1], isn't it?

Reading the git log in order to find the corresponding source code of a release is not easy.
Why developers don't use the git tag feature in order to release their source code?
Example:
$ git tag 1.21.1-am 75ce273c55a6fad764b066b8076cd3348e7610dd
$ git push origin --tags

[1] https://github.com/alliedmodders/met...6cd3348e7610dd

[Arkshine]

I'm not sure what you're trying to do or what you don't understand.

The latest source code is the master : https://github.com/alliedmodders/metamod-hl1
SteamPipe update happened in 2013, you just need to look at the first page of commits anyway.
I'm not the maintainer of metamod, but yes having tag is handy.

1.20 can likely work on games which don't use pfnCheckParm (which is the case for CS).

[YuGiOhJCJ]

My goal is to install a counter-strike 1.6 dedicated server with steamcmd, metamod, amxmodx and podbot.
Previously, I was using hlds instead of steamcmd and I read that the metamod version I was using (metamod-1.9) is not compatible [1].

I already know how to get the latest source code of "metamod-am" (also named "metamod-hl1") but I prefer to get the source code corresponding to the latest release (metamod-1.21.1-am) for stability reason.

Previously, I was able to get the source code corresponding to a specific release through a tarball available on the metamod website [2].
Now, I need to get the source code of metamod-am from a git repository where the git tag feature is not used [3].

Anyway, I guess I have answers to all my questions now.
I will compile metamod-am from the source code corresponding to the "75ce273c55a6fad764b066b8076cd3348e7610dd " git commit.

I posted an issue to the developers to suggest using git tags: https://github.com/alliedmodders/metamod-hl1/issues/5
Maybe they will accept my suggestion who knows.

[1] https://forums.alliedmods.net/showpo...51&postcount=1
[2] http://metamod.org/
[3] https://github.com/alliedmodders/metamod-hl1

[Arkshine]

Last binary has been compiled on September 26, 2013. So the actual version starts likely at 6cbc0db76bd76b8fe692d6d36e08be40e32cd68d.
Then the four first commits are essentially related to compilation, not the code itself.
In others words, just use the current master version or simply use the available binary.