Viority Development
DiscordShop
  • 🏠Home
    • Welcome
    • FAQ
    • Common issues
  • Tutorials
    • βš™οΈProduct
      • How to get the Security Token?
      • How to create new locales?
      • getSharedObject Deprecated
  • 🀝Support
    • Support Policy
    • πŸ‡ΊπŸ‡ΈTicket Rules (EN)
    • πŸ‡©πŸ‡ͺTicket Rules (GER)
  • Products
    • πŸ”’Viority Script Lock
      • How to use
      • JavaScript example
      • Lua example
    • πŸ“‹Viority Advanced Menu
      • πŸ‘€Config Preview
      • Event Command
      • NotifyBoard
      • OpenMenu Event
      • CloseMenu Event
      • UpdateChallengeProgress
      • UpdateAchievementProgress
      • CheckAchievementProgress
      • CheckCurrentLevel
    • 🚘Viority Garage V2
      • πŸ‘€Config Preview
      • OpenGarage Event
      • CloseGarage Event
      • VehicleParkIn
      • VehicleParkIn DV
    • πŸš—Viority Cardealer
      • πŸ‘€Config Preview
      • Vehicle Color Fix
      • OpenCardealer Event
      • CloseCardealer Event
      • UpdateLeasingStatus
      • CheckPlate
      • CheckPlateBlacklist
      • GeneratePlate
    • β›½Viority Gasoline
      • πŸ‘€Config Preview
      • OpenGasoline Event
      • CloseGasoline Event
      • RefillFuelStock
      • GetFuel
      • SetFuel
    • πŸ’³Viority Billingmenu
      • πŸ‘€Config Preview
      • OpenBillingMenu Event
      • CloseBillingMenu Event
    • πŸ’Viority Marry
      • Page
      • πŸ‘€Config Preview
      • StartAnimation Event
      • StopAnimation Event
    • πŸ“ŠViority HUD
      • πŸ‘€Config Preview
        • PMA-Voice Example
        • Saltychat Example
      • Announce Command
      • TriggerNotifySystem
      • UpdateWantedStars
      • UpdateTransactionData
      • UpdateCurrentMission
      • GetWantedStars
    • πŸ•Viority Playtime Rewards
      • πŸ‘€Config Preview
      • ClosePlaytimeReward
      • OpenPlaytimeReward
      • CheckCurrentLevel
    • 🀝Viority Interaction
      • πŸ‘€Config Preview
      • ESX Interaction Integration
      • How to use
    • πŸ†”Viority SupportID
      • πŸ‘€Config Preview
      • getNearestPlayerID
      • getPlayerID
    • πŸ“Viority Register
      • πŸ‘€Config Preview
      • getAllPromocodes
      • getPlayerPromocode
    • 🏒Viority Fraction Request
      • πŸ‘€Config Preview
    • 🌐Viority LifeInvader
      • πŸ‘€Config Preview
    • πŸ””Viority LifeInvader Notify
      • πŸ‘€Config Preview
      • Notify
    • πŸͺ™Viority Trading
      • πŸ‘€Config Preview
      • OpenTradingMenu Event
      • CloseTradingMenu Event
  • πŸ“ŒDiscord Server
Powered by GitBook
On this page
  • 1. Interaction and resistance:
  • 2. Cooperativeness:
  • 3. Quick response time:
  • 4. Cooperativeness:
  • 5. Conditions:
  1. Support

Ticket Rules (EN)

πŸ“‚ All rules about the ticket system

1. Interaction and resistance:

  1. We treat all customers and users of our service with respect and professionalism.

  2. We do not tolerate discriminatory, offensive, or abusive behavior towards other customers or users of our service.

  3. We reserve the right to remove any users who engage in these behaviors from our Service.

2. Cooperativeness:

  1. We strive to help every customer and user of our service as much as possible.

  2. We will do our best to answer and solve questions and problems quickly and efficiently.

  3. We expect a helpful and solution-oriented way of working, on the other hand we are forced to terminate the support relationship with immediate effect.

  4. We reserve the right, however, to prioritize requests or issues based on urgency or complexity.

Please always remember that you are not the only customer who needs help!

3. Quick response time:

  1. We strive to respond to all support tickets within 24 hours.

  2. During peak times or for particularly complex requests, it may take longer to respond, depending on the nature of the request.

4. Cooperativeness:

  1. We expect a cooperative attitude from our customers and users in resolving any issues or requests.

  2. We ask that all relevant information be provided to help us diagnose and resolve problems.

5. Conditions:

  1. We assume that your server is fully configured correctly, from the FiveM artifact (internal game files), the database (working MySQL instance), the framework (e.g. ESX) to scripting requirements such as esx_status, food and drink management.

  2. As a reference, we always use the preconfigured default server provided by the framework in the version you are using. If the submitted error does not occur, it means that a resource you changed or added is causing the error. In this case, we will help you find the cause, but it is your server and your responsibility. We are not obligated to fix the resources you changed. Out of kindness, we will do our best to help you find a solution in a competent and cooperative approach, but only as long as our team's time allows.

We would like to point out that our support service is a voluntary service. We are not obligated to handle or fix server data or other technical problems that are not caused by us. However, we will do our best to help solve problems if it is within our capabilities.

We hope that these rules clarify how our support service works and what we expect from our customers and users. Please feel free to contact us if you have any further questions or concerns.

PreviousSupport PolicyNextTicket Rules (GER)

Last updated 5 months ago

🀝
πŸ‡ΊπŸ‡Έ