/sethome blocked because of monuments even when allowed in ConfigSolved

Hi all,

/sethome seems to be continually blocked at momuments even when I have interruptTP set to false for monuments. It seems to be in the code setup that way:

 private string CheckPlayer(BasePlayer player, bool build = False, bool craft = False, bool origin = True, string mode = "home")
        {
            if (config.Settings.Interrupt.Oilrig || config.Settings.Interrupt.Excavator || config.Settings.Interrupt.Monument || mode == "sethome")
            {
                string monname = NearMonument(player.transform.position);

                if (!string.IsNullOrEmpty(monname))
                {
                    if (config.Settings.Interrupt.Oilrig && monname.Contains("Oil Rig"))
                    {
                        return "TPOilRig";
                    }

                    if (config.Settings.Interrupt.Excavator && monname.Contains("Excavator"))
                    {
                        return "TPExcavator";
                    }

                    if (mode == "sethome")
                    {
                        return "HomeTooCloseToMon";
                    }​
Is there a reason why sethome ignores the config? Thanks

it isn't ignoring the config. there is no option for it. interrupt is specifically for teleporting, not setting a home or viewing info :p

There is no config setting for this yet. Nothing about this is ideal yet. I personally don't care if people sethome at monuments. It has ALWAYS been allowed up until now. There is no pleasing everyone unless I add options for literally EVERYTHING.

Interrupt settings are for interrupting a teleport only. Some server owners will want to block setting homes at monuments while still allowing teleports. You can't do that if interrupt settings apply to setting a home too. You will have to wait until I can add more options.

Sorry, that wasn't intended as a complaint. I just wanted to make sure I understood the changes so I could explain them to my players. 

As for whoever complained about setting a home in a monument, all they had to do was turn on force on foundation. I'm sorry for the issues.

I ended up just removing the sethome references in the code. I don't have force on foundation and we allow players to set homes at monuments. For some reason this was blocking it entirely even though it was for some reason working fine with a prior version. That solved it. Not sure why sethome in particular is considered seperately to the config settings.

I explained this already. Read the reply...

Yep I read it, I just couldn't get it to work based on the config. So the only way to allow /homes from what I could see was to remove the below line. I love your work Nivex, and maybe this is me not understanding how to make use of the config properly. Just sharing what worked for me that's all. Thanks for everything you do :)

if (mode == "sethome")​
h3Hns22wE9F9nlr.jpg Kinesis

Yep I read it, I just couldn't get it to work based on the config. So the only way to allow /homes from what I could see was to remove the below line. I love your work Nivex, and maybe this is me not understanding how to make use of the config properly. Just sharing what worked for me that's all. Thanks for everything you do :)

if (mode == "sethome")​

Thanks! i had the same problem

Locked automatically