The reason is simple... ClientVerification's Initialize() function is being set AFTER ClientPatchGump's Initialize() function (cause they are executed by class in alphabetic order). There are two options, move the ClientEnforcement to OnLogin where it is executed many times (probably no harm), or set it yourself in ClientVerification.
RunUO Community
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Client Patch Warning
- Thread starter Joeku
- Start date
I could modify it to make it not-work in certain circumstances, but it would require a PlayerMobile edit (which I was trying to avoid). Either way, if the owner doesn't want that, he can set it to "0" and remove any possible exploits. Note that the player will still be able to be attacked after 15 seconds, so either way he can still get attacked. Before, if you didn't press the button, it simply didn't un-invul you. This provides a better alternative.XxSP1DERxX said:
I could make a check to see if the player already has combatants before the gump is sent, if you think that'd help.
As long as the timer to unbless doesn't stop when a player disconnects, which it shouldn't, everything should be fine. I added a failsafe, so that when any player logs in, they are unblessed. Note that this does not apply to staff members. This feature works well with default RunUO, but it might conflict with some custom scripts that have anything to do with blessing the player. The way I see it: that's not my problem. 
The reason I had to add the failsafe was because, whenever the shard gets shut down/restarted, all of the timers are stopped and the player is left blessed. While there is a shut down event, there is no such thing as a restart event, so I had to add the login failsafe. It's possible to get this script to work in a much more organized fashion than it currently does, but that would require distro files and I'm trying to avoid that. This way, it covers everything.
Please tell me if the timer would stop when the player disconnects, I believe it wouldn't.
P.S. I didn't add freezing, I forgot it!
I'll add it in the next update.
The reason I had to add the failsafe was because, whenever the shard gets shut down/restarted, all of the timers are stopped and the player is left blessed. While there is a shut down event, there is no such thing as a restart event, so I had to add the login failsafe. It's possible to get this script to work in a much more organized fashion than it currently does, but that would require distro files and I'm trying to avoid that. This way, it covers everything.Please tell me if the timer would stop when the player disconnects, I believe it wouldn't.
P.S. I didn't add freezing, I forgot it!
I'll add it in the next update.Prohor Meletevich
Wanderer
It isnt works for 3D client.