[Starbish]

will sourcemod support them?

or no plans yet?

[psychonic]

The reverse engineering effort for it is very low priority right now. MM:S was (mostly) working at some point, but SM (or similar) is a very long way off. There are numerous large changes in the engine to figure out and then figure out how to adjust our code to gracefully handle both paths with minimal API change.

[Starbish]

Originally Posted by psychonic The reverse engineering effort for it is very low priority right now. MM:S was (mostly) working at some point, but SM (or similar) is a very long way off. There are numerous large changes in the engine to figure out and then figure out how to adjust our code to gracefully handle both paths with minimal API change.

Wow, thank you for your replying and efforts in developing them.

[Prof. Orribilus]

Instead of extending the support on Source 2, isn't the case to create a separate environment? If AMX Mod X is for GoldSource, SourceMod is for Source, should a SourceMod 2 be for Source 2?

[psychonic]

Originally Posted by Prof. Orribilus Instead of extending the support on Source 2, isn't the case to create a separate environment? If AMX Mod X is for GoldSource, SourceMod is for Source, should a SourceMod 2 be for Source 2?

No. It would clearly be "Source2Mod".

Joking aside, there's a lot at play here. While there's much less of an engine and server API/ABI change between Source and Source 2 for the parts we care about, there's still much that needs to be reverse-engineered (or an actual SDK release). There's also only a single game released on the platform, and it's not a good example of the kind of games that we typically support or users write plugins for. When SourceMod supported Dota 2 on Source 1, there were very few consumers compared to something like CS:GO due to the nature of the game.

Metamod:Source is working on Source 2, although support hasn't been upstreamed yet. I do have a fairly sizable plugin running with it.

We're not really near a point that we could start porting SourceMod, although I do think it's doable.

If we were to decide that it wasn't feasible or practical to port SourceMod and thought a different approach would be appropriate, we'd also want to consider is that there is already a scripting API in newer games (L4D and onward), Valve's "vscript". It implements Squirrel, Lua, or both, depending on the game, and has the benefit of first-party support (no/less random breakage on updates). With MM:S alone, it is also fairly trivial to extend the Valve-provided scripting API with plugins. I did some proofs-of-concept with that on Source 1 and the Source 2 vscript C++ API has not changed much.

[Prof. Orribilus]

Originally Posted by psychonic No. It would clearly be "Source2Mod". Joking aside,

Hehe. I agree with "Source2Mod" however.

Originally Posted by psychonic there's a lot at play here. While there's much less of an engine and server API/ABI change between Source and Source 2 for the parts we care about, there's still much that needs to be reverse-engineered (or an actual SDK release). There's also only a single game released on the platform, and it's not a good example of the kind of games that we typically support or users write plugins for. When SourceMod supported Dota 2 on Source 1, there were very few consumers compared to something like CS:GO due to the nature of the game.

Ok.

Originally Posted by psychonic Metamod:Source is working on Source 2, although support hasn't been upstreamed yet. I do have a fairly sizable plugin running with it. We're not really near a point that we could start porting SourceMod, although I do think it's doable. If we were to decide that it wasn't feasible or practical to port SourceMod and thought a different approach would be appropriate, we'd also want to consider is that there is already a scripting API in newer games (L4D and onward), Valve's "vscript". It implements Squirrel, Lua, or both, depending on the game, and has the benefit of first-party support (no/less random breakage on updates). With MM:S alone, it is also fairly trivial to extend the Valve-provided scripting API with plugins. I did some proofs-of-concept with that on Source 1 and the Source 2 vscript C++ API has not changed much.

So, are you telling that future Source 2 games could yet have a good server-side plugins API making a Source2Mod quite unneeded?

[Powerlord]

I admit I've only glanced at the L4D2 version of vscript, but it didn't appear to have any administrative functions in it.

While you can create things like new game modes, having no functions to kick/ban users... or even show menus... is kind of a big deal.

[psychonic]

Originally Posted by Powerlord I admit I've only glanced at the L4D2 version of vscript, but it didn't appear to have any administrative functions in it. While you can create things like new game modes, having no functions to kick/ban users... or even show menus... is kind of a big deal.

Quite right, but as noted, that kind of API could be created and exposed to the vscript VM via a Metamod plugin.

[psychonic]

Originally Posted by Prof. Orribilus So, are you telling that future Source 2 games could yet have a good server-side plugins API making a Source2Mod quite unneeded?

It's already possible with vscript-enabled games now. No one has ended up making any admin API for that layer though (afaik), and many people prefer SourceMod as it's what they already know and are familiar with, as well as due to the wealth of functionality it already exposes.

[Prof. Orribilus]

Ok, thanks for the informations.