It's not clear what you're expecting. WIth HomeRequireFoundation off, you can set a home anywhere that isn't also restricted by proximity to monuments, caves, distance to other homes, etc. What requirement would you want to set?
Assuming you have only the default ruleset, make sure that player_npc and npc_player appears in the list of exclusions. But make sure also that the default damage is set to false (default).
Additionally, next time please create your own support thread.
If the prefabs, etc. that are part of the monument are each owned by 0, and I think they should be, that probably doesn't have any impact. I was just thinking that because of the 'some time during the month' statement.
If you made the map, perhaps some of the other map guys know about how this can be prevented for those custom prefabs. It really shouldn't be impacting them. As a workaround, I would place zones at each monument and set the NoDecay flag on those zones.
You may have allowFuelIfUnlimited set to true, which skips adding the ONE fuel since the player can add fuel. The idea was not to give them fuel on every call to /mymini, but to let them store fuel in the copter.
If you set that to false, the plugin will add one fuel to the tank so the copter will fly and not use fuel. It's probably more than confusing to have it set to true.
I'll consider the concept of spawning with fuel, but it has potential for abuse without any cost for spawning the copter.
Just to verify, make sure the rules are all lower case, e.g. player_building. I'm not sure about that plugin, but if it is free I can check into it. Otherwise, perhaps there is a hook I could call to check. Ideally, it should be that plugin that manages the damage. I can't possibly add every new plugin in here as a check as it would be TOO much to check on EVERY damage attempt, because that is the reality of how it would have to work.
This is (now being) caused by line 1587, which reads:
sphereCollider.tag = "FlyingCarpet";
You can comment it out:
//sphereCollider.tag = "FlyingCarpet";
I don't think this will cause problems.
Actually, I just saw this while porting it to a different plugin framework. The carpet spawns but this message appears in console. Will be looking into it, although it's possibly harmless.
Codefling is the largest marketplace for plugins, maps, tools, and more, making it easy for customers to discover new content and for creators to monetize their work.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.