[OrphanShadow]

Originally Posted by FlaminSarge Orphan: reason for that is already known: Hale's health hits a multiple of 1024 and the clientside health bar hits zero (before looping back) hence he sees himself as sorta dead.

Cool. Also found that taunt needs redefining because they mest up the keyboard map for taunts or something.

Ill patiently await the update =3

[FlaminSarge]

Taunt is +taunt now, so ok.

[PMAvers]

Slightly OT, but was that Eggman's hat that was included in today's update? Thought that name sounded familiar.

[BBG_Theory]

Originally Posted by FlaminSarge Post it! I might be able to code it into VSH too, if I know which entities to replace/disable. Also tf2update probably broke everything I DO NOT WANT TO SEE ANYTHING ABOUT THIS BEING BROKEN BECAUSE WE ALREADY KNOW.

Yes it is broken for me on at least a Windows server, will try Linux later tonight or tomorrow. I did update hooks and items (saw there was an update for items already) but it acts just like the last time items was needing updating. server will run, but as soon as you join and select a team, it crashes. This behavior is exactly the same behavior the server showed, the last time new items was introduced into the game.

Running the latest snapshot of metamod and sourcemod, and the latest release of tf2items_release-3ce0e7f1a3a7 and sdkhooks-2.1.0-windows

Help / advice anyone????

[serpentine]

Update your tf2items, works fine for me after that. Windows server.

edit: It does work, however taunting with full rage meter does nothing, and while running around as hale it's as though your legs are under the ground, choppy feeling.

[loranger]

when i load plugin, i get a fatal error from that line:

CreateNative("VSH_IsSaxtonHaleModeEnabled", Native_IsEnabled)

server keep crashing and i just did a fresh install

[BBG_Theory]

Originally Posted by serpentine Update your tf2items, works fine for me after that. Windows server. edit: It does work, however taunting with full rage meter does nothing, and while running around as hale it's as though your legs are under the ground, choppy feeling.

I have! im using the very latest snapshot of everything. Metamod, sourcemod, tf2items_release-3ce0e7f1a3a7 , hooks

What sourcemod and metamod are you using???

[loranger]

Originally Posted by BBG_Theory I have! im using the very latest snapshot of everything. Metamod, sourcemod, tf2items_release-3ce0e7f1a3a7 , hooks What sourcemod and metamod are you using???

same here.. im using stable 1.8.9 sm and MMs from gameserver and I get consecutive crash soon as i load saxtonhale.smx..

My first tought was looking into /gamedata files but everythinng looks fine

[x6herbius]

I can confirm that when I played the mode this morning, Saxton's rage wasn't working (taunting at full rage just did the taunt and nothing else) and there were points where the camera for the person playing as Saxton hovered about 8 inches off the ground. It wasn't just the 1024-bug either (I've known that happen and it wasn't the same). A lot of people were suiciding as Saxton because it was difficult to win while playing as him.

[FlaminSarge]

I have the ANSWER to all of those problems and the SOLUTION to about half of those problems.
P1) Hale's rage isn't working.
A1) The "taunt" key is now "+taunt" rather than just "taunt". It's an easy fix, and I've already fixed it, will upload asap.

P2) Hale's view is half-underground, etc.
A2) This IS the 1024-bug. Valve changed it so that there's some range of health above 1024 where you appear "dead" instead of just at 1024, so now most of the time, Hale's like that. I'm going to test what bounds those are, so bear with me. I'll try to come up with a fix, if Valve doesn't fix it or doesn't want to fix it.

I've also fixed a definite exploit/bug with the High Five taunt.

Originally Posted by BBG_Theory I have! im using the very latest snapshot of everything. Metamod, sourcemod, tf2items_release-3ce0e7f1a3a7 , hooks What sourcemod and metamod are you using???

Updating to the latest Sourcemod snapshot, plus updating tf2items, worked for me, and I had that exact same problem. This was on all my servers, not just VSH.