I've had a few users report the same thing over time, (I've noticed it tends to be in caves, they also are working in groups of 3+), that they set a "home" go out and about. Then when they try to TP back to it. They get the message "Your home xxx was removed because it's not on a foundation or owned!" If they try to set it again, it will take it. They can view it on the list of homes. Yet, if they try to TP to it again, it will then remove it.
I'm guessing it has to do with this line in the json:
"ForceOnTopOfFoundation": true,
However, I noticed a while back if I set that to false, then they are able to set TP's on top of where ever they wish. Meaning they could go up to launch site and set it right by the elite crates.
Then I thought if I turn this one to true instead of false, that it would fix the issue. However, is it smart enough to know that the foundation is owned/shared based on the TC's auth? or is it by the person who laid the foundation? I'm trying to make it that they must have a foundation/"own" the building (auth'ed on TC) to set a "home"
"CheckFoundationForOwner": false,
Would you be able to tell me what is this needs to be set properly for that to occur? I noticed if someone gets raided and the person who did the raiding auth's on TC they can set a "home" down within that base. Then again, I've not tried that same method in a cave.
"Home": {
"AllowAboveFoundation": true,
"AllowCave": true,
"AllowCraft": false,
"AllowIceberg": true,
"Bypass": 0,
"CheckFoundationForOwner": false,
"CheckValidOnList": false,
"Cooldown": 15,
"Countdown": 15,
"CupOwnerAllowOnBuildingBlocked": true,
"DailyLimit": 100,
"ForceOnTopOfFoundation": true,
"HomesLimit": 6,
"LocationRadius": 25,
"Pay": 0,
"UsableIntoBuildingBlocked": false,
"UsableOutOfBuildingBlocked": false,
"UseFriends": false,
"VIPCooldowns": {
"nteleportation.vip": 10
},
"VIPCountdowns": {
"nteleportation.vip": 10
},
"VIPDailyLimits": {
"nteleportation.vip": 100
},
"VIPHomesLimits": {
"nteleportation.vip": 8
}