Search Results

Step 6 — Install Dependencies Some Nord Forge resources require additional FiveM resources. Examples can include: Frameworks Database libraries Inventory systems Target systems Notification systems Voice systems UI libraries Check the individual resource docum...

Step 7 — Database & SQL Some Nord Forge resources require database tables or migrations. If the resource package contains SQL files, review them before starting the resource. Example files: install.sql database.sql migration.sql Installation Import the require...

Step 8 — Configure the Resource Open the resource configuration files and configure them for your server. Depending on the product, this can include: Framework Locale Inventory Target Notifications Text UI Database Permissions Integrations Common configuration...

Step 9 — Add the Resource to server.cfg Add the resource to your FiveM startup configuration. Example: ensure nord_inventory For several Nord resources: ensure nord_inventory ensure nord_crafting ensure nord_hud Recommended order Put required dependencies bef...

Step 10 — Start & Verify Restart your FiveM server after completing the installation. You can also start the resource manually from the server console: ensure nord_inventory or: restart nord_inventory What to check Verify that: The resource starts without Lua ...

Full Installation Example This is a complete example for installing a protected Nord Forge FiveM resource. 1. Register the server in Nord Forge Register: cfxk_MY_SERVER_KEY under: Nord Forge → Servers 2. Configure server.cfg sv_licenseKey "cfxk_MY_SERVER_KEY"...

Marketplace The authenticated marketplace lists products that are ready for distribution. A product must meet all of these requirements before appearing normally: Product status is published. Store status is published. At least one published release exists. ...

Free Products Products with a price of 0 are delivered automatically. When a customer claims a free product, Nord Forge: Creates or reuses the active product license. Associates the product with the customer's Forge Key. Adds the product to My Products. Recor...

Manual Purchases Paid products using the Manual payment provider use a buyer/developer conversation flow. Customer flow Open the product. Start the purchase. A purchase conversation is created. Discuss the purchase with the seller/workspace. The workspace gran...

Tebex Purchases Products configured with the Tebex payment provider can use the Nord Forge Tebex Bridge. Checkout flow The customer starts checkout from Nord Forge. Nord Forge creates or redirects to the configured Tebex checkout. Tebex processes the payment. ...

Becoming a Developer Nord Forge uses a customer-first account model. A normal account does not automatically receive a developer workspace. When the user activates the developer flow, Nord Forge creates: A developer workspace The user as workspace Owner A stor...

Workspace Roles The current team management flow exposes the following main roles. Owner The workspace owner has full workspace control. Owner permissions include all workspace capabilities and owner-only actions. Developer Intended for product and release dev...

Workspace Lifecycle Workspaces can be active or archived. Archive Archiving keeps the workspace and its data but removes it from normal active operation. Restore An archived workspace can be restored by its owner. Delete protection A workspace cannot be delete...

Creating a Product Developers with product management permission can create products inside a workspace. New products are always created as: draft Nord Forge does not allow a new product to be published before a valid release exists. Product information A prod...

Creating Releases A release represents a downloadable version of a product. Required file Every new release requires a file. Nord Forge rejects a release without an uploaded file. Release fields A release can include: Version Changelog File Status Critical upd...

Publishing a Product A product can only be published when at least one valid published release with a file exists. If a developer tries to publish too early, Nord Forge returns: product_requires_release_before_publish Recommended publishing flow Create the pro...

Managing Existing Releases Developers can update release metadata after creation. Supported actions include: Change version Change changelog Change release status Update critical/config/database flags Update compatibility notes Replace the release file Delete ...

Protected Customer Builds Nord Forge can generate a protected customer build when a customer downloads a licensed script product. Developer download Developers/admins can use direct release downloads and receive the clean uploaded package. Customer download Fo...