IIIaKa

@ShiiZo Hello. Can you please try this:

Yes, those ones. In the "\data\RealPVE\BarConfig.json" and "\data\RealPVE\BarProgressConfig.json" files, you can create new settings, delete unnecessary ones, or edit existing configurations for the status bars. Don’t forget to reload the plugin after making changes. You can then use the key of any setting for any status bar, a single setting can be used by multiple status bars, even by all of them. The "_default" settings are the default configurations.

Hello. Try unloading the MonumentsWatcher plugin, then delete the file "\data\MonumentsWatcher\MonumentsBounds.json", and load the plugin back. Alternatively, you can use the console/chat command "/monument recreate all" to recreate the bounds. If that doesn’t help, and you have previously edited "DefaultBounds.json" or "CustomMonumentsBounds.json", you’ll need to delete those as well(while the plugin is unloaded), along with "MonumentsBounds.json".

Changed Status from Pending to Work in Progress

Changed Status from Pending to Work in Progress

By @Stark

Hello, as I understand it, you’re saying that all your monuments have the same image in the status bars? In the previous update, all status bar settings were moved to the files "\data\RealPVE\BarConfig.json" and "\data\RealPVE\BarProgressConfig.json" You can now configure all bars in one place and simply reference their keys in the desired status bars. This also helps reduce the size of "MonumentsConfig.json"(the monuments configuration), making it easier to navigate through those settings. For existing MonumentsConfig.json files, the keys are assigned as "_default". You can replace them with any of the keys defined in "BarConfig.json", or unload the plugin, delete "MonumentsConfig.json", and reload plugin, this will recreate the default configuration for all monuments. However, keep in mind that this will erase all your previous settings, so it’s probably better to manually replace the status bar keys instead. Note that there are two status bar keys: The first one is for regular bars(BarConfig.json) The second one is for progress bars(timers, BarProgressConfig.json)

Changed Status from Pending to Work in Progress

By @Stark

Hello. Are you sure you're using the latest downloaded version? It works just fine for me.

I can't check this myself, I haven't been able to reproduce this error. So please try replacing the OnEntitySpawned hook(lines 193–197) with this code: void OnEntitySpawned(BuildingBlock block) { if (block.OwnerID.IsSteamId() && IsRightBlock(block)) NextTick(() => { if (block.IsValid() && !block.IsDestroyed) TryInitBlockDecay(block); }); } Let me know what the result is.

@Aelanna @Aeryn Sun Hello. Does this happen every time or just occasionally? Because during this whole period, I haven’t encountered such a message even once.

Changed Status from Pending to Work in Progress

If you have anything to add, feel free to write in this thread.

Changed Status from Work in Progress to Fixed Changed Fixed In to 0.1.2

The issue turned out to be caused by a single extra space during hook generation... Thanks for reporting the bug, the funniest part is that I added that space for aesthetics after all tests

If you have anything to add, feel free to write in this thread.

Changed Status from Pending to Fixed Changed Fixed In to 0.1.22

If you have anything to add, feel free to write in this thread.

Changed Status from Pending to Fixed Changed Fixed In to 0.1.22

Changed Status from Pending to Work in Progress

Hello, try redownloading the plugin.

Hello, try redownloading the plugin.

Hello, try redownloading the plugin.