[leiftiger]

Originally Posted by dirka_dirka the reason for the plugin was to fix the charger stick issue - which was fixed. however since l4d1 there have been cases and places where you can still get stuck. so this plugin still has a use and should be approved. does it unstick infected? i had this happen to me the other night while being a hunter. i plan to add this to my server, but might restrict it to admin use.

This plugin is for both survivors and infected, not only charger.

[Ydiss]

This needs to be approved again. I've used this twice since the charger fix. I was a charger myself when using it.

This is still a very useful plugin and I'm keeping it on my server indefinitely.

[PeterFreimann]

Error-Message on my L4D2 Servers:

[SM] Plugin encountered error 15: Array index is out of bounds
L 02/06/2010 - 11:29:25: [SM] Displaying call stack trace for plugin "l4d2unstick.smx":
L 02/06/2010 - 11:29:25: [SM] [0] Line 57, /home/groups/alliedmodders/forums/files/5/2/3/6/9/54198.attach::OnClientDisconnect()

[cartman-2000]

do you have more then 19 slots on your server?

This also works on servers from other games too, with a few modifications.

[IronWarrior]

If a hunter/jockey/smoker/charger has you, you can't use this command to escape right?

[cigs]

right

[IronWarrior]

Originally Posted by cigs right

Thank you, just wanted to check.

[CUatTHEFINISH]

Originally Posted by PeterFreimann Error-Message on my L4D2 Servers: [SM] Plugin encountered error 15: Array index is out of bounds L 02/06/2010 - 11:29:25: [SM] Displaying call stack trace for plugin "l4d2unstick.smx": L 02/06/2010 - 11:29:25: [SM] [0] Line 57, /home/groups/alliedmodders/forums/files/5/2/3/6/9/54198.attach::OnClientDisconnect()

cartman-2000 is correct, this error should only happen if your maxplayers is above the max array size set in the code. As far as I know L4D1 and L4D2 only support maxplayers of 18, so there shouldn't be a reason to set that higher in your server command line. Unless a new update snuck that in somewhere.

[IronWarrior]

Awesome, thank you V10.

Will install your version.

[dirka_dirka]

Don't think I ever looked at the code before, but now I found a few more places to improve the code from v10. This is basically what I did:

PHP Code:

/*
    v1.1 (by me) was modified from v1.0.7:
    -    Fixed up 1 if/else if case.. removed 3 or 4 checks, with the poential to skip a couple more.
    -    Fixed another if/else case from 2 possibilites to 3 (with the same number of checks).
    -    Made the teleport somewhat random (x & y only - z should always be up).
    -    Renamed the command from stuck to sm_stuck. This allows you to use sm_stuck in console, as well as !stuck, !sm_stuck, /stuck and /sm_stuck in chat.
    -    Added color the the chat messages
    -    Renamed the global vars and initialized the handles.
    -    Reduced the number of calls on the teleport cvar.
    -    Enforced good code format (with #pragma semicolon 1)
    -    Cleaned up indentation and some un-necessary comments (either from code that no longer exists or because the var name is more clear now).
*/ 


You can change the amount of teleporting with:

PHP Code:

#define    MIN_TELEPORT        3
#define    MAX_TELEPORT        5 


near the top of the source - the original was just 4. I haven't played around with the numbers much yet which is why I setup the option like that.

*removed plugin - see later post..