Known issues and limits

GAMPEON is in a closed test. This page lists parts that are not finished yet and bugs we already know about. If something you run into is listed here, you do not need to report it. For everything else, see Report a problem.

For the overall picture, see Platform status. Fixes show up in the changelog as soon as they ship, and we remove them from this page at the same time.

Playing

• There is no game to download yet. The desktop launcher is in early development and not available for download. Game servers and the game client come later.
• Sign-up is by invitation only. Accounts are for the closed test.

Scripting

• Lua in the game runs on internal test servers only. The game is not available for download yet. Run your resources with gampeon-server until then.
• The game API is small. Scripts can read where players are, teleport them and place simple objects (see Objects and World and entities). Only five built-in object models exist so far (prop_cube, prop_sphere, prop_cylinder, prop_cone, prop_plane). Vehicles, client-side objects and most of the world come later. Only the functions in the Lua API reference exist.
• The chat shows plain text only. HTML, colour codes like ^1 and styled templates from FiveM chat resources are removed. See Text chat.
• GTA natives do not exist and never will. A few GAMPEON functions use FiveM names, like GetEntityCoords and CreateObject, but GTA models, DrawMarker and most other GTA calls fail. This is not a bug. See Coming from FiveM.

Portal and communities

• Community messages are not real-time. New messages appear after a short delay because the portal and launcher check for them regularly. Real-time updates are planned.
• The marketplace is free. There are no payments, prices or payouts yet.

Web API and MCP

• The web API can change without notice. It is a preview. Check the changelog when something stops working.
• AI assistants sign in with an access token. Sign-in with OAuth is planned. See Connect your assistant.

Before you report

1. Check this page and the changelog. The problem may already be fixed or known.
2. Reload the page or restart the app and try again.
3. Still broken? Report it.