Dynmap looked crazzy now in 8.0.0[BUG]

[CloudeLecaw]

The settings in config seems not to not reaci to the dynmap.. in result the dynma look a bit crazy

[Blueeyestar]

I can only confirm this. I was able to duplicate this error. Even on a newly generated RedProtect folder. It is not possible to disable makers or the boxes with the names. You can't even change the name marker namen RedProtect. No matter what you write, the name RedProtect always remains

# Group name to show on hide/show tab map.
        marks-groupname=Zone
        min-zoom=0
        # Show icons under regions.
        show-icon=false
        # Show names under regions.
        show-label=false
        # Show leaders and admins on hover?
        show-leaders-admins=true

[FabioZumbi12]

@CloudeLecaw i don't know whats exactly its wrong just looking to your map. What's you trying and whats redprotect is not doing? @Blueeyestar i think i got it.

[CloudeLecaw]

With Version 8 this "million home markers and the ownernames where set and seen but they should not be there.

Also we defined the world Zonen for the marker list what is now shown as Redprtect 8 as "RedProtect". Even if we change it it in a fresh version 8 config we get this crazzy look result (see screenshot from first post) in Version 8 the filled color seems to miss and all zones got these markers with there owners names that should not be there...

Here u see the player Zones, and Server Zones filled with the right color + the right color for outdated player zones. (This is how its shown correctly in Version 7.7.3 Build 413)

normaly you also just should see the infos if u click in the region like seen here

Here is a hasebin of our config that we use in 7.7.3-Build 413 https://www.toptal.com/developers/hastebin/unoxikagag.coffeescript

current used version of server: [22:36:39 INFO]: This server is running Paper version git-Paper-42 (MC: 1.19) (Implementing API version 1.19-R0.1-SNAPSHOT) (Git: c029645)

[CloudeLecaw]

any updateds here?

We really wanne update to version 8.0.0...

[Blueeyestar]

It's nice that there's an update for 1.19.2 since October 22, 2022, but RedProtect is still not usable with the dynmap. Apparently you don't understand where the problem lies or is it so defective with the update that you can't fix it anymore?

Unfortunately, the RedProtect can no longer be used since 8.0.0 if you also use the dynmap.

[CloudeLecaw]

any updateds here?

We really wanne update to version 8.0.0...

we tested Build #417 today...the issue with the dynmap still exists.. we want the map back looking like this (build 413) . . .

and NOT like this (build 417)

[Blueeyestar]

It probably doesn't interest anyone that there are problems and errors....

[Blueeyestar]

too bad even with Build #418 the garbage is still not fixed.....why is there an update if the problem remains the same....very very very unfortunate...

[Blueeyestar]

Since unfortunately no answer came from the developer, I had to start solving the problem myself. So I came up with the idea of looking for the dynmap files from an old working RP version. I then exchanged these for the defective files in the current RedProtect-8.0.0-SNAPSHOT-b418-Universal. And then the dynmap works again in RP as you are used to

Old dynmap version RedProtect_7.7.3-Build413:

New broken dynmap version RedProtect-8.0.0-SNAPSHOT-b418-Universal:

You can download the RedProtect-8.0.0-SNAPSHOT-b418-Universal with working Dynmap here: RedProtect-8.0.0.SNAPSHOT-b418-Universal.zip

As you can see, 2 dynmap .class files are missing in the new RP version. These were added from the old one. Then the dynmap worked again in the 8.0.0 version

The dynmap is now running in the new version. But there is still a bug in the version that was reported in June 2022. Therefore, this is not recommended because this bug is very annoying.

https://github.com/FabioZumbi12/RedProtect/issues/820

That's why I've adapted the working RP version: RedProtect_7.7.3-Build413 to 1.19 and added the mobs and animal heads so that they don't have a placeholder in the menu. The version also works perfectly in Minecraft version 1.19.4.

RedProtect_7.7.3-Build413.zip

We'll keep looking to fix some issues but would be really grateful if FabioZumbi12 gets active again and also fixes the "Enter Region in chat in Redprotect https://github.com/FabioZumbi12/RedProtect/issues/820" issue as we don't yet know which file is causing this issue.

[aurel85]

Thanks you so much !!! I confirm that it works very well :)

[CloudeLecaw]

If you want the Addoons Killer Projectiles and RentRegion for 7.7.3 here they are. i sendet them to you here, because on the Redprotect Github you only get the once for Version 8 anymore. Dont ask me for other Addons of it for 7.7.3 i have no others because we didnt used the others. Redprotect_7.7.3-Addons_KillerProjectilesAndRentRegion.zip

[FabioZumbi12]

Hi. Try this version. Its a 8.1.0 created directly from the last 7.7.3 but with all latest changes except changes on configurations, and added an option:

# Convert all regions with minY = 0 to the world min y? Fix existing regions not protecting below 0 on 1.19+!
convert-zeros-y=true

RedProtect-8.1.0-SNAPSHOT-Spigot.zip

[Blueeyestar]

Hi. Try this version. Its a 8.1.0 created directly from the last 7.7.3 but with all latest changes except changes on configurations, and added an option:

# Convert all regions with minY = 0 to the world min y? Fix existing regions not protecting below 0 on 1.19+!
convert-zeros-y=true

RedProtect-8.1.0-SNAPSHOT-Spigot.zip

Is this a trailing April Fool's joke? You throw out a new RedProtect version 8.1.0 without correcting the serious bugs in the version? Instead, are they continued?

Did you actually take a look at this thread? Neither the Dynmap problem https://github.com/FabioZumbi12/RedProtect/issues/821 I solved here nor the Enter Region in chat problem https://github.com/FabioZumbi12/RedProtect/issues/820 have been fixed. The 8.1.0 is not usable!!!!

[CloudeLecaw]

well that really was a bit disapointed.. im not sure why the version 8.1. was made when its results in the same issue as before. cant you simply use the 7.7.3 versions and do the snaller changes on this working on?

[FabioZumbi12]

Since unfortunately no answer came from the developer, I had to start solving the problem myself. So I came up with the idea of looking for the dynmap files from an old working RP version. I then exchanged these for the defective files in the current RedProtect-8.0.0-SNAPSHOT-b418-Universal. And then the dynmap works again in RP as you are used to

Old dynmap version RedProtect_7.7.3-Build413:

New broken dynmap version RedProtect-8.0.0-SNAPSHOT-b418-Universal:

You can download the RedProtect-8.0.0-SNAPSHOT-b418-Universal with working Dynmap here: RedProtect-8.0.0.SNAPSHOT-b418-Universal.zip

As you can see, 2 dynmap .class files are missing in the new RP version. These were added from the old one. Then the dynmap worked again in the 8.0.0 version

The dynmap is now running in the new version. But there is still a bug in the version that was reported in June 2022. Therefore, this is not recommended because this bug is very annoying.

820

That's why I've adapted the working RP version: RedProtect_7.7.3-Build413 to 1.19 and added the mobs and animal heads so that they don't have a placeholder in the menu. The version also works perfectly in Minecraft version 1.19.4.

RedProtect_7.7.3-Build413.zip

We'll keep looking to fix some issues but would be really grateful if FabioZumbi12 gets active again and also fixes the "Enter Region in chat in Redprotect #820" issue as we don't yet know which file is causing this issue.

Yeah, this version is based on the last 7.7.3 that you used to build this version. Instead to continue the 8.0.0 i just jumped from 7.7.3-Build413 to 8.1.0. with the last bugfixes present here: https://github.com/FabioZumbi12/RedProtect/compare/master-legacy1.18...RedProtect-8.0.0

I got the 8.0.0 updated a lot of things related to configuration and bugged a lot of things like dynmap and redprotect configs too. Running here locally with 8.1.0 i didnt got the issues i got on 8.0.0

[Blueeyestar]

Since unfortunately no answer came from the developer, I had to start solving the problem myself. So I came up with the idea of looking for the dynmap files from an old working RP version. I then exchanged these for the defective files in the current RedProtect-8.0.0-SNAPSHOT-b418-Universal. And then the dynmap works again in RP as you are used to Old dynmap version RedProtect_7.7.3-Build413: New broken dynmap version RedProtect-8.0.0-SNAPSHOT-b418-Universal: You can download the RedProtect-8.0.0-SNAPSHOT-b418-Universal with working Dynmap here: RedProtect-8.0.0.SNAPSHOT-b418-Universal.zip As you can see, 2 dynmap .class files are missing in the new RP version. These were added from the old one. Then the dynmap worked again in the 8.0.0 version The dynmap is now running in the new version. But there is still a bug in the version that was reported in June 2022. Therefore, this is not recommended because this bug is very annoying.

820

That's why I've adapted the working RP version: RedProtect_7.7.3-Build413 to 1.19 and added the mobs and animal heads so that they don't have a placeholder in the menu. The version also works perfectly in Minecraft version 1.19.4. RedProtect_7.7.3-Build413.zip We'll keep looking to fix some issues but would be really grateful if FabioZumbi12 gets active again and also fixes the "Enter Region in chat in Redprotect #820" issue as we don't yet know which file is causing this issue.

Yeah, this version is based on the last 7.7.3 that you used to build this version. Instead to continue the 8.0.0 i just jumped from 7.7.3-Build413 to 8.1.0. with the last bugfixes present here: master-legacy1.18...RedProtect-8.0.0

I got the 8.0.0 updated a lot of things related to configuration and bugged a lot of things like dynmap and redprotect configs too. Running here locally with 8.1.0 i didnt got the issues i got on 8.0.0

Are you sure that you also took the RedProtect_7.7.3-Build413.zip and not accidentally the 8.0.0?

Because I just set up a server from scratch. And then Red Protect installed from scratch.

Unfortunately, the errors that are present in the 8.0.0 version are still the same!!!

You can use Show messages on enter, exit and welcome messages. it doesn't matter how you change it. RP always uses chat function.

It is still not adopted if you change the map name in the config: Group name to show on hide/show tab map

No matter which name you choose, it always remains Redprotect.

You can't even turn the maker on and off in this version.

The dynmap is still defective in appearance.

The problem is the same as in the 8.0.0 version.

if you took the RedProtect_7.7.3-Build413 why are there only 4 dynmap files in the 8.10 version?

In the RedProtect_7.7.3-Build413 there are 6 dynmap files. The dynmap only works if the other 2 files are included.

But these are missing in the 8.1.0 version just like in the 8.0.0 version

[FabioZumbi12]

Whats the paths of that 2 other classes? Here on dev side, i have only one class called DynmapHook.class. Maybe the problem is on build way or similar. As example:

[FabioZumbi12]

My God, i got that my IDE its trolling me. Checkout this version:

RedProtect-8.1.0-SNAPSHOT-Spigot.zip

[Blueeyestar]

My God, i got that my IDE its trolling me. Checkout this version:

Congratulations now works the 8.1.0

https://github.com/FabioZumbi12/RedProtect/issues/820

https://github.com/FabioZumbi12/RedProtect/issues/821

have been fixed and are working properly again

great job :)

[Blueeyestar]

It is best to upload the working version here http://host.areaz12server.net.br:8081/job/RedProtect/

and with Spigot so that everyone downloads the working version and not the next one comes and says it doesn't work

[CloudeLecaw]

if you update the new 8.1.0 pls dont forget to also update the Addons @FabioZumbi12 <3 :§ i know it a bit out of theme :3

[22:11:37] [Server thread/ERROR]: Error occurred while enabling KillerProjectiles v8.0.0-SNAPSHOT (Is it up to date?)
java.lang.NoSuchMethodError: 'void br.net.fabiozumbi12.RedProtect.Bukkit.API.RedProtectAPI.addFlag(java.lang.String, boolean, boolean)'
    at br.net.fabiozumbi12.killerprojectiles.KillerProjectiles.onEnable(KillerProjectiles.java:53) ~[RedProtect_8.0.0-Build418-RPKillerProjectiles.jar:?]
    at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:279) ~[paper-api-1.19.4-R0.1-SNAPSHOT.jar:?]
    at io.papermc.paper.plugin.manager.PaperPluginInstanceManager.enablePlugin(PaperPluginInstanceManager.java:189) ~[paper-1.19.4.jar:git-Paper-503]
    at io.papermc.paper.plugin.manager.PaperPluginManagerImpl.enablePlugin(PaperPluginManagerImpl.java:104) ~[paper-1.19.4.jar:git-Paper-503]
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:507) ~[paper-api-1.19.4-R0.1-SNAPSHOT.jar:?]
    at org.bukkit.craftbukkit.v1_19_R3.CraftServer.enablePlugin(CraftServer.java:555) ~[paper-1.19.4.jar:git-Paper-503]
    at org.bukkit.craftbukkit.v1_19_R3.CraftServer.enablePlugins(CraftServer.java:466) ~[paper-1.19.4.jar:git-Paper-503]
    at net.minecraft.server.MinecraftServer.loadWorld0(MinecraftServer.java:638) ~[paper-1.19.4.jar:git-Paper-503]
    at net.minecraft.server.MinecraftServer.loadLevel(MinecraftServer.java:437) ~[paper-1.19.4.jar:git-Paper-503]
    at net.minecraft.server.dedicated.DedicatedServer.initServer(DedicatedServer.java:308) ~[paper-1.19.4.jar:git-Paper-503]
    at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1104) ~[paper-1.19.4.jar:git-Paper-503]
    at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:320) ~[paper-1.19.4.jar:git-Paper-503]
    at java.lang.Thread.run(Thread.java:1623) ~[?:?]
[22:11:37] [Server thread/INFO]: [KillerProjectiles] Disabling KillerProjectiles v8.0.0-SNAPSHOT
[22:11:37] [Server thread/ERROR]: Error occurred (in the plugin loader) while disabling KillerProjectiles v8.0.0-SNAPSHOT (Is it up to date?)
java.lang.NoSuchMethodError: 'void br.net.fabiozumbi12.RedProtect.Bukkit.API.RedProtectAPI.removeFlag(java.lang.String, boolean)'
    at br.net.fabiozumbi12.killerprojectiles.KillerProjectiles.onDisable(KillerProjectiles.java:77) ~[RedProtect_8.0.0-Build418-RPKillerProjectiles.jar:?]
    at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:281) ~[paper-api-1.19.4-R0.1-SNAPSHOT.jar:?]
    at io.papermc.paper.plugin.manager.PaperPluginInstanceManager.disablePlugin(PaperPluginInstanceManager.java:224) ~[paper-1.19.4.jar:git-Paper-503]
    at io.papermc.paper.plugin.manager.PaperPluginManagerImpl.disablePlugin(PaperPluginManagerImpl.java:109) ~[paper-1.19.4.jar:git-Paper-503]
    at org.bukkit.plugin.SimplePluginManager.disablePlugin(SimplePluginManager.java:537) ~[paper-api-1.19.4-R0.1-SNAPSHOT.jar:?]
    at io.papermc.paper.plugin.manager.PaperPluginInstanceManager.enablePlugin(PaperPluginInstanceManager.java:193) ~[paper-1.19.4.jar:git-Paper-503]
    at io.papermc.paper.plugin.manager.PaperPluginManagerImpl.enablePlugin(PaperPluginManagerImpl.java:104) ~[paper-1.19.4.jar:git-Paper-503]
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:507) ~[paper-api-1.19.4-R0.1-SNAPSHOT.jar:?]
    at org.bukkit.craftbukkit.v1_19_R3.CraftServer.enablePlugin(CraftServer.java:555) ~[paper-1.19.4.jar:git-Paper-503]
    at org.bukkit.craftbukkit.v1_19_R3.CraftServer.enablePlugins(CraftServer.java:466) ~[paper-1.19.4.jar:git-Paper-503]
    at net.minecraft.server.MinecraftServer.loadWorld0(MinecraftServer.java:638) ~[paper-1.19.4.jar:git-Paper-503]
    at net.minecraft.server.MinecraftServer.loadLevel(MinecraftServer.java:437) ~[paper-1.19.4.jar:git-Paper-503]
    at net.minecraft.server.dedicated.DedicatedServer.initServer(DedicatedServer.java:308) ~[paper-1.19.4.jar:git-Paper-503]
    at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1104) ~[paper-1.19.4.jar:git-Paper-503]
    at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:320) ~[paper-1.19.4.jar:git-Paper-503]
    at java.lang.Thread.run(Thread.java:1623) ~[?:?]

[FabioZumbi12]

The addons just here for now

RedBackups-8.1.0-SNAPSHOT.zip

[CloudeLecaw]

The Problem is solved with thie new 8.1.0 Build 419. So the issue can be closed <3 Thank you for solving this for us.