Death

Ah, I can certainly understand the confusion there. Glad it's all cleared up!

Could you elaborate on the part that confuses you?

This is not needed as we can easily see if they've created a support request or not, which is a requirement for warranty refunds. No point in adding an extra step for customers when we can look it up on our end.

Since introducing the standard warranty on all purchases, we've covered hundreds in damages from abandoned or discontinued files for our customers. Now, we've made the process even easier by adding a dedicated claims center to quickly submit refund requests for applicable purchases. We hope this will alleviate the strain from our main support channels while also providing faster responses by having a dedicated claims team. You can initiate the process directly from the claims center, though it's recommended to do so from your purchase dashboard, as we're able to prefill much of the required fields for you. We expect responses within 24 hours, but please bear with us as we improve the process as we go!

Great idea. We'll be releasing an optional DLC you can purchase to unlock this feature.

Fixed. Sorry about that.

Ah I see. I recommend having a look at https://codefling.com/services/ if you find no luck here. Be careful with who you entrust with your ideas.

This seems very vague. What do you mean by voting? Like a poll? Not a lot to work on here.

https://help.codefling.com/en/article/how-to-delete-your-account-ef4ws5/

This was done with Headphones plugin so I imagine what you're after is very much possible. You'd just run into issues if the client has audio streams disabled. You could reach out to the author of the plugin mentioned or check out the services page to find a developer for the project.

You could also request a refund with the author directly. At this point they'd be the only one who could authorize one. We can only step in if it's against SLA or covered under warranty. Since they responded to you very quickly with a proposed solution there's no way for us to issue the refund on our end without the authors approval.

The author mentioned they would fill in these holes with rocks. If you're concerned with how they approach this you're free to leave a review.

We'll need an actual support request from you first. Also, to be fair to the author there what they're saying is 100% true. Rivers are indeed bugged in RustEdit and have been for a long time now.

Before we can even consider a refund, you'll need to submit a support request on the file's page to give the author a chance to resolve any issues you might have.

One week to go! It's not too late to join in on the giveaways at https://discord.gg/codefling. Event ends on July 31st!

We have no rule against multiple accounts. If your other account was banned it was likely for something else. Please reach out https://codefling.com/help

Glad we were able to get this resolved for you

Font companies got real quiet after this dropped

These plugins will have to be updated. Why does this affect anything posted above?

Right, but these plugins shouldn't be unlocking DLC content anymore, and if they were (for say a creative or test server) none of the above is relevant.

You originally said plugins like this are modifying the blueprint data, which would be modifying the ItemDefinition. But based on that code they aren't, so how would this affect CheckSkinOwnership??

Doesn't sound like a problem to anyone but the developer of that plugin. I also don't see why it would need to modify the ItemDefinition just to unlock a blueprint? lol playerInfo.unlockedItems.Add(bp.itemid); player.ClientRPCPlayer(null, player, "UnlockedBlueprint", bp.itemid); player.stats.Add("blueprint_studied", 1);

I sure hope not. That plugin overcomplicates something that is extremely simple. I'm struggling to see the value in it at all. It does absolutely nothing besides expensive api calls. For developers: If you want to see if a user owns a skin: player.blueprints.CheckSkinOwnership(skinItemId, player.userID) If you want to see if a user owns DLC: item.info.steamDlc.HasLicense(player.userID) If you want to see if an item requires a DLC: item.info.NeedsSteamDLC If for whatever reason you need the full list of approved skins: foreach (var skin in Approved.All) { var itemName = skin.Value.Skinnable.ItemName; var skinId = skin.Value.WorkshopdId; // etc... It's a Dictionary<ulong, ApprovedSkinInfo> } Furthermore, you can go pretty deep with skins and see if they're tradable and marketable. There may be some skins Facepunch makes an exception for that aren't obtainable via monetary means. ApprovedSkinInfo.Tradable ApprovedSkinInfo.Marketable That's it. That's all you need. If I'm missing something let me know and I'll add it.

No. These plugins can still be used on creative and test servers. They also include config settings to disable approved skins which you can already do. Any plugin that does not can easily check if the player owns the item first so I don't expect many plugins to be affected by this.