HandyMan

I've thought of some possibles solutions to this.

1) Only allow 1 player to repair at a time on the entire server, sending a message to others that they must try again later.

2) Restrict the amount of entities repairable by a single person to a configurable maximum; e.g. 50

Thanks for reporting this.

Looks like I'll need to check for player resources before processing any data. Thanks for the report.

 

nivex updated HandyMan with a new update entry:

1.1.0

 

I think option 2 would be sufficient as I can see option 1 causing players to get frustrated.

EDIT: Sorry was thinking of another plugin! My bad :/

 

you mind me asking how it was built before this update? like entity wise. I've used it a long time and had to decrease the range to 10 and even at 10 it sometime almost made the server crash if someone bashed continiusly on their entity.

 

It performed more functions than needed which put strain on the server. This should be minimized now. If you still experience issues let me know and I'll see what I can do.

 

think about using coroutines, I know it's not so easy )

 

please add resource id to support updater plugin
ResourceId = 1737
thx

 

nivex updated HandyMan with a new update entry:

1.1.1

 

Great plugin @nivex ! All were missing now is an error message when missing resources. People are gonna have a hard time when it says, Guess I fixed them all... Guess I fixed them all... Guess I fixed them all... when there is missing resources.

 

nivex updated HandyMan with a new update entry:

1.2.0

 

Code:

ing] Calling 'OnPlayerTick' on 'Vanish v0.5.1' took 734ms [GARBAGE COLLECT]
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 1112ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 612ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 559ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 623ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 616ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 779ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 1057ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 835ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 842ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 870ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 822ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 856ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 829ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 902ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 870ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 732ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 792ms
15:29 [Warning] Calling 'OnStructureRepair' on 'EnhancedHammer v1.3.4' took average 5323ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 733ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 675ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took average 9084ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 624ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 615ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 547ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 545ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 503ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 564ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 584ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 533ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 677ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 579ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 636ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 670ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took average 6406ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 595ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 655ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 676ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 759ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 620ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 827ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 737ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 659ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 622ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 563ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 619ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 604ms
15:29 [Warning] Calling 'OnStructureRepair' on 'EnhancedHammer v1.3.4' took average 5257ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 606ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 682ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took average 9039ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 647ms
15:29 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 627ms
15:30 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 565ms
15:30 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 664ms
15:30 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 637ms
15:30 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 613ms
15:30 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 550ms
15:30 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 704ms
15:30 [Warning] Calling 'OnHammerHit' on 'HandyMan v1.2.0' took 678ms

 

@Hider Which server host are you using? That's insane.

 

spam on higher log appears when player unsuccessfully tries to repair buildings..
don't repair anymore with the latest rust updates for me, who else have so?

 

nivex updated HandyMan with a new update entry:

1.3.0

 

nivex updated HandyMan with a new update entry:

1.3.1

 

I'm hurried with conclusions

 

hey @nivex can you maybe create a activation timer? so when the command /handyman has been activate it will turn of after xx seconds
i would like to put the command in serverrewards shop so people can buy the command with rp in the shop.

for now if people buy the command the handyman in the serverrewards it stays on for every ; s

 

now players complain about lags

 

player tick flooding bug

 

Is this using resources properly? I've had players saying it doesn't. I have to test. Curious if others are seeing it takes resources to help speed my testing along.