Question Content Vs Content Access

I see "content access" is for threads.

You can also charge users for specific text in a thread (using the money icon on the toolbar), but what is the use of this event...


A user can enter any amount of credits to be charged when they click the money icon in the editor toolbar, not restricted.

Hi,

The "Content" event is what enables the [CHARGE=X] tag to work. Anything within those tags will cost X currency to unlock.

The "Content Access" event is used to pay to unlock access to the entire thread.

Thank you for that.

On the "Content" event, even if I set the "Flat Rate" to 10, whatever number the user sets in [Charge=X] still applies.

E.g. I set flat rate to 10. The user enters [CHARGE=1], so the total charged should be 11 credits?

It says alongside flat rate - "Extra amount added to the amount being transferred". That's how I get that impression?

I guess I'm expecting that if the admin sets up the "content" event, it overrides or alters the users CHARGE=X amount the user inputs?

Sorry for the confusion, new to this.

Unfortunately that’s a side effect of events using a common configuration UI. It would be confusing to users to have the number they enter differ from what’s actually being charged.

Hello @Captain Morgan,

We hope your ticket regarding DragonByte Credits has been addressed to your satisfaction. This ticket has now been scheduled to be closed.

If your ticket has not been resolved, you can reply to this thread at any point in the next 7 days in order to reopen the ticket, afterwards this thread will be closed.

Please do not reply to this thread if your ticket has been resolved.

Thank you.


- DragonByte Technologies, Ltd.

Hello @Captain Morgan,

As we have not heard back from you, your ticket regarding DragonByte Credits has now been closed.

If your ticket has not been resolved, please feel free to start a new support ticket and link back to this ticket.

If you have time, please leave a review on XenForo.com's Resource Manager.

Thank you.


- DragonByte Technologies, Ltd.