From 9009f75bf5fd33e13abae5762d31968b39f233c3 Mon Sep 17 00:00:00 2001 From: Michael Smith Date: Sun, 15 May 2022 23:05:41 +0100 Subject: Fix GetEngineBuildNumber and entity property stuff I still haven't bothered to flesh out all the possible indices for GetEngineBuildNumber but we're back to being able to use it to detect The Last Stand (as a result of some old version testing Aciidz did - thanks again!). This means we can do away with the terrible map file- based hotfix. Also, turns out sst_l4d_testwarp doesn't work if the plugin gets loaded early via VDF because certain SendTable offsets start out negated, so we work around that too now. --- gamedata/engine.kv | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'gamedata') diff --git a/gamedata/engine.kv b/gamedata/engine.kv index 39fa1df..80caa74 100644 --- a/gamedata/engine.kv +++ b/gamedata/engine.kv @@ -26,16 +26,19 @@ vtidx_GetGameDirectory { 2013 35 } Client013 { - L4Dx 36 // AND THEN THEY CHANGED IT BACK LATER! + L4Dx 36 // AND THEN THEY CHANGED IT BACK LATER! (on 2.0.4.1) default 35 // <- most things have this! } Client012 37 // dmomm, ep1, ... } -// TODO(compat): apparently this changed, in early versions it's NOT 99! -// Come up with some way to detect it properly!? vtidx_GetEngineBuildNumber { - //L4D2 99 + L4D2 { + Client013 99 + //Client014 ??? // TODO(compat): find out what this (maybe 136?) + } } + +// VEngineServer vtidx_PEntityOfEntIndex { OrangeBox 19 } // probably OE too but??? sz_edict { -- cgit v1.2.3