[Fearts]

On a few of my servers (Windows) I'm experiencing some crashes. They are seemingly random and I do notice that the Mayhem glitch is present before the crash. I also notice the Mayhem glitch will appear very shortly after a crash. These are servers where I have never experienced the Mayhem glitch before and I haven't added any new plugins.

I can see the Mayhem glitch is present because Demo grenades will go through the walls and floor.

Is anyone else seeing similar issues?

[Horsedick]

You were careful to mention this "Mayhem glitch" 4 times.... what is this glitch?

[Fearts]

Originally Posted by Horsedick You were careful to mention this "Mayhem glitch" 4 times.... what is this glitch?

https://forums.alliedmods.net/showthread.php?t=99819

Here is a thread where I believe the term was first coined.

Basically physics props in the game start to act weird. In TF2 the most noticeable thing you see is all Demo grenades will fall through the floor and walls.

[Fearts]

I think I found the issue. I needed to update one of my gamedata offsets:

"Games"
{
    "tf"
    {
        "Offsets"
        {
            "WeaponReset"
            {
                "windows"    "408"
            }
        }
    }
}

[Horsedick]

I believe the Weapon Reset gamedata for windows should be 412 unless it got changed today.

[Powerlord]

I can only tell you that the current Linux offset for CTFWeaponBase's WeaponReset is 417. No idea how far off Linux CTFWeaponBase offsets are from their Windows versions... most classes are off by one, but that only applies if Valve didn't decide to inline anything.

[psychonic]

Originally Posted by Powerlord but that only applies if Valve didn't decide to inline anything.

Virtual functions cannot be inlined, and most inline-ings are done via the compiler as an optimization, rather than manually.

Differences between offsets in the vtable across compilers are caused by having virtual dtors (this is the +1 on Linux/Mac from Windows, from GCC/Clang adding a second entry for it), function overloads (MSVC reverses the order for these), and multiple inheritance (MSVC creates multiple vtables, GCC/Clang stick it all into one), among possible other factors.