[[NATO]Hunter]

Originally Posted by OliMic Hi. Is this so I can access the plugin via the adminmenu? or what? Thx for a great plugin.

No, this means other plugins can access the plugin.

[Ska]

Server crashes with plugin when someone chooses medic.

Server: TF2 1.0.5.9, Sourcemod 1.2.2-snapshot, no other plugins

Error message on crash:

Bad entity in IndexOfEdict() index -1680799 pEdict 0E0E0FA0 sv.edicts 100F0010

[Max_Damage]

Thanks for this plugin!

[DontWannaName]

I just got this in my log, I know cashworks has a lot of entitys but wanted to let you know.

L 07/28/2009 - 19:45:12: Info (map "pl_cashworks_rc2") (file "errors_20090728.log")
L 07/28/2009 - 19:45:12: [medipacks.smx] Entity limit is nearly reached: 2039/2048
L 07/28/2009 - 19:48:58: [medipacks.smx] Entity limit is nearly reached: 2039/2048
L 07/28/2009 - 19:51:08: [medipacks.smx] Entity limit is nearly reached: 2039/2048
L 07/28/2009 - 19:518: [medipacks.smx] Entity limit is nearly reached: 2039/2048
L 07/28/2009 - 19:53:02: [medipacks.smx] Entity limit is nearly reached: 2039/2048
L 07/28/2009 - 19:53:03: [medipacks.smx] Entity limit is nearly reached: 2039/2048
L 07/28/2009 - 19:53:27: [medipacks.smx] Entity limit is nearly reached: 2039/2048
L 07/28/2009 - 19:54:27: [medipacks.smx] Entity limit is nearly reached: 2039/2048
L 07/28/2009 - 19:543: [medipacks.smx] Entity limit is nearly reached: 2039/2048
L 07/28/2009 - 19:56:19: [medipacks.smx] Entity limit is nearly reached: 2039/2048
L 07/28/2009 - 19:56:29: [medipacks.smx] Entity limit is nearly reached: 2039/2048
L 07/28/2009 - 19:58:52: [medipacks.smx] Entity limit is nearly reached: 2039/2048
L 07/28/2009 - 19:59:02: [medipacks.smx] Entity limit is nearly reached: 2039/2048
L 07/28/2009 - 20:00:02: [medipacks.smx] Entity limit is nearly reached: 2039/2048
L 07/28/2009 - 20:01:14: [medipacks.smx] Entity limit is nearly reached: 2039/2048
L 07/28/2009 - 20:02:42: [medipacks.smx] Entity limit is nearly reached: 2039/2048

[cpt.abort]

Is this still working with the new tf2 update and sm snapshot?

[retsam]

Hum is this error from offsets? I have not yet updated sm to 2738, but I do however have 2737 on there, and I get this error all over the place...


L 08/18/2009 - 07:47:42: [SM] [1] Line 268, medipacks.sp::Timer_Caching()
L 08/18/2009 - 07:47:43: [SM] Native "GetEntPropFloat" reported: Property "m_flChargeLevel" not found (entity 174/tf_weapon_smg)
L 08/18/2009 - 07:47:43: [SM] Displaying call stack trace for plugin "medipacks.smx":
L 08/18/2009 - 07:47:43: [SM] [0] Line 489, medipacks.sp::TF_GetUberLevel()
L 08/18/2009 - 07:47:43: [SM] [1] Line 268, medipacks.sp::Timer_Caching()
L 08/18/2009 - 09:116: [SM] Native "GetEntPropFloat" reported: Property "m_flChargeLevel" not found (entity 297/tf_weapon_jar)
L 08/18/2009 - 09:116: [SM] Displaying call stack trace for plugin "medipacks.smx":
L 08/18/2009 - 09:116: [SM] [0] Line 489, medipacks.sp::TF_GetUberLevel()
L 08/18/2009 - 09:116: [SM] [1] Line 268, medipacks.sp::Timer_Caching()
L 08/18/2009 - 09:117: [SM] Native "GetEntPropFloat" reported: Property "m_flChargeLevel" not found (entity 297/tf_weapon_jar)
L 08/18/2009 - 09:117: [SM] Displaying call stack trace for plugin "medipacks.smx":
L 08/18/2009 - 09:117: [SM] [0] Line 489, medipacks.sp::TF_GetUberLevel()

[physonic]

It still seems to work for me on TF version 1.0.7.0

but i get this error spam in my logs:
L 10/03/2009 - 03:29:25: [SM] [0] Line 448, /home/groups/alliedmodders/forums/files/1/7/5/5/1/35197.attach::TF_GetUberLevel()
L 10/03/2009 - 03:29:25: [SM] [1] Line 250, /home/groups/alliedmodders/forums/files/1/7/5/5/1/35197.attach::Timer_Caching()
L 10/03/2009 - 03:29:26: [SM] Native "GetEntPropFloat" reported: Property "m_flChargeLevel" not found (entity 130/tf_weapon_smg)
L 10/03/2009 - 03:29:26: [SM] Displaying call stack trace for plugin "medipacks.smx":

It also seems that everyone can pick up medpacks marked for own team only.. is this plugin still suspported?

I use SM: 1.2.4-hg2789

[retsam]

I dont know but I can tell you this plugin doesnt work for me anymore. It looks like its never gotten fixed, so I removed it. And ya those errors still spam the logs too.

[DontWannaName]

I dont get any of those errors... maybe im running a special version I dont remember.

[naris]

The version we have been using works fine using SM 1.2.3. No errors or crashes.

It does seem that I have made some changes to it, including adding this

ConVar

sm_medipacks_deploy 80 - Max UberCharge to deploy Medipacks with medigun