@blazium-games/skills 0.1.14 → 0.1.16
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/GROK.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
How Grok should load these skills. Same files as Claude, Cursor, and Codex. No invented marketplace schema.
|
|
4
4
|
|
|
5
|
-
These skills are for the
|
|
5
|
+
These skills are for the game publishing platform at [blazium.games](https://blazium.games). They are not the Blazium engine skills.
|
|
6
6
|
|
|
7
7
|
Read [SKILL_TREE.md](SKILL_TREE.md) for which skill to use. The guide is [docs.blazium.games](https://docs.blazium.games), and the short map is [llms.txt](https://docs.blazium.games/llms.txt). Do not invent platform behavior that those pages do not describe.
|
|
8
8
|
|
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Blazium Games skills
|
|
2
2
|
|
|
3
|
-
Agent skills for [Blazium Games](https://blazium.games),
|
|
3
|
+
Agent skills for [Blazium Games](https://blazium.games), a game publishing platform, with an infrastructure focus, operated by Divine Games, Inc. They are not the engine skills at [`@blazium-engine/skills`](https://www.npmjs.com/package/@blazium-engine/skills), and they do not install Hub or the engine.
|
|
4
4
|
|
|
5
5
|
## Install
|
|
6
6
|
|
package/SKILL_TREE.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Blazium Games skill tree
|
|
2
2
|
|
|
3
|
-
Blazium Games is
|
|
3
|
+
Blazium Games is a game publishing platform, with an infrastructure focus. A token belongs to one server: `blazium-games` (developer, `https://mcp.blazium.games/mcp`, keys `bgames_mcp_`) publishes pages, builds, crashes, analytics, and keys. `blazium-games-player` (player, `https://mcp.blazium.games/player`, keys `bgames_play_`) finds, reviews, installs, and buys.
|
|
4
4
|
|
|
5
5
|
The guide is [docs.blazium.games](https://docs.blazium.games). This file is the skill index. The docs site remains the source for how the platform works.
|
|
6
6
|
|
package/package.json
CHANGED
|
@@ -1,12 +1,12 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: blazium-games-get-started
|
|
3
|
-
description: Connect Cursor to Blazium Games and route to the right skill. Blazium Games is
|
|
3
|
+
description: Connect Cursor to Blazium Games and route to the right skill. Blazium Games is a game publishing platform, with an infrastructure focus. The developer server (mcp.blazium.games/mcp) publishes pages, builds, crashes, analytics, and keys. The player server (mcp.blazium.games/player) finds, reviews, installs, and buys. Use when the user mentions Blazium Games for the first time, asks how to connect, or is unsure whether they want to play or publish.
|
|
4
4
|
license: MIT
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# Blazium Games: Get Started
|
|
8
8
|
|
|
9
|
-
Blazium Games is
|
|
9
|
+
Blazium Games is a game publishing platform, with an infrastructure focus. A token belongs to one server:
|
|
10
10
|
|
|
11
11
|
- Developer server `https://mcp.blazium.games/mcp` (`blazium-games`, keys `bgames_mcp_`): pages, builds, crashes, analytics, and keys. Needs developer mode.
|
|
12
12
|
- Player server `https://mcp.blazium.games/player` (`blazium-games-player`, keys `bgames_play_`): find, review, install, and buy. Works for every account.
|
|
@@ -72,6 +72,10 @@ Redeemable game keys are not credentials; they give players a copy of the game.
|
|
|
72
72
|
|
|
73
73
|
If the user approved the connection with **Read-only access**, the token only has `mcp:read`. Rotation tools then fail with HTTP 403, code 4031 ("This token is read-only"). Ask the user to reconnect without the read-only option, or to rotate on the website. A token from a narrower preset without `mcp:keys.manage` gets `4073`; reconnect with the **Keys** or **Full access** preset.
|
|
74
74
|
|
|
75
|
+
## Mint keys
|
|
76
|
+
|
|
77
|
+
A mint key is a 128-character secret for one game. `request_mint_key` returns it once. It can mint items and, for a named player, set stats, socket, unsocket, and use. It cannot edit the catalog, turn Steam on, or sell. Players and the game client cannot do those actions. `mcp:keys.manage` covers mint keys. `mcp:catalog.write` does not.
|
|
78
|
+
|
|
75
79
|
## Docs
|
|
76
80
|
|
|
77
81
|
- https://docs.blazium.games/docs/mcp/access-and-keys
|
|
@@ -9,3 +9,5 @@ license: MIT
|
|
|
9
9
|
Other Godot engines vendor `addons/blazium_games/`. Auth is the login websocket only. The addon never loads the official DLL. After the JWT arrives, `BlaziumLobby` and `BlaziumIce` use that token. Set project setting `blazium/game/game_uid`.
|
|
10
10
|
|
|
11
11
|
Inside a Discord activity, the addon sends API, login, and lobby traffic through `{applicationId}.discordsays.com`. Unity and Unreal do not.
|
|
12
|
+
|
|
13
|
+
`transfer_item` can move the signed-in player's items to Steam when that game allows it. `socket_item`, `unsocket_item`, `set_item_stats`, and `use_item` fail locally. Those actions belong to the game owner, an accepted admin, or a mint key on the owner's server, never a player session.
|