Dream Services Documentation

website·Indexed 32 days ago

https://docs.dream-services.eu

Technical documentation and configuration guides for Dream Services products, including Dream Wind Turbines, Dream Cryptomining, Dream Vending, Dream Solarjob, Dream Junkyard, and other server scripts. Includes installation instructions, Lua configuration details for DreamCore, server-side exports, and a knowledge base for troubleshooting Lua errors.

Tokens
30.6K
Snippets
143
Records
181
Agent score
55%

What's inside Dream Services

  1. Understand support eligibility for Dream Services

    Support is exclusively available to customers who purchased items directly from the official Dream Services store. Assistance is not provided for items acquired via transfers, as the team cannot verify the authenticity or integrity of transferred items. For issues related to transfers, users should contact FiveM's official support.
  2. Install Dream SecretDealer

    To install Dream SecretDealer, follow these steps:

    1. Download the script from the CFX Portal and place it in your server's resources directory.
    2. Install the required dependency: ox_lib (available on GitHub).
    3. Configure the DreamCore.lua and DreamCoreExt.lua files.
    4. Execute the provided SQL script for your specific framework in your database. Ensure that tables are created with their defined values.
    5. Add the script to your server startup configuration.

    Critical Warning: Do not rename your framework folder or modify the bridge system, as this will break the installation.

    ensure dream_secretdealer
  3. Identify modifiable files in Dream Services scripts

    To avoid breaking script integrity or violating escrow protections, follow these modification guidelines:

    Safe to modify:

    • Configuration files (e.g., DreamCore.lua)
    • Locale and translation files
    • Framework bridges (e.g., ESX, QBCore)

    Not permitted/Risky:

    • Escrowed code files (cannot be edited or decrypted)
    • Core logic files (e.g., main.lua) - modifications are at the user's own risk
  4. Install Dream Crypto Mining script

    To install the Dream Crypto Mining script, follow these steps:

    1. Place the downloaded script from Keymaster into your server's resources directory.
    2. Configure the main settings in DreamCore.lua.
    3. Configure the webhook settings in Webhooks.lua.
    4. Execute the provided SQL file corresponding to your framework in your database. Ensure that tables are created with their defined values.
    5. Add the script to your server startup configuration.

    Important: Do not rename your framework folder or modify the bridge system settings, as this may break the installation.

    ensure dream_cryptomining
  5. Install the dream_smoking resource

    To install the dream_smoking resource, follow these steps:

    1. Download the script from Keymaster and place it into your server's resources directory.
    2. Configure the DreamCore.lua file to select your preferred UI library.
    3. Add ensure dream_smoking to your server.cfg file to start the script on server boot.
    ensure dream_smoking
  6. Requirements for purchasing Dream Services scripts

    To ensure scripts are correctly delivered and licensed, you must use the same FiveM account for both the Tebex store login and the Keymaster account used to generate your server license key. Purchases are linked directly to the FiveM account.
  7. Fix collation errors by adjusting specific tables or columns

    If you cannot unify the entire database, you can fix collation mismatches by targeting specific affected tables or columns:

    1. Drop or alter the affected tables.
    2. Modify the SQL schema to use a consistent collation (either utf8mb4_unicode_ci or utf8mb4_general_ci).
    3. Recreate or migrate the data.
  8. Create a custom language locale for Dream scripts

    To add a new language translation to Dream scripts, follow these steps:

    1. Create the locale file: Navigate to the /settings/locales folder. Copy an existing locale file (e.g., en.lua) and rename it using the official language code (e.g., de.lua for German, fr.lua for French).
    2. Update the identifier: Open the new file and update the DreamLocales table key to match your language code.
    3. Translate values: Translate the text values on the right side of each line.

    Critical Constraints:

    • Do not change the keys (the strings on the left side of the assignment).
    • Preserve formatting: Keep special characters and placeholders intact (e.g., ~INPUT_CONTEXT~, ~r~, %s).
    -- Example for German (de.lua)
    DreamLocales['de'] = {
        ["open_menu"] = "Menü öffnen", -- ✅ Correct: only value is translated
    }
  9. Install Dream Junkyard script

    To install Dream Junkyard, follow these steps:

    1. Place the script downloaded from Keymaster into your server's resources directory.
    2. Install the required dependency scripts into the resources directory: ox_lib and glow_minigames.
    3. Configure the DreamCore.lua and DreamCoreExt.lua files.
    4. Execute the provided SQL script corresponding to your framework in your database. Ensure that tables are created with their defined values.
    5. Add the script to your server startup configuration.
    ensure dream_junkyard
  10. Set up Informants and their requirements

    Informants are configured in DreamCore.Informants. Each informant can have a specific model, coordinates, a blip (which can be hidden unless the player has a specific item), and a prop.

    Crucially, you can define requirements that players must meet to interact with the secret dealer. Requirements can be based on:

    • Weapons: Points awarded based on specific weapon ownership.
    • Items: Points awarded based on specific item ownership.
    • Tuncion XP: Points awarded based on the player's level (if TuncionXP integration is active).
    DreamCore.InformantsCooldown = 60000 -- Time in ms for the informant cooldown
    DreamCore.Informants = {
        [1] = {
            name = 'Tony',
            model = 'csb_ballasog',
            coords = vector4(128.8308, -1945.3152, 21.15, 45.5087),
            blip = {
                show = false, 
                item = 'bigt_note', -- Only show when the player has this item
                sprite = 280, scale = 0.8, color = 5
            },
            requirements = {
                neededRequirementPoints = 60,
                possibleRequirements = {
                    { type = 'weapon', stages = { { weapon = 'WEAPON_PISTOL', points = 5 } } },
                    { type = 'item', stages = { { item = 'weed', points = 5 } } },
                    { type = 'tuncion_xp', stages = { { minLevel = 2, points = 10 } } }
                }
            }
        }
    }
  11. Install dream_windturbines script

    To install the dream_windturbines script, follow these steps:

    1. Place the script downloaded from Keymaster into your server's resources directory.
    2. Install the required dependency: ox_lib (available on GitHub).
    3. Configure the DreamCore.lua and DreamCoreExt.lua configuration files.
    4. Execute the provided SQL script for your specific framework in your database. Ensure that tables are created with their defined values.
    5. Add the script to your server startup configuration.

    Critical Warning: Do not rename your framework folder or modify the bridge system settings, as this may break the installation.

    ensure dream_windturbines
  12. Understand Dream Services support expectations and behavior rules

    Dream Services maintains a professional support environment with the following guidelines:

    • Behavior: Discriminatory, offensive, or abusive behavior is not tolerated and may result in removal from the service.
    • Response Times: The team strives to respond to all support tickets within 24 hours, though complex requests or peak times may cause delays.
    • Cooperation: Users are expected to maintain a helpful, solution-oriented attitude and provide all relevant information necessary to diagnose and resolve problems.
    • Prioritization: Support requests may be prioritized based on urgency or complexity.