Jump to content

MON@H

Creator
  • Posts

    348
  • Joined

Everything posted by MON@H

  1. MON@H

    PunishAttacker

    Please, read description tab carefully. You must enable player to player damage in TruePVE plugin. This plugin will prevent damage. If you have issues - start support thread, post your config and give more details about your issue.
  2. MON@H

    PunishAttacker

    Added in latest version
  3. MON@H

    Life Support

    Read the description tab, I described the difference. While they look similar, my plugin was written from scratch and optimized much better, among other differences.
  4. MON@H

    Limit Entities

    Read the description tab, I described the difference. While they look similar, my plugin was written from scratch and optimized much better, among other differences.
  5. MON@H

    Raidable Bases

    Use "Chance To Automatically Spawn Each Difficulty" option in config
  6. Changed Status from Pending to Can't Reproduce
  7. Not able to reproduce this one. Please, post your full config file. Are there any errors in your console-log? Are you sure plugin was fully loaded when this happens? Enable logging and check for record like this: 01:46:50 73 players in cache
  8. MON@H

    Limit Entities

    OnEntityKill called when an entity is destroyed. So it's not related to building new entities, it's related to destroying ones. If you want to figure out what is causing your issue, feel free to add me on discord, I will give you a version with some additional logging for debugging. @M_#8888 In case with Copy Paste plugin, you can try to edit those options in it's config file to also reduce performance impact: "Amount of entities to paste per batch. Use to tweak performance impact of pasting": 15, "Amount of entities to copy per batch. Use to tweak performance impact of copying": 100, "Amount of entities to undo per batch. Use to tweak performance impact of undoing": 15, "EntityOwner (true/false)": true Try to set entityowner to false and see results
  9. MON@H

    Limit Entities

    @MNfreakTim, despite the fact that the plugin is optimized as much as possible, checking each building for compliance with the limit in any case occurs and uses some part of the resources - this is inevitable and I hope it is obvious. I have done everything I can to optimize this plugin in order to minimize the load on the server. As far as I know, any server, regardless of the amount of its resources, will start lagging when a certain number of buildings is reached. The more resources the server has, the more buildings it allows to build without lags. Perhaps you have reached this very threshold of the maximum allowable number of buildings that the server can withstand without lags. Also, according to my observations, a large number of entities of a certain type (for example, wind turbines) in one place (for example, on the roof of the same building) significantly reduce FPS and can cause lags. Actually, to prevent all these problems, similar plugins were created. You can, of course, remove it completely, but most likely this will not solve your problem.
  10. MON@H

    PunishAttacker

    @unrealtairo What jail are you referring to?
  11. MON@H

    Windmills

    Changed Status from Pending to Closed
  12. MON@H

    Windmills

    Changed Status from Work in Progress to Pending
  13. MON@H

    Windmills

    Solved both issues.
  14. MON@H

    Windmills

    Who is the owner of that TC? BTW, your config contains error, see screenshot
  15. MON@H

    Windmills

    Changed Status from Pending to Work in Progress
  16. MON@H

    Limit Entities

    No idea. Try to ask author of that plugin
  17. MON@H

    Limit Entities

    Sorry, pasted wrong one, mine is just like yours, since it is default one: { "Translations override": { "zh-CN": { "fogmachine": "雾机" } } } Config file is only used to override translation phrases if you don't like Rust native ones. So config file is not metter, if you are not trying to replace phrases. So, please, forget about your config file. Follow my instructions above to check your console log to make sure both Rust Translation API plugin and TranslationsDownloader Extension works as expected.
  18. MON@H

    Raidable Bases

    Best plugin I have ever known. Great developer. Thank you for being awesome, nivex.
  19. MON@H

    Limit Entities

    I have a default config, nothing needs to be changed or configured. Just install the extention, the plugin and then restart the server { "API key (if required)": "", "Translation service": "google" } Then check the console log of the server there should be like this: 05:14 [Warning] Start downloading the translation files. 05:14 [Warning] Translation files were successfully downloaded(2.15MB) and extracted to '/oxide/data/Translations'. Means extension works like expected. Also check for this: 05:06 [Info] Loaded plugin Rust Translation API v1.0.3 by Arainrr Means plugin loaded fine.
  20. MON@H

    Limit Entities

    It works. Make sure to read the documentation page on uMod. You need to download translation file(s) and place it into oxide/data/Translations or install extention that will do it automaticaly on each server boot. It's needed to track new added items/languages.
  21. MON@H

    not working

    Changed Status from Pending to Not a Bug
  22. MON@H

    not working

    I see you have "Prevent ally damage (team / friend / clan)": false, this means you allowing members of team / friend / clan to damage each other. Also they will not get penalty because they are allies. If you want to be able to punish even allies then you should disable those options: "Use Clans": false, "Use Friends": false, "Use Teams": false, The idea was like if you want to punish your allies - just remove them from team / friend / clan and they will start to get penalty. Also, they may want to test something or teach one another how to shoot etc. So I suggest you use it as is and if you don't want to allow damage between allies, just change this option to "Prevent ally damage (team / friend / clan)": true, Also, for testing purposes you can use spawn player console command. It will spawn a dummy and you can shoot it without need to ask anyone for help.
  23. MON@H

    not working

    I have it installed on my own PVE server and it works without any issues. Please, describe your problem. What exactly not working?
  24. MON@H

    PunishAttacker

    I can, but the problem is it's not supported by ZLevelsRemastered plugin. Also, level penalty used only when 3-rd threshold reached and by default kicking player is taking place. With default config player must hit 15 times before this will be triggered, so are you sure 1 level is a lot for this player? Also, with default config, he will have to reconnect after being kicked and attack again during 5 minutes after last attack to get another -lvl. Just trying to clarify this.
  25. MON@H

    PunishAttacker

    Version 1.8.9

    155 downloads

    Tired of someone shooting into your players face on your PVE server? While it deal no damage it may lead to fps loss and be really annoying. This plugin will help you to punish them. The main idea of the plugin is to punish a player attacking another. There is variety of options in config file. You need to decide what exactly you want to do with attackers to punish them. Plugin will count every hit attacker made to another player. More hits - heavier punishment, because hits counter serves as multiplier. There are 4 thresholds by number of hits attacker made: The number of hits allowed without punishment The number of hits before death is used as a punishment The number of hits before kick is used as a punishment The number of hits before ban is used as a punishment Start with setting a number of hits you may allow do deal without punishment. Notifications to stop attacking players still appear (if enabled in config). Then set initial percentage of damage that attacker will get back. For example, by default it set to 0.5, so if attacker hits another player and dealt 30 hp damage he will get 50% back = -15 hp. Additionally ServerRewards RP will be discounted (if enabled in config) by formula: Initial server reward RP amount * The number of hits attacker made. After reaching death as punishment threshold punishment include death. After reaching kick as punishment threshold punishment include kick (if enabled in config) and additionally ZLevelsRemastered levels skills amount may also be taken (if enabled in config). After reaching ban as punishment threshold punishment include ban (if enabled in config). There are 2 ways to inflict damage on an attacker - using the slap plugin (if activated in config and loaded) or simply by taking away health. Here is an example of how this plugin works with default thresholds values (5, 10, 15) and Initial percentage damage (0.5) with 50 hp damage dealt by each shot. So by default, first threshold is 5 hits without punishment. Every hit attacker made he gets notification to stop attacking players. If player will continue hitting another player and reach first threshold 5 hits, on 6th hit he will get punishment: -25 hp (-50 hp, -75 hp and so on) and -100 RP (-200 RP, -300 RP and so on). If player will continue hitting another player and reach second threshold 10 hits, on 10th hit and every hit afterwards he will get punishment: death. If player will continue hitting another player and reach third threshold 15 hits, on 15th hit and every hit afterwards he will get punishment: kick and -10 levels skills in ZLevelsRemastered. You may also change time (5 minutes default) after which hits number will be cleared and count will start from scratch. Zone Manager support. If ZoneManager include mode is set to true, only attackers in specified zones will be punished. If set to false, only attackers outside specified zones will be punished. As a bonus, this plugin may help to solve several other problems: Protect personal growables from being damaged by other players Protect personal vehicles from being damaged by other players Prevent any fireball damage There is a problem with fireball damage in rust - you can't detect the author of this type of damage. So there is no way to know whose fireball is attacking target. This type of damage is dealt only by incendiary bullets. So to prevent players from abusing this you may want to disable incendiary bullets damage entirely. ## Permissions punishattacker.use -- give player/group this permission to activate punishment system for them punishattacker.immunity -- allows player to be ignored by punishment system ## Commands This plugin provides no commands ## Configuration Enable / disable notifications / logging Set SteamIDIcon steamid to set desired account icon in chat messages Enable / disable modes/plugins support ## Localization Out of the box plugins phrases are available on : English, Russian and Ukrainian { "Format.Prefix": "<color=#00FF00>[PunishAttacker]</color>: ", "Punishment.Damage": "Attacking other player punishment damage: <color=#FFA500>{0}</color>", "Punishment.Ban": "Banned for continuously attacking other player", "Punishment.Kick": "Kicked for continuously attacking other player", "Punishment.Kill": "<color=#FFA500>{0}</color> was attacking <color=#FFA500>{1}</color> and was punished", "Warning.First": "Stop attacking players or you will be punished!", "Warning.Second": "Stop attacking players or you will be killed!", "Warning.Third": "Stop attacking players or you will be kicked!", "Warning.Fourth": "Stop attacking players or you will be banned!" } Log file example:
    $15.00
1.9m

Downloads

Total number of downloads.

9k

Customers

Total customers served.

132.3k

Files Sold

Total number of files sold.

2.8m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.