🚨 License Troubleshooting

This page explains common EventForge license messages and how to fix them.

info

EventForge uses BuiltByBit buyer information to validate official downloads and help prevent unauthorised redistribution.

This copy was not downloaded through BuiltByBit

Message:

[EventForge] [License] This copy was not downloaded through BuiltByBit.

This usually means the file was built locally or downloaded somewhere outside BuiltByBit.

Common causes:

• the jar was uploaded manually instead of downloaded through BuiltByBit
• BuiltByBit placeholders were not replaced
• the file came from an unofficial source

Buyer ID was not replaced

Message:

[EventForge] [License] license.buyer-id was not replaced by BuiltByBit.

This means this placeholder was not replaced:

buyer-id: "%%__USER__%%"

Common causes:

• the jar was not downloaded through BuiltByBit
• anti-piracy placeholders were not processed
• the file was modified after download
• the config was edited incorrectly

warning

make sure the resource is downloaded through BuiltByBit.

Timestamp was not replaced

Message:

[EventForge] [License] license.timestamp was not replaced by BuiltByBit.

This means this placeholder was not replaced:

timestamp: "%%__TIMESTAMP__%%"

Fix:

• download the plugin through BuiltByBit
• check that the placeholder exists exactly as expected
• do not rename or edit the placeholder before upload

Nonce was not replaced

Message:

[EventForge] [License] license.nonce was not replaced by BuiltByBit.

This means this placeholder was not replaced:

nonce: "%%__NONCE__%%"

The nonce is used as part of BuiltByBit license validation.

Fix:

• make sure the file was downloaded through BuiltByBit
• make sure the placeholder is not edited incorrectly

BuiltByBit rejected the license validation request

Message:

[EventForge] [License] BuiltByBit rejected the license validation request.

Possible causes:

• invalid shared token
• token type is not Shared
• token does not allow V1 endpoints
• resource ID is wrong
• nonce/timestamp validation failed
• BuiltByBit rejected the request

Check:

license:
  resource-id: YOUR_REAL_RESOURCE_ID

And make sure the plugin was built with a valid BuiltByBit Shared token.

No BuiltByBit license found for this buyer

Message:

[EventForge] [License] No BuiltByBit license found for this buyer.

This means BuiltByBit did not find a matching license for the buyer and resource.

Possible causes:

• wrong resource ID
• copied/leaked jar
• buyer does not own the resource
• placeholders belong to a different resource
• file was redistributed from another account

Fix:

• download EventForge from the official BuiltByBit resource page
• verify the buyer account owns the resource
• check the configured resource ID

BuiltByBit returned HTTP 429

Message:

[EventForge] [License] BuiltByBit rate limited the license validation request.

This means too many requests were made to BuiltByBit in a short time.

EventForge uses cache settings to reduce repeated validation.

If a valid cache exists, EventForge can continue using cached validation.

BuiltByBit API unreachable

Message examples:

[EventForge] [License] Could not contact BuiltByBit
[EventForge] [License] BuiltByBit returned HTTP 500.
[EventForge] [License] BuiltByBit validation was interrupted.

This means EventForge could not complete online validation.

Possible causes:

• BuiltByBit API outage
• server has no internet access
• firewall blocks outgoing requests
• DNS issue
• temporary network issue

If a valid cached license exists, EventForge can continue using it during the grace period.

Using cached license validation

Message:

[EventForge] [License] BuiltByBit product licensed to: BuyerName (BuyerId) [cached]

This means EventForge is using a previously successful validation.

This is normal when:

• the cache is still fresh
• BuiltByBit is temporarily unreachable
• EventForge is avoiding unnecessary API calls

What is cache-hours?

cache-hours controls how long EventForge can use a fresh successful validation before trying to validate online again.

Example:

license:
  cache-hours: 24

This means EventForge can reuse a successful validation for 24 hours before checking again.

What is grace-days?

grace-days controls how long EventForge can continue using an older valid cache if BuiltByBit is unreachable.

Example:

license:
  grace-days: 3

This means a previously validated license can continue to run for up to 3 days during API/network issues.

EventForge may disable itself when validation fails and no valid cached license is available.

Do not edit buyer placeholders manually

Do not manually replace these values:

%%__USER__%%
%%__USERNAME__%%
%%__TIMESTAMP__%%
%%__NONCE__%%

BuiltByBit should replace them when the buyer downloads the resource.

Manual edits can break validation.

Do not share your downloaded jar

Your downloaded jar may contain buyer-identifying information.

Do not share:

EventForge.jar
modified EventForge.jar
license-patched EventForge.jar
cracked EventForge.jar

If the file is leaked, the license information may help identify where it came from.

If you bought EventForge but validation fails

Try:

1. Download EventForge again from BuiltByBit.
2. Make sure you are using the official jar.
3. Do not use a jar from Discord, a friend, or another website.
4. Check that your server can access the internet.
5. Check console for the exact license message.
6. Contact support from the BuiltByBit account that purchased EventForge.

If you are using a cracked or leaked copy

Cracked, leaked, modified, or redistributed copies are not supported.

They may be:

• unsafe
• outdated
• modified
• missing files
• blocked from support
• traceable to the original buyer

Use the official BuiltByBit resource page to get a legitimate license.

Summary

Most license issues come from one of these causes:

• local build
• missing resource ID
• file not downloaded through BuiltByBit
• placeholders not replaced
• invalid shared token
• BuiltByBit API/network issue
• leaked or modified jar