[Johnny got his gun]

Originally Posted by jtp10181 Originally Posted by AllMassive HEya - are there still issues with those fullupdate-cmds ? Should i install that plugin to avoid "bad behavior" of my server ?! it will always be a problem, as long as plugin authors continue to use bad style for coding and use a hudreset as a way to detect a new round.

I always used that way :-\
Got any ideas on how to do it properly then?

[twistedeuphoria]

register_logevent("newRound",2,"0=World triggered","1=Round_Start")

should work in most cases.

[Johnny got his gun]

That would be when the round timer starts, which is OK only in some cases.

[twistedeuphoria]

Yes, I know but it works for what I want to do most of the time.

[jtp10181]

Originally Posted by Johnny got his gun Originally Posted by jtp10181 Originally Posted by AllMassive HEya - are there still issues with those fullupdate-cmds ? Should i install that plugin to avoid "bad behavior" of my server ?! it will always be a problem, as long as plugin authors continue to use bad style for coding and use a hudreset as a way to detect a new round. I always used that way :-\ Got any ideas on how to do it properly then?

there are safe ways to do it using the end_round log event and some global variables. That prevent the resethud stuff from ONLY getting called on a new round. I did this in superhero. Basically you set something true on end round then flase on resethud.... or something. I did it some goofy way but it works good.

[Zor]

register_logevent("newRound",2,"0=World triggered","1=Round_Start")

This is all well and done for any ROUND based mods such as CS. But for DoD / TFC and most others it wont work as you DO respawn before the round ends...so what I need to do is if I use this ResetHUD, I will have to check that the player died prior / or went to spectator etx. So, is their any other way to capture the ResetHud.

Cheers!

[jtp10181]

good point.... non round based mods need a way to detect a new player spawn. Safest way to do it would be what you suggested. Set some var like... "playerdied[id]" to true upon death and when they first join. Then on the resethud event, if they are alive, set it to false. If the var is already false cancel out of the resethud event.

[ktrain]

only problem with that is not all mods use resethud

i have had so many incompatibility issues with zp and hi that i just give up on all plugins designed for cs, not worth the headache

[Uzeal]

Hello, sorry to bring up such an old thread but I have a question about fullupdate. It has recently been brought to my attention that fullupdate is what is crashing one of our servers quite frequently. Is there any actual use to fullupdate if it is ran client side, or is it just meant for server side use?

I want to implement this little fix to my server, but I want to show no mercy to the user if its only use is to crash the server.. I.E. rather than just blocking the command, I want to ban the user.

Would this code work for this?

#include <amxmodx>
public plugin_init() {
	register_plugin("fullupdate Blocker","1.0","JTP10181")
	register_clcmd("fullupdate","fullupdate")
}
public fullupdate(id) {
	server_cmd("amx_ban %s Permanent Attempted server crash", id)
	return PLUGIN_HANDLED
}

Thanks for the help

-Uzeal

[jtp10181]

there is no use for the command at all that I have found.

and your code would not work....

#include <amxmodx>
public plugin_init() {
    register_plugin("fullupdate Blocker","1.0","JTP10181")
    register_clcmd("fullupdate","fullupdate")
}
public fullupdate(id) {
    server_cmd("amx_ban #%i 0 Attempted server crash", get_user_userid(id))
    return PLUGIN_HANDLED
}

that might work, but its untested