Death

Good catch. We'll release a fix asap.

We're excited to announce our huge update that reinvents how you find custom maps, as well as putting hundreds of data points at your fingertips to know everything about the map before you pull the trigger on it. You're no longer at the mercy of the author providing all of the relevant information about their map, as this is now handled automatically by Codefling to expand filtering capability and reduce the burden on authors to keep this information up to date as the map evolves. This is all possible thanks to our new map parser that automatically verifies the integrity of the map file, as well as grabs all relevant information, which allows us to automatically flag problematic maps, as well as expand upon your ability to filter out maps. From map size, monuments, buildable area, biome percentage, down to how many lakes, tunnels, and rails, you can now find the perfect map that fits your server! Additionally, when viewing a map, you'll see a quick overview at the top of the description that provides a comprehensive breakdown of the map's contents.

The author said they'd fix it soon. That's the only update I have for now.

The plugin does not have this functionality, but it's something I could consider in a future update.

@0xDEADBEEF

Correct, we reached out to the author. I'm not entirely sure what else we could do. It's free, so we can't disable sales, and it works for Carbon, so disabling downloads is also out of the question, and we cannot modify the file due to licensing restrictions imposed by the author.

@Bear Grills What do you recommend we do exactly?

Any update on this @FireCrow?

Considering neither you nor I even know what file they're referring to, and the fact that they still haven't submitted a support request, likely not.

Yeah that's fair. We don't have any record of reviews during that time. In any case, this is no longer an issue and we hope you give it another chat.

Our review feed has been public for over a year now. You can easily debunk this claim by heading over to our Discord and checking out #reviews, which details all reviews accepted or declined, and the reason for it. I don't see any from you, but that could mean the reviews in question were posted before the feed became public.

Yes, this is caused by elevators. The RustEdit extension needs an update. It's outdated.

This is a RustEdit bug unrelated to the monument. You'll need to wait for an update for the extension.

If you're having issues with a file please submit a support request in the support tab on the file's page.

Thanks, this is on our radar.

We’ve updated our review policy to make the feedback process more open, transparent, and now completely community-driven. Reviews will still undergo an initial check to ensure they are appropriate and in line with our terms of service. Beyond this, we will no longer evaluate the authenticity of user experiences beyond what is outlined in our disclaimer. Starting today, the community has taken control of all reviews to improve transparency and fairness. You get to decide what you deem appropriate feedback or not, rather than at the whim of our moderation team. While we worked extremely hard to be transparent and ensure quality reviews, we completely understand that it wasn't a good look. You can mark a review as helpful or unhelpful to increase or decrease the signal from each review. Once a review becomes overwhelmingly unhelpful, it will no longer contribute to the review's rating, but will still be visible, positioned slightly out of sight to avoid occupying screen real estate from helpful reviews. This can go either way, so we'll be actively monitoring review voting activity to ensure the integrity of our new review system and prevent it from being used in an inappropriate way to influence or invalidate reviews, such as coordinated attacks from malicious users or creators trying to boost their ratings. As with everything, we will hope for the best and adjust accordingly. If you have any feedback or questions about these changes, please don't hesitate to ask them here. We're very interested to know what your take is. To read the updated disclaimer, check out https://codefling.com/disclaimer/

@Mr01sam

Added at the bottom. Sorry for the delay!

@kasvoton

@Nogard

@TF Crazy

@FastBurst can we get an update on this?

Were you able to find a solution @HolaHi?

Oof, that's not the kind of wait times we were hoping for. We are still inventing our processes as we go, and grossly underestimated the volume of requests we'd get. The problem is people aren't requesting refunds within the scope of our warranty, so it's taking a bit for us to sift through. This is being improved, and I apologize for the delay.

I'll add it. Just didn't think there'd be enough content to show.