It's not really a game, but it mirrors the name used by HLE. I just pushed the "game" repository for the engine codebase to Github, you can find it here: That's actually a really good name, i'll have to keep that in mind
I'm also going to see if i can use the latest Steamworks SDK legally in this, i think i can force the other one to unload so i can load the latest and use that instead. That should eliminate any remaining problems caused by having to run under the original engine. To solve that problem i'm going to add special parsing to the command line object to treat commands passed as -meta: as though they were passed as. There is an obvious problem here with command line arguments having the same name as those used by the original engine, which could cause unwanted code execution. To load another tool, using -metatool "library name" -metatoolname "tool name" on the command line would do the trick.
That's assuming Hammer would ever support such an interface, but the essentials are there. This allows you to load any library and load any tool from it.Įventually it should be possible to load any number of tools concurrently from it using this approach, so you could do stuff like loading Hammer with it and talk directly to it from the game. It defaults to loading the Engine library and creating the default tool from it, which is using the interface name "IMetaToolV001". I've updated the engine to use a meta loader so it can load any tool. I wouldn't call it an SDK, it's a dump of their engine repository with a modified copy of the mod SDK and the code for each game removed from it.
0 kommentar(er)
