TruePVE

Better PVE/PVP implementation

Total Downloads: 4,637 - First Release: Mar 25, 2016 - Last Update: Mar 7, 2018

5/5, 26 likes
  1. I'm not sure when they were seeing it.. but I want to say that it was happening randomingly..

    I want to just leave it on, but cant because I don't know that its going to enable and disable at the right times.
     

    Attached Files:

  2. Thanks - I'll test this out. Can you try to get clarification on when the players were seeing the message? Part of the schedule functionality is that it will send a player the schedule broadcast message when the player connects to the server so that they know what the current rules are. So if they were seeing the messages only when they connected to the server, that's intended functionality. I just want to make sure that this isn't what they're seeing.
     
  3. Its not what they were seeing. Just confirmed.

    It enabled, and disabled over and over again. not sure what the time between them was.

    But either way, it enabled on the wrong day.
     
  4. Hello - I have the following problem since version 0.7.8. I uninstalled v 0.7.8 completely, before I install v 0.7.12 and have also the last Oxide version. It does not happen when the server is started, but while it is working. The half day nothing happens and then 2x the following in the same time, in red font and in 'Log.Error.txt':
    [03/29/2017 21:34:54] Failed to call hook 'OnEntityTakeDamage' on plugin 'TruePVE v0.7.12' (NullReferenceException: Object reference not set to an instance of an object). I don't know, what it means and what can I do. Please help. Greetings from Germany.
     
    Last edited by a moderator: Mar 29, 2017
  5. Can you please upload your TruePVE config file? Also, do you know if anything was happening while the error printed? (Heli, arenas, scheduled changes, etc)
     
  6. Before the error-message comes, heli is starting. Here is my config:
    [DOUBLEPOST=1490823895][/DOUBLEPOST]Here is it in another view
    Sorry - I forgotten: In error-time, there are no players online and on the server are not arenas, zones or another. For heli, only the PlugIn 'Coptor Tracker' is working. Maybe it is not compatible?
     

    Attached Files:

    Last edited by a moderator: Mar 30, 2017
  7. It's possible it's related to Copter Tracker but I'm not certain (the code isn't clear). I normally use HeliControl to spawn helis for testing, and I've not seen this particular scenario before.
     
  8. OK. Thanks for the information! I will try to switch to HeliControl and then report. The curiosity is that this error message came yesterday only this one time, although the heli comes every 90 minutes.
     
  9. So, when used in conjunction with Zone Manager, would this plugin allow me to create an entire map that is PvE, but add zones within that map that are PVP?
     
  10. yes, it will... the only part that you have to modify is zone manager with a bit of code and set settings and map the zones in the truepve config to use zones. but that's it. It tells you how to do it on the overview page.
     
  11. Thanks!
     
  12. I'm sorry but I can't for the life of me figure out how to turn off lootable sleepers and corpses. They are on by default and the only options I see are to turn them on with flags and not off. Please help.
     
  13. Sleeper and corpse looting are OFF by default, and the flags turn them on. Admins can always loot sleepers and corpses. Are non-admins able to loot corpses/sleepers even with the flags not set?
     
  14. I was able to loot my sleeping admin body with another account that has no authorizations or permissions with oxide (through library sharing of the admin account). No flags set, everything is default. Even tried deleting config/plugin and redownload/reinstall.
     
  15. I'm not familiar with how sharing works regarding player attributes - can you verify that when you connect with the shared account that the console doesn't show auth level of 1 or 2?
     
  16. Doesn't show any auth levels on the non admin account.

    Also just tried it with a friends account that owns rust. Still able to loot sleepers with no auth levels
     
    Last edited by a moderator: Mar 30, 2017
  17. I'm not able to reproduce this - the only way I've been able to loot is to disable the admin checks or add the flag into the default RuleSet.

    I know you said you reloaded the default config, but could you verify TruePVE is set up to handle looting? In the config:
    Code:
    "Configuration Options": {
        "handleDamage": true,
        "handleLooting": true, // should be true
        "useZones": true
      },
    Do the rest of the rules and flags in the RuleSet work properly, and only looting is giving you problems? Also, what other plugins are you running?
     
    Last edited by a moderator: Mar 30, 2017
  18. OK, so I'm trying to setup PVP zones...I've got the code for ZoneManager installed and everything seems to be set, except when I try to set the PVP zone exclusions as specified in the FAQ, I'm not understanding exactly what they're asking for. The example says to enter the following in the Mappings section of the config:

    "Mappings":{
    "default":"default",
    "zoneId":"exclude"
    }

    I put that code in place and the plugin reloads properly, but I'm still not taking damage in the zones. it seemed likely to me that it was actually asking for a zoneID there rather than just the word "zoneId", so I changed that to actual zone number, but that failed to load the config file. so I'm confused on exactly how to use the mappings section to exclude zones from being managed by TruePVE, any any tips would be most appreciated. Thanks!
     
  19. @Mr. Jingles 2.0 - That bit of config is saying to exclude the zone with the specified ID from any TruePVE damage checks (as opposed to pointing the zone to a different set of damage handling rules).

    Make sure you're using the zone ID and not the zone name. You can verify the ID by looking at your ZoneManager.json file in /oxide/data (not to be confused with the ZoneManager.json in /oxide/config).
     
  20. For some reason it is now working after updating the server+oxide today. Thanks for your time!