dhosty

Discord & community · 6 min read

Plan Discord Bot Runtime at dhosty

For the duration of a discord bot, you have to separate test access, paid package and extension. dhosty has a separate bot test over 14 days; this is not the same process as booking a paid package. Check in the customer area which performance is active and which end is displayed.](/discord-bot-hosting/) This overview helps you to plan connections, responsibilities and the transition to the ongoing community operation.

Differentiating test access and paid package

The bot test offered has its own limited runtime. It serves to get to know the managed bot environment and its operation. Such a test is not a commitment that any additional resources or other product types are provided free of charge. Check whether your customer account can still use the test and what is displayed in the specific process as contained.

The end of the test is not equivalent to a paid contract renewal. If you want to use a paid offer afterwards, check the appropriate package and the necessary steps. Plan this decision in time. A bot already added to your Discord server does not prove on its own that its hosting runtime is still active or that the desired connection order has already been completed.

Check the actual status in the customer area

Start with the specific bot performance in the customer area. Note the name of the instance, the displayed status and the associated runtime. In this case, distinguish between a stored order, a technical provision and a actually started bot. These states may require various next steps. A pure login in the panel does not extend either a test or an already running performance.

If several people are in charge of the community, a responsible person should keep an eye on this information. Document which bot belongs to which Discord server and which application is used for it. Avoid parallel, conflicting orders from multiple team members. In case of a query, instance name and process reference help; secret tokens or passwords are not required in a general message.

Separate balances and concrete payment

A deposit and payment of a particular service are different steps. After checking an actual payment receipt, credits may be available in the customer area. However, this does not follow that every open order or renewal is automatically paid. Check the corresponding process and the confirmation displayed there, instead of assuming the general balance alone.

Before you confirm a payment, check the selected service and the price reference. Keep an displayed reference for queries. Then compare the booking status with the status of the bot service. If this information does not fit together, a targeted inquiry is more useful than an immediate second payment. Further information on the process is available in the [Help Center].](/hilfe/).

Treat the extension as your own process

Before the end of the run, check which extension is intended for your active performance. The specific display and the confirmed booking are decisive. A fixed package duration is not an unlimited continuing test. Nor should it be derived from a general capacity check that an additional period has already been booked without your further decision.

For a clean planning, you determine who is preparing the extension and who is controlling the completion. Note the affected bot and the desired next period. After a confirmed booking, you check the updated runtime again. If an advertisement remains unclear, clarify it before further changes. A repeated order is not a reliable replacement for checking an already existing process.

View Discord connection and hosting separately

Even when hosting runs are active, the bot must be connected to the correct Discord application and added to the desired server. A bot token and an OAuth client secret perform different tasks. Do not confuse these values and do not publish them in the chat. Check the actual application stored and the permissions granted on the server in case of connection problems.

A reactive login via Discord does not automatically prove that each bot function is available on a server. Conversely, a missing bot on Discord is not necessarily a runtime problem. Check hosting status, connection status and server permissions separately. Do not change all settings at the same time: With individually documented steps, it can be seen which change has fixed or triggered a problem.

Do not confuse managed bot with a VPS

The managed bot offer is maintained via its intended panel functions. Depending on the booked scope, this includes commands, greetings, roles and the control of the instance. From this, no general claim to root access to a separate Linux system can be derived. If you want to run your own software on a self-managed server, you have to check this request separately.

This distinction is also important for runtime planning. An additional VPS project and a managed bot are not automatically the same performance or the same order. Therefore, compare not only the name of a package, but the specific administrative scope. Note which configuration you are responsible for and which operation the selected offer actually provides. Thus, you avoid false expectations in the future expansion of the community.

Documenting the transition for your team

Create a short inventory before the end of a test. Which commands are used, which role actions are set up and who is allowed to make changes? Document the settings to the extent reasonable and separate this information from secret keys. Determine which configuration must be maintained when switching and which functions you want to check again before regular use.

Inform the responsible team members about the scheduled time of a change. Test the most important commands with a controlled process and check the display in the panel. For later queries, date, instance name and confirmed process reference are particularly helpful. Thus, the support remains comprehensible, even if the person who started the test initially does not take over every future extension himself.

Frequently asked questions

Is the bot test simply a paid package?

No. The separate test is a time-limited entry and is treated separately from a paid booking. Check in the customer area, which status and the end are displayed for your specific performance. A package that is desired then requires the corresponding order steps.

Does a deposit automatically pay my bot extension?

A deposit will initially provide funds after verification. Then check whether the specific extension has been selected and confirmed. An existing credit and a completed performance process are different information; keep the respective reference for possible queries.

Why is the bot not visible on Discord despite active runtime?

In addition to the hosting runtime, connection, application and server permissions must be correct. Check whether exactly this bot has been added to the intended Discord server. An OAuth login is not a substitute for the bot's server access. Check the individual points separately instead of changing the entire configuration at the same time.

Which data are included in a question for the duration?

Name the instance concerned, the displayed status, the time and the existing order or payment reference. Also, describe whether you mean a test, a new booking or an extension. Passwords, bot tokens and private keys do not belong in a general support message.

More hosting topics