Death

Please clear your browser. This is a chromium issue we're trying to navigate around. Sorry about that @Patpend

Correction, we have identified an issue on our end and have rolled out a fix. Apologies about that.

I'm not able to reproduce any issues on our end. I was able to checkout just fine for chest stacks using your account. Here's your checkout URL https://codefling.com/checkout/68946/

This issue was resolved earlier today. Please download the latest version here: https://codefling.com/carbon/download

Thanks for reaching out. It does appear to have been an issue on our end that has been fixed. Sorry for the delay!

Thanks for reaching out. I've approved your pending transactions! We process payments automatically. However, suspicious activity, such as multiple failed payment attempts, using multiple payment methods at once, etc., will flag your account for manual reviews for 90 days.

I'll get you started by helping you with your first problem. You want to create a new file in your server/cfg folder and name it server.cfg then add the relationshipmanager.maxteamsize 1 to it and save. Now the server will apply this on startup. You can add as many convars to this file as you'd like. One per line.

I imagine if you put in a request and not be an asshat about it you'd be better off 👀

Yes, you will need to uninstall Oxide. To do that, delete all of the oxide.dll's from the managed folder and run validate to overwrite the assembly.dll. You can copy and paste all of your oxide folders and files into Carbon as we've opted to use the same name convention to ensure a seamless switch. The only thing you need to rename is config folder to configs. If you need additional assistance be sure to reach out to us on Discord! discord.gg/carbonmod

Last update: The billing requirement for the new PayPal API was indeed a fluke and has been resolved. Because of this we dropped the requirement. You can manage or remove billing information at https://codefling.com/clients/addresses/ as it's no longer required.

We've identified the issues causing the error at checkout for PayPal. It seems to be an issue with the API requiring billing information which shouldn't be the case. We're awaiting confirmation on this but in the meantime we've added the proper fields for personal information to get PayPal transactions working again. You'll be prompted to provide this information the next time you checkout. Alternatively, you can go ahead and add this information at https://codefling.com/clients/addresses/ as well as manage and delete said information at your discretion.

We're aware and have confirmed it's an issue on our end after updating to the latest PayPal API to make checking out more seamless. There's a few lingering issues we're trying to resolve. I'll reply here once it's is. In the meantime please use the other payment methods we offer in the meantime. We have Google, Apply Pay, Credit/Debit Card or Alipay.

Clear your browser cache. Chromium-based browsers tend to cache static files. We're working on a fix on our end.

What email are you referring to?

Please submit a support request on the file's page so the author can assist you! https://codefling.com/plugins/fuel-pump?tab=support

The first link I provided is to our private web ticket system. We do not use email for support, or for anything for that matter.

I've already answered that 😛

You can submit a web ticket at https://codefling.com/support or visit https://codefling.com/help/ for all of our support options.

No, we will not allow Carbon DRM to be implemented into Oxide plugins. Though bear in mind oxide has plans for its own DRM.

No, what he's saying is that the majority of the plugins you paid for don't allow for editing anyways. So regardless if the author chooses to use DRM, you shouldn't modify files without the author's permission.

No, DRM usually doesn't involve plugins phoning home. It's done once when the plugin is loaded, and that's it. As for editing the plugin, that's up to the license provided by the author. Paid plugins typically don't allow modification, even for personal use, to minimize the support overlap. But yes, this would prevent you from editing plugins. You'll want to communicate with the author to implement changes instead, which is why you should do either way, IMO.

Is this on purpose? I went to disable it and the server would not start back up without it being in my plugins folder.