Not able to re sethome #5


  • Defect
  • Accepted
Open
Assigned to novafoxx161
  • crazypigfamilyfriendly created this issue Apr 16, 2016

    What steps will reproduce the problem? 1."/sethome Test" 2."/delhome Test" 3."/sethome Test"

    It is not possible to re sethomes at any new locations.

    What is the expected output? What do you see instead?

    "Home saved, use /home <homename> to get there! "You are not allowed to set anymore homes"

    What version of the product are you using?

    Do you have an error log of what happened?

    Please provide any additional information below.

    The Issue is this: Somehow a few players arent able to re sethome after deleting a home, it is just not working for only 2-3 players, 1 player got the maximum of 100 sethomes but only have 9 active sethomes, when he trys to re sethome it tells him you cant set any more homes. I can temp fix it with /edithomes playername limit xyz, that is the main issue we have since a few weeks. The bug/issue accure at the player Markdoon and RedCoffeeMaker, they both have the right permission after the plugin description.

    UUID of Markdoon: 2a3772f7-9829-4b05-b10f-425b0bd7e04b UUID of RedCoffeeMaker: 6e741ed3-b5ec-4da7-a323-781ddb40b173

    We are using CraftBukkit version git-Spigot-e4d4710-e1ebe52 (MC: 1.8.8) (Implementing API version 1.8.8-R0.1-SNAPSHOT) with following plugins: ActionHealth, AdminChatChannel-1.2.5, AdvancedAchievements, AdvancedBan, AIO-Jetpacks, AenaParkour, ArenaSpleef, AsyncWorldEdit, AsyncWorldEditinjector, Auto-Arm-0.8, Autorank, AutoSaveWorld, Backpacks-0.1.3, BattleArena, BedwarsRel, BedwarsRel-LuckyBlock Addon, BountifulAPI-1.5.1, Carz, Citiziens, Color_Signs_Text, CoreProtect_2.12.0, DeathMessagePrime, DiceFurniture, EnjinMinecraftPlugin, EssentialsChat-2.xSNAPSHOT, EssentialsSpawn-2.xSNAPSHOT, EssentialsX-2.0.1, ExtraHardMode-3.6.7, FurnitureLib, GlobalMarket-2.0.0.20, GriefPrevention, HideNSeek-1-5-9, iConomy, InsaneMobs_v1.9.8, Jobs3.3.1, Knock, LibsDisguises, LuckyBlock-1.8, MasterBuilders-MultiArena-1.8, MGOneInTheChamber, MGSkyWars, MinigamesLib, MobArena, MobEggSpawnerBlocker, Multiverse-Core-2.5, Multiverse-Inventories-2.5, Multiverse-Portals-2.5, MuteManager, MyCommand, NCore, NEnchantingEgg, NickNamer_v2.4.3, NoPluginViewer, NTheEndAgain, PacketListenerAPI_v3.3.3, PermissionEx-1.23.3, PressurePush, ProtectionLib, ProtocolLib, PwnFilter, RainbowArmor, RandomTPFix2, ServerSigns, Skins, SpawnJoin_5.0.0v, SuperVanish, Tablist, UltraCosmetics-2.1.2-RELEASE, uSkyBlock, Vault, Votifier, worldedit-bukkit-6.1, worldguard-6.1, ZavAutoMessager.

    Here is the latest.log link: http://www.filedropper.com/latest_1 The file was too big for PasteBin, i could only upload it via this website here, hope thats ok.

    Here are the SpawnJoin data files: config.yml: http://pastebin.com/8vNcYNMm HomeData.yml: http://pastebin.com/93f2iSuy list.yml: http://pastebin.com/Z5gjAxmw HomeSettings.yml: http://pastebin.com/UDRv0a5w permission.yml: http://pastebin.com/GmjLrvKg

  • crazypigfamilyfriendly added the tags New Defect Apr 16, 2016
  • NovaFoxx161 posted a comment Apr 16, 2016

    The issue seems to be that in the homedata.yml file, they have set more homes than they are allowed. To fix this either clear their homes and reset it to 0 so the plugin sees it as less than their max (would require a restart), give them the bypass perm to bypass the home limits, or give them a special home group that has a higher limit.

    The issue is also that you use home group limits, while useful, this overrides the per player home limits (not technically a bug/issue per-say, but can cause problems) using the edithome command works until they disconnect and reconnect as it does the permission check on join and sets the home limits accordingly.

    In the next update I do plan to add a way to get around this so it won't happen again. However due to personal matters and school, the update has been delayed a bit.


    Edited Apr 16, 2016
  • NovaFoxx161 removed a tag New Apr 16, 2016
  • NovaFoxx161 added a tag Accepted Apr 16, 2016
  • crazypigfamilyfriendly posted a comment Apr 16, 2016

    Ok that sounds awesome, and thanks for the fast reply! Im just editted the numbers at the homedata.yml and restarted the server, hope this fixed the issue we had, if not im sticking with the bypass perms for now.

    Thanks again and no problem, i know reallife can get busy sometimes :)

  • crazypigfamilyfriendly posted a comment Apr 17, 2016

    I just had a look thru the permission nodes again and was wondering if it matters when i add these permission node to a rank, if both nodes mean the same or if the capitals matter like this: i have created per rank sethomes with capital names for example "Legend"

    SpawnJoin.group.Legend or spawnjoin.group.legend


To post a comment, please login or register a new account.