Death

Exactly, because saying "your players enjoy it" is no different from saying "nice plugin." But why is it nice? Why do they enjoy it? It's a small request to ask for justification of your rating. Also, we've never pressured anyone to write their review in a specific way. We only provide examples to show how you can structure your review to add meaningful context. If you were to copy that wording, we’d reject it because it demonstrates a lack of effort. We genuinely believe that if you're not willing to put effort into your review, it's better not to leave one at all. Leaving a review without context does a disservice to everyone.

Are you referring to Npc Random Raids? If so, please submit a support request https://codefling.com/plugins/npc-random-raids?tab=support

This is contradictory. Either reviews can be curated, or they can't. You're introducing a moral standard to decide which reviews should be removed and which shouldn't. Essentially, we're doing the same thing, just with different criteria. The key term here is actual, which is the focus of our moderation. Our goal is to provide the genuine experience of the reviewer. We reject reviews that are fabricated, misleading, or related to support issues that the reviewer hasn't tried to resolve. Many reviews are driven by emotion and seldom represent the true experience. Our curation process ensures that reviews offer context, are free from emotional bias. We are not the party offering the service or product itself, but a marketplace for third-party content. Therefore, we can freely moderate reviews on files within our platform. Additionally, users agree to our moderation terms when submitting reviews. We ensure our practices comply with the Consumer Review Fairness Act, as we do not prevent users from sharing honest feedback, but we may moderate to ensure reviews follow our guidelines. This may be a bit biased on your part, given the lack of reviews you've received as a creator. But I can assure you that when you wake up one morning to a 1-star rating because a user feels that you should have implemented a feature that was never promised or planned, you will think differently. This comes across as somewhat misleading. You're assuming that most of the reviews we remove are negative, but in reality, over 98% of the reviews we moderate are 4 or 5 stars. While you're focusing on negative reviews tied to unreported support issues, the majority of reviews we reject are due to a lack of context or substance. We ensure that when customers read reviews, they see ones that genuinely reflect their experience. I often hear this argument about wanting to see all reviews, but the reality is that most people don’t actually do that. You’re likely to skim past them, only focusing on the reviews that address your specific concerns. Having numerous "nice" or "works good" reviews becomes repetitive and can actually diminish the overall value of reviews.

To purchase the subscription, you must already be a creator, meaning you've uploaded a paid file and undergone some level of vetting. This means specific criteria have been met for this feature to be accessible—it's not simply a matter of paying $20 for instant access. The use of established is ambiguous to apply to cases outside of what's described. The policy clearly outlines its purpose, and a badge is prominently displayed above the purchase and download buttons, linking to the policy. It also cautions users to exercise their own discretion before proceeding, especially if a formal review hasn’t yet been made. This part of the policy is meant to clarify what it means for a file to be published but not yet approved. How a creator gained access to instant approvals is irrelevant here. What truly matters is ensuring users understand the distinction and what it implies before they choose to purchase or download the file.

Correct, but the ones winning are the customers who can access their favorite creator's latest files sooner. It was a bit unprofessional of them to share privileged information before we had the chance to announce it officially. It's still a WIP. We'll announce it officially and explain what it means once everything is ready to go!

Currently yes, but this will not always be the case, thus the broad wording in the disclaimer. In legal language, "established" can also refer to someone or something that has met certain criteria, including the formalization of a relationship (in this case, purchasing the Creator Pro subscription). The phrasing clearly states "established or trusted," which makes a distinction between the two terms. In this context, "established" can mean either being appointed or, as mentioned, purchasing the subscription. I agree it would be misleading if we only referred to "established" instead of "trusted," but by your reasoning, it would imply we are saying "trusted or trusted users," which doesn’t make much sense, does it? Ultimately, this is a legal disclaimer that most users will only glance at occasionally. The wording is intentionally broad to allow for flexibility in making changes to the service as needed, while still adhering to the original guidelines. Footnote: you can't have your own definition of a legal definition (going to assume you meant interpretation of), you stupid goose.

Thanks for letting us know. I've disabled sales on the file. I wasn't able to find any active licenses on your account for this file, so sadly, I'm unable to issue a refund. If you can provide proof of purchase, we can look into this for you.

We're now aware of the lack of updates and support and have deactivated sales.

This sounds like an issue on your end. We closely monitor the performance and have monitors in 30 different locations around the world to capture real-world user metrics.

Do you see the light bulb to the right of the navigation bar? Click that for me

This is actually being worked on. Slowly making progress on our help articles https://help.codefling.com/en/category/file-management-and-submission-1nljt2b/

I'm not sure about this one. We do not send emails out in batches. What email provider do you use?

I'll put that down as your feedback then. Make the options more visible

We do have this already, though it could be more visible.

@Chill Roleplay To clarify, should notifications intended for creators be in a different color? For example, when someone purchases your file or does anything on your file that would trigger a notification?

Are you clearing cookies? Because it does in fact remember your choice

We're always trying to make Codefling suck a little less, but we need your help. If you've got just one thing you’d like changed, added, or removed to make your experience here better, we want to hear it! Leave your idea in reply to this post, and we’ll pick 10 lucky responses at random to win a $20 gift card! If your suggestion gets implemented, you'll also snag a $50 gift card, whether or not you were one of the random winners. Now, if you're just here to roast us, fair enough—we probably deserve it. We’re ready for the good, the bad, and the brutally honest. Let’s hear it!

Ah, right, it's for the skin ID. That makes a lot of sense.

Sorry, it seemed more like a request. I can certainly see the confusion with the config accepting a value in the block list? That's odd. Perhaps @YaMang -w- could clarify this for us?

Moved this over to requests for you.

@Amino

Please join us in live chat so we can help recover your account. Thank you!

Please submit a support request here: https://codefling.com/plugins/shipwreck?tab=support and also https://codefling.com/plugins/space?tab=support

Correct, though the update will break a few plugins (as with most updates), but that's unrelated. In terms of plugins, this should be very minimal.

With the World 2.0 update coming in this wipe, it's crucial for server owners to ensure they're using maps and assets that are compatible with the latest changes. World 2.0 introduces significant modifications that might impact existing content, and we want to make the transition as smooth as possible for everyone. To simplify the process, we've added a new feature that allows creators to mark their files as World 2.0 Compatible. When browsing through the marketplace, keep an eye out for the compatibility label to make sure you're selecting files that work seamlessly with the update. You can also see compatibility information directly from your purchase dashboard. Please keep in mind that it's still early in the update cycle, and our talented level designers are hard at work updating their creations to be fully compatible with World 2.0. We expect a large number of files to be updated over the next few days, so stay tuned for more!