> For the complete documentation index, see [llms.txt](https://gameluk.gitbook.io/gameluk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gameluk.gitbook.io/gameluk/develop/get-started/gameid.md).

# GameID

This guide assumes that the necessary dependencies have been installed. To interact with the Gameluk blockchain, the GameID command-line tool should be used. To install GameID, please select the appropriate version from this link and execute the following commands:

git clone <https://github.com/GameLuk/gameluk-core> cd gameluk-chain git checkout $RELEASE make install

```
// git clone https://github.com/GameLuk/gameluk-core
cd Gameluk-chain
git checkout $RELEASE
make install
```

You can verify that `GAMEID` was installed properly by running

```
// $ GameID version
3.3.3
```

{% hint style="info" %}
If you see an error like `command not found: GameID` then you may need to set your GOPATH environment variable.\
\
1\. Use `go env GOPATH` to find your GOPATH\
2\. add &#x20;

```
export GOPATH=[your GOPATH from step 1]
export PATH=$PATH:$GOPATH/bin
```

to your \~/.bashrc
{% endhint %}

GameID supports general Cosmos SDK and Tendermint commands. You can run the tool to see a list of commands with explanations of what they do:

```
// Start Gameluk app

Usage:
  GameID [command]

Available Commands:
  add-genesis-account      Add a genesis account to genesis.json
  add-wasm-genesis-message Wasm genesis subcommands
  collect-gentxs           Collect genesis txs and output a genesis.json file
  config                   Create or query an application CLI configuration file
  debug                    Tool for helping with debugging your application
  export                   Export state to JSON
  gentx                    Generate a genesis tx carrying a self delegation
  help                     Help about any command
  init                     Initialize private validator, p2p, genesis, and application configuration files
  keys                     Manage your application's keys
  migrate                  Migrate genesis to a specified target version
  query                    Querying subcommands
  rollback                 rollback cosmos-sdk and tendermint state by one height
  start                    Run the full node
  status                   Query remote node for status
  tendermint               Tendermint subcommands
  tx                       Transactions subcommands
  validate-genesis         validates the genesis file at the default location or at the location passed as an arg
  version                  Print the application binary version information

Flags:
  -h, --help                help for gameid
      --home string         directory for config and data (default "/root/.sei")
      --log_format string   The logging format (json|plain) (default "plain")
      --log_level string    The logging level (trace|debug|info|warn|error|fatal|panic) (default "info")
      --trace               print out full stack trace on errors

Use "gameid [command] --help" for more information about a command.
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gameluk.gitbook.io/gameluk/develop/get-started/gameid.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.