UGather

Adds zones, permissions, and other options to modify gather rates!

Total Downloads: 6,566 - First Release: Mar 14, 2016 - Last Update: Apr 28, 2018

5/5, 19 likes
  1. Add console commands please.
     
  2. Yeah ill do that soon! If you want there is trygroup which gives you a list of all groups! Only works in RCON/Server console though.
     
  3. I want make day rates - x2, night rates - x5.
    Premium: day - x4
    Vip: day - x3
    With plugin Timed Events.
    This plugin send console command in 6:00 (for gather manager: gather.rate dispenser * 2) and 18:00 (dispenser * 5), all work perfect, but I cant setup Gather Manager for vip and premium.
     
  4. If you wanna do it for this that would be a bit harder as you would need to constantly add and remove people from groups. I could add this eventully though :)
     
  5. I dont understand you.
    I have a plugin "Timed Permissions" and web-shop.
    When player buy premium, he will get "premium" group.
    I need commands I can use FOR DAY like "igath gather regular 2", "igath gather vip 3", "igath gather premium 4"
    and FOR NIGHT like "igath gather regular 5", "igath gather vip 5", "igath gather premium 5".

    Maybe add permissions when I create new group?
    Example: I give "igath.premium" permission for premium, and he have x4 day, x5 night.

    Sorry for bad English.
     
  6. Ohhh, yeah when I update soon I will add a command/console command to change the gather rate of a specific group. So you can do that for example!
    [DOUBLEPOST=1460267752][/DOUBLEPOST]So you can do like "igath grate {groupID} x, x, x" to which will set the groups rate. Of course this will be added in the upcoming update.
     
  7. And player will have 4x day, if he have igath.premium permission?
    Ok, I wait update.
     
  8. I think its because a quarry in the rad town is running, I will provide a fix for this when I update with console command and such.
     
  9. I've edited the config so base group has a 10x gather rate, IG it says they have a 0x.

    How do I fix this?
     
  10. Sorry stupid mistake, go ahead and change it to 10 then delete the data file(Then reload the plugin). That should fix it!
    [DOUBLEPOST=1460313981][/DOUBLEPOST]I'll have to fix that in the next patch aswell, gotta check if gather rate has changed upon it loading :D
     
    Last edited by a moderator: Apr 10, 2016
  11. So you have to edit the .jsom then delete the .cs?
     
  12. No no, you edit the json, delete the data file which is "quarrylocks_qdata", then reload the plugin. I just made a fix for that problem so in the new update it should be fixed!
     
  13. I'll wait for the update honestly. But it's np thanks for the help
     
  14. Im getting these same errors, its lagging out my console and spamming every min with error messages. This is also lagging my server, the plugin is working just creating alot of these errors (in quote) and alot of frustration from players.
     
  15. Yeah im working on, finding a solution atleast! Ill put a quick update out soon to fix it.
    [DOUBLEPOST=1460341420][/DOUBLEPOST]Make sure your players dont use rad quarrys, thinking that is the problem. Could be wrong though!
     
  16. If it helps i do not think it is just the rad quarries, i get this error with or without rad quarries running.
     
  17. You guys deleted your data and had everyone rejoin right? Only other reason I can think of it causing errors.
     
  18. Yeah mate stopped server, deleted all data/lang/config uploaded new version restarted server reloaded plugin then let people join. Maybe is there a way to make it ignore this error? Besides the error everything seems to work how it should, it not working on static entities i think is good and should stay like that.
     
  19. Wulf

    Wulf Community Admin

    You may want to add some debugging output, and a friendly error if it fails to find a user in the data. Right now you aren't checking if the data exists, instead you're assuming the data exists and trying to set data that may or may not exist to a variable, which is where the issue is.