You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that my issue may get closed without notice if I intentionally remove or skip any mandatory* field
This is NOT a bug/crash report
I've searched the bugtracker for similar questions/requests including closed ones
Description
Through NpBot Cost. hire configuration parameter hiring NPCBOT, NpcBot will be charged every 10 minutes The rental hourly wage set by the Cost. Rent parameter.
If the current player's bag does not have enough coins to pay for every 10 minutes of hourly wage, how does the system handle the hired NPCBOT?
Can a warning function be provided for players with insufficient gold coins, and when the warning of unpaid wages accumulates to a certain number of times, dismissal will be executed?
Is it also possible to return the weapons and equipment allocated to players through email when firing?
TrinityCore or AzerothCore
Both
Core rev. hash/commit
AzerothCore-wotlk-with-NPCBots 0355ccf 2024-12-17
Operating system
Ubuntu 22.04
The text was updated successfully, but these errors were encountered:
DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
Description
Through NpBot Cost. hire configuration parameter hiring NPCBOT, NpcBot will be charged every 10 minutes The rental hourly wage set by the Cost. Rent parameter.
If the current player's bag does not have enough coins to pay for every 10 minutes of hourly wage, how does the system handle the hired NPCBOT?
Can a warning function be provided for players with insufficient gold coins, and when the warning of unpaid wages accumulates to a certain number of times, dismissal will be executed?
Is it also possible to return the weapons and equipment allocated to players through email when firing?
TrinityCore or AzerothCore
Both
Core rev. hash/commit
AzerothCore-wotlk-with-NPCBots 0355ccf 2024-12-17
Operating system
Ubuntu 22.04
The text was updated successfully, but these errors were encountered: