FluxDash

A Fluxer bot for Geometry Dash lovers! Still very much a WIP, contributions are appreciated!

Unofficial successor to f's GDStats bot (RIP, thanks f my goat)

The bot part of FluxDash was made with fluxer-rs. The GD part of FluxDash was made with gdutils, which I started because of this bot!

The official instance is being hosted by benjae#6963. thanks oomf <3. Auth link to add the bot to a community

Check for issues, PRs, etc in Codeberg @ https://codeberg.org/JuxGD/FluxDash and in GitHub @ https://github.org/JuxGD/FluxDash

AI, Agents, LLMs

Please refer to llms.txt, llms-full.txt, AGENTS.md or CLAUDE.md, and CONTRIBUTING.md. Don't look at the README anymore. Go on check the files I said

To-do list / What to help with

Current (or future) bot features:

• Getting arbitrary level data (gd!level)
  • Name
  • ID
  • Author
  • Level length
  • Song ID
  • Song artist - song name (Newgrounds/Music Library)
  • Difficulty rating
  • "Quality" status (normal, featured, epic etc) and feature score (the higher that is, the higher in the featured tab the level is)
  • Stars/Moons
  • Coins (and if verified)
  • Likes
  • Downloads
  • Work with level name (searches and returns data for most popular)
• Getting timely level info (gd!daily, gd!weekly, gd!event)
  • Index (i.e. daily level number)
  • Time Left (not for event levels)
  • Actual level info (like with gd!level)
• Getting arbitrary user data (gd!user)
  • Username
  • Account ID
  • Player ID
  • Leaderboard placement
  • Stars
  • Moons
  • Amount of levels of each difficulty beaten
  • User Coins
  • Secret Coins
  • Diamonds
  • Demons
    • Amount of levels of each demon difficulty beaten
  • Creator Points
  • Work with username
• Sending message to arbitrary channel when level was recently rated, or rated level difficulty changes

Side quests

• AREDL integration

• Pointercrate integration

• Pemonlist integration

• The Shitty List/TSL+ integration

• Geometry Dash Demon Ladder integration

• Geometry Dash Demon Progression integration

• Global Stats Viewer integration

• Updated Leaderboard integration

• Unrated Demon List integration

• Insane Demon List integration

• Hard Demon List integration

• Song File Hub integration

• For demons (gd!level)

  • AREDL spot (Extreme only)
  • Pointercrate spot (Classic Extreme only)
  • Plist spot (Platformer only)
  • GDDL Tier (Classic Extreme only)
  • GDDP Tier (Classic Extreme only, if applicable to level)
  • IDL spot (Insane only)
  • HDL spot (Hard only)

• For users (gd!user)

  • Updated Leaderboard integration

• Sending message to arbitrary channel when new Geode release

• Sending message to arbitrary channel when new Geometry Dash update

• Geometry Dash login maybe? Idk what we'd do with that though

Private Servers

FluxDash uses gdutils, which is meant to work with the official Geometry Dash servers. To use the bot with private servers, a dedicated FluxDash instance is needed. Clone the gdutils repo, modify src/constants.rs to work with that server's URL, and build FluxDash with the custom gdutils as a dependency.

Building

This repository provides an .envrc and a Nix flake. By doing direnv allow with Nix and direnv installed, one can get a basically exact replica of the development environment used. For this to work, Nix's "flakes" and "nix-command" features have to be enabled.

Once with a working dev environment, FluxDash can be built with cargo build

Running

FluxDash is available as a crate. Install it:

cargo install fluxdash

After that, it can be ran with:

~/.cargo/bin/fluxdash

FluxDash can also be ran in the dev environment:

cargo run

Alternatively, after building, the binary will be in the repo directory:

./target/debug/fluxdash

---

Provide the FLUXER_BOT_TOKEN environment variable. This corresponds to the string shown in Fluxer Application settings when the "Regenerate" button near to the "Bot token" text field is clicked.

If running with cargo run, one can also put a .env file at the root of the project directory, with export FLUXER_BOT_TOKEN="<bot_token>" in it, where <bot_token> is the token.

To automatically boot the bot back up if (when) it crashes, run the bot as a service (eg a systemd or openrc service on Linux). Make sure to configure the service so that it restarts FluxDash in the event of a crash, and that it stays running if the user the service is running on disconnects or logs out.