Death

@Raul-Sorin Sorban

@Raul-Sorin Sorban

@Raul-Sorin Sorban

@Raul-Sorin Sorban

@Raul-Sorin Sorban

@Raul-Sorin Sorban

@Raul-Sorin Sorban

@Raul-Sorin Sorban

@Raul-Sorin Sorban

No, I'm shitting all over your evident personal affliction with our review process. I appreciate the feedback, but that's not what you're doing here. You're trying to contradict anyone who speaks positively about something you dislike. You're now having a spitting match with someone who is likely in the top 10% of users with the most reviews and telling them they're least qualified to have an opinion on them lol

Someone with 22 reviews will have much more insight into the process than most people. I don't get your fixation on negative reviews. You're assuming everyone is going to have a bad experience, but that's just not the case. You can argue about how you think reviews should be all you want, but it's not going to change anything. Our system works and is favored by both customers and creators. We even did a poll where the entire community voted in favor of our current system. As I said before, you're going to find yourself in the minority here.

This doesn't make any sense. If, for example, we capped the fee to 30 cents for something that costs $1, we'd lose money? PayPal transaction fee alone is 0.49 cents

@Cobalt Studios

The issue was resolved via live chat.

https://codefling.com/?do=bulkSale

@Bubbafett Ah yeah I was way off. Not sure what's wrong with that one but thanks for bringing it to our attention.

They are suggestions. So make a suggestion in the appropriate channel as mentioned numerous times. This has nothing to do with your rating but the fact that's the premise of the review. It's not that complicated. We aren't going to let you abuse reviews to facilitate feature requests. Correct, you cannot leave a review based on a suggestion or support issue for which you made no effort to reach out to the author for. So I ask again, why would you rather leave a bad review about something you'd like to see improved instead of just contacting the author? That doesn't make any sense at all.

Got a screenshot of what you mean? Perhaps I'm referring to the wrong thing

This is planned, but I'm not sure if the count would be separate for the two. I think a better solution is to perhaps show the support request but not allow it to be clickable so you know it exists. I'm not entirely sure how we'd approach that, but I don't really think this is really an issue. Have you encountered this? I'm a bit confused.

By negative or critical, do you mean leaving a review based on a support issue you made no effort to reach out for support on? Why are you generalizing it as just negative and critical reviews? You're being questionably dishonest with your responses. You've cherry-picked things I've said to victimize yourself with and have managed to personally insult me 2 times within the span of an hour. You clearly don't take criticism very well yourself. You still think you're in the right despite the amount of time I've dedicated here, providing you with all the information you need to understand how reviews are moderated. You're choosing to play ignorant, and I don't understand why. The personal attacks end here, or I'll begin enforcing our terms of service.

Support requests being private is not that common and are usually done for the sake of concealing sensitive information. Reporting exploits, sharing customer/purchase data, etc. The option needs to be there for when you need it.

Yeah, sorry, I don't know how else to help you. You're intentionally skimming over all of the information I've provided, trying to find anything and everything to become a victim here. Your review is not going to be approved because the review consists of complaints/suggestions/support issues that were not reported. Either follow the appropriate steps or stop leaving reviews.

Your latest review: Default attire (scientists instead of traditional "zombies") can be confusing or immersion-breaking. - Not mentioned in the support request. The default loadout (double-barrel shotgun) can lead to player frustration and rage quits. - Not mentioned in the support request. Everything else seems to be addressed by the author: https://codefling.com/files/support/16814-zombies-not-spawning/ As you've said yourself, you've had other reviews approved with no issue, which means it's not a problem with our process but rather the context of your review. Just like the one above, you're going after it for suggestions and issues you never brought to the attention of the author. The ones you did submit a support request for seem to be resolved. This is not how you communicate suggestions and is likely why your previous review was rejected.

There’s no contradiction here. Your analogy isn’t an apples-to-apples comparison, and I pointed that out in case the suggestion was for an expected feature (e.g., a kill feed showing deaths from drowning), which aligns with your fridge light analogy since both are reasonable expectations based on the product’s nature. Reviews are evaluated on a case-by-case basis, and in your example, a review could be justified. However, that doesn’t mean all reviews based on suggestions should be approved. Your argument is a bit misleading. This policy has been in place since the start and was supported by a community vote. While your feedback is certainly valid, it's worth noting that your stance is in the minority. Even the reviews you've just recently posted highlight issues and suggestions you made no effort to create a support request for or discuss in the appropriate channels. The definition of insanity is doing the same thing over and over again, expecting a different outcome.

So, according to your reasoning, instead of notifying the author through the proper channels and giving them a chance to address the issue, you should just post an extensive review that took more effort than submitting a simple support request? Your claim that this is misleading to customers is completely unfounded. The support tab is one of the primary places users check to see if a file has active support. It absolutely is. You're taking advantage of them by putting pressure on the rating of their file to get what you want. That's abuse. Instead, you should use the discussion tab (or even submit a support request) to propose new features. If your suggestions are declined, so be it. Those features were never guaranteed to you in the first place. A light on the door is generally an expected feature of a fridge and would constitute a design flaw or a shortcoming for it. I completely understand a review in this case, but that's just it. It's not the case. You can't make this comparison to a plugin when you want a feature that was never promised. If it's a kill feed plugin that doesn't show deaths from drowning then sure, I could see a valid review for that. It's all based on context, which is why we moderate reviews. Reviews should be used to assess products based on what they promise and deliver. Criticizing a product for lacking features it never advertised shifts the purpose of reviews away from objective evaluation and toward personal preferences, which can be misleading to other potential users. If users want to suggest new features or highlight areas for improvement, the appropriate way to do so is through feedback channels like support or discussion tabs. This maintains fairness and constructive dialogue, supporting both creators and users without distorting the product's reputation.