Dynamic Monuments 1.0.2

When running /respawnmonuments I get the messages repeatedly. in the console

(17:11:46) | Calling hook CanStackItem resulted in a conflict between the following plugins: Profiler - False (Boolean), StackModifier (True (Boolean))

(17:11:46) | Calling hook CanStackItem resulted in a conflict between the following plugins: Profiler - False (Boolean), StackModifier (True (Boolean))

(17:11:46) | Calling hook CanStackItem resulted in a conflict between the following plugins: Profiler - False (Boolean), StackModifier (True (Boolean))

(17:11:46) | Calling hook CanStackItem resulted in a conflict between the following plugins: Profiler - False (Boolean), StackModifier (True (Boolean))

(17:11:46) | Calling hook CanStackItem resulted in a conflict between the following plugins: Profiler - False (Boolean), StackModifier (True (Boolean))

(17:11:46) | Calling hook CanStackItem resulted in a conflict between the following plugins: Profiler - False (Boolean), StackModifier (True (Boolean))

(17:11:46) | Calling hook CanStackItem resulted in a conflict between the following plugins: Profiler - False (Boolean), StackModifier (True (Boolean))

(17:11:46) | Calling hook CanStackItem resulted in a conflict between the following plugins: Profiler - False (Boolean), StackModifier (True (Boolean))

(17:11:46) | Calling hook CanStackItem resulted in a conflict between the following plugins: Profiler - False (Boolean), StackModifier (True (Boolean))

(17:11:46) | Calling hook CanStackItem resulted in a conflict between the following plugins: Profiler - False (Boolean), StackModifier (True (Boolean))

(17:11:46) | Calling hook CanStackItem resulted in a conflict between the following plugins: Profiler - False (Boolean), StackModifier (True (Boolean))

(17:11:46) | Calling hook CanStackItem resulted in a conflict between the following plugins: Profiler - False (Boolean), StackModifier (True (Boolean))

Just FYI Stack modifier is not compatible with a lot of plugins. I'm using stacks and have had 0 issues since.  If properly loaded the Dynamic Monuments works as planned. Restart the server after loading.

The config file is set as follows:

"Allow the Loot Table Stacksize GUI plugin to spawn items in this crate": true,

My server does not have any normal routes and everything is managed with the "Loot Table Stacksize GUI plugin",
but with the above settings all the boxes are empty.
Please fix this.

I am also seeing "some" boxes empty while using alphaloot. 
The oil platform is really noticable.

Update, actually seem to populate boxes now, corpses does not drop loot tho still 20 min in.

This type of monument has a warped top of the submarine, and if you stand on it, you will die. I'm also curious about the fish swimming around it. It's beautiful, but...

5 hours ago, hid333 said:

This type of monument has a warped top of the submarine, and if you stand on it, you will die. I'm also curious about the fish swimming around it. It's beautiful, but...

I like the idea here, loving the barges! Are these monuments as bad as some of the build sites where entities are smashed together and overall quality is garbage?

Is there an option to set a min/max for specific presents that are present on the map? For example, if I did not want more than 1 Pier to exist, could I limit that? I know there's a min/max for total locations, but I haven't seen an option for maximizing individual presents.

When using Alpha Loot is this setting supposed to be my Alpha Loot loot table name ? :

"The name of the loot preset for AlphaLoot": "",

If not that then what would go here ?

Your AlphaLoot Loottable has settings for different prefabs, npcs etc.

like those

They are considered a preset.

if you put "crate_normal_2" it will spawn the loot from that container profile.

You can even add presets that are not used for standard stuff of the game.

technically you can create specific presets for all adem events

Has anyone done the card room on the Broken Giant monument ? Players could not sort it so I just tried all three cards and could not open the door so figure I might be missing something.

This plugin was not ready for prime time. It is pretty hard core beta. I don't have a problem with that if I know up front I will be a beta tester. With what I have seen of both Gruber's and Adem's polished work I am optimistic this plugin will get sorted but for me, I have to uninstall it because every time I turn around there is a different issue.