ktsu.CounterStrikeProgression

Matchmaking-style ranks, weapon levels, and skill shot challenges for CS2 community servers.

Introduction

ktsu.CounterStrikeProgression is a CounterStrikeSharp plugin that gives players on a small community server a reason to play everything, not just their favourite gun. CS2 never awards Steam profile XP on community servers, so the progression lives on the server.

Players climb an up-only rank ladder from Silver I to Global Elite. Every weapon has its own level and a permanent ladder of tiered challenges. Around 50 skill shots, from jumpshots and wallbangs to flicks and efficient reloads, pay noticeably more than plain kills.

Features

• Up-only ranks: 12 matchmaking-style ranks with five stages each, from Silver · I to Global Elite · V. Numbered ranks such as Silver I to IV are one rank here, because the stages number it. The first stage takes 5,000 XP, each one after costs about 7.7% more, and Global Elite · V takes about 5 million XP in total. Nobody loses progress for a bad night.
• Weapon levels: every weapon, grenade, the knife, and the Zeus levels up to 40, and each level-up pays rank XP.
• Mastery stars: past level 40, weapon XP keeps counting toward mastery stars, one for each 40 levels' worth of XP. They're cosmetic and pay no rank XP, but they show next to the weapon on the panel, in !stats and !top, and on the site, and each one is announced.
• Chickens: every weapon has a Chickens challenge (1, 5, 15, 40, and 100 chickens), and each chicken pays 2 XP to the weapon and to rank. Twelve chicken skill shots sit on the weapon ladders too, from Nugget (headshot a chicken) and Fowl play (through a wall) to Fried chicken, Rotisserie, and Crossed the road (from long range).
• Weapon ladders: Kills, Headshots, and Hits, plus one challenge for every skill shot the weapon can earn, each with five tiers. Skill tiers pay more than volume tiers.
• Skill shots: about 50, covering movement, distance, wallbangs and smokes, scopes, utility and melee, timing and aim, multi-kills, and round situations.
• Daily and weekly contracts: three daily contracts and one weekly, such as "Get 20 kills with SMGs" or "Get 2 kills through walls", pay 500 and 2,500 rank XP. The picks come from the UTC date, so everyone gets the same ones, and they reset at midnight UTC and on Monday. !contracts opens them in the panel, and the site's player page shows your progress.
• Server records: a hall of fame of single-moment bests: the longest kill with each gun class, the longest no-scope, the most kills in one life, the best accuracy over one life (from 30 shots), and the most skill shots in one map. Beating one is announced to the server, to the site's feed, and to Discord, naming the holder it was taken from, and the site's Leaderboards page lists every record. A record has to be beaten outright, a bot never holds one, and kills and skill shots against bots don't count unless RecordsCountBots is on. RecordsEnabled turns them off.
• Bounty on the leader: the player on the longest current life streak, once it reaches 5 kills, carries a bounty worth 50 rank XP per kill in the streak. Whoever ends the streak collects it, and chat hears when a bounty is placed, every 5 kills after, and when it's collected. A bot persona carries and collects a bounty like a human (see Bot personas), and BountyStartKills and BountyXpPerKill tune it (0 turns it off).
• Bots count, at a reduced rate: rank XP against bots is scaled down, while weapon levels and ladders still move, so practice against bots isn't wasted.
• Bot personas: each bot name is a persistent player with its own rank, progress, and player page, marked as a bot everywhere it shows. Bots are tracked only while a human is on, and they're kept out of server records and the global feed. See Bot personas.
• Featured weapon of the day: one gun class (pistols, SMGs, rifles, snipers, shotguns, or machine guns) earns double weapon XP each UTC day. Challenge ladders move at the usual pace. The pick comes from the date, so the panel overview and the site's live page always agree. FeaturedWeaponMultiplier sets the multiplier, and 1 turns it off.
• Welcome-back bonus: a player back after 7 or more days away earns double rank XP until they've had 2,000 bonus XP. The join message and the panel overview say how much is left, and what's left is saved, so it carries over between visits. WelcomeBackDays sets the gap, and WelcomeBackXp the bonus, where 0 turns it off.
• Nemesis and rivals: kills between players, bot personas included, are counted per pair. Your nemesis is whoever has killed you most, at least 3 times, and killing them pays 50 bonus rank XP with a floatie. !stats names your nemesis and favourite victim, and the site's player page has a Rivals tab with every head-to-head. NemesisMinimumKills and NemesisKillXp set the numbers, where 0 XP turns the bonus off. A bot persona can be your nemesis, and a bot with no persona never counts.
• In-game panel: !rank opens a side panel to the right of the view. It falls back to a center-screen card and then to chat if a way of drawing fails.
• XP floaties: every XP gain floats up as "+XP" text from the center of your screen. Only you see your own. Quick gains add up in one floatie, and skill shots, tiers, and level-ups are named under the number in gold. A World mode floats them above the target instead.
• Daily play streak: every UTC day in a row with any rank XP adds to the streak. Each new day of a streak is told to the player in chat, and the streak shows on the panel overview and the player page. It's worked out from the daily XP rows already stored, so nothing new is saved.
• Feats: twelve really difficult feats, such as Global Elite, Millionaire, Weapon master, Full ladder, Collector, Chicken overlord, Arsenal (every gun to level 10), Polymath (a skill shot tier on 20 weapons), and Regular and Devoted for 7 and 30 day play streaks. They are worked out from the stored progress, announced to the server when earned, and shown as medallions on the progression site.
• Rank tags: everyone's rank, such as [GN III], shows as their scoreboard clan tag and before their name in chat.
• Announcements: rank-ups, finished tiers, mastery stars, and every fifth weapon level go to the whole server.
• Map recap: when the map ends, each player gets one chat line with the XP, kills and deaths, skill shots, levels, and tiers they earned, and their best moment. The recap also goes to the progression site, which shows it as "Last session" on the player page, and a player who leaves early still gets one there. AnnounceMapRecap turns the chat line off.
• Durable storage: progress is kept in MariaDB or MySQL in csp_ tables, saved off the game thread, and retried after a failed save without double counting.
• Configurable: every XP value, multiplier, and detection threshold is a setting.

Installation

1. Install Metamod:Source 2.0 and CounterStrikeSharp v1.0.376 or newer, with its .NET runtime.
2. Download CounterStrikeProgression-<version>.zip from the releases.
3. Extract it into the server's game/csgo/ directory. It contains addons/counterstrikesharp/plugins/CounterStrikeProgression/.
4. Start the server once, then edit addons/counterstrikesharp/configs/plugins/CounterStrikeProgression/CounterStrikeProgression.json.
5. Restart the server, or run css_plugins reload CounterStrikeProgression.

With no database host set, progress is kept in memory and lost when the server restarts.

Usage Examples

Player commands

Command	Effect
!rank, !xp, !progress	Open or close the progress panel
!contracts	Open the progress panel on today's contracts
!top	Print the 10 players with the most rank XP
!top <weapon>	Print the 10 players with the most XP with one weapon, such as !top ak or !top awp
!next	Print your three challenges closest to their next tier
!feats	Print every feat, with the ones you've earned and how close you are to the rest
!stats [name]	Print your rank, XP, kills, headshot share, best weapon, feats, nemesis, and favourite victim, or a connected player's
!site	Print the progression site's address

When a player first spawns, they get a welcome line with their rank, the site's address (when Site.PublicUrl is set), and the commands. "WelcomeMessage": false turns it off.

While the panel is open, W and S scroll, A and D move between the overview, the contracts, and each weapon, and R closes it. It also closes when you take damage or die.

Admin commands

All three require @css/root.

Command	Effect
css_csp_status	Print the plugin version, the store in use, how many players have loaded, and whether the match is in warmup or free-for-all
css_csp_grant <player> <xp>	Add rank XP, or take it away with a negative amount. Taking XP away also takes away the ranks it bought, and it stops at 0
css_csp_reset <player>	Delete every rank, weapon, and ladder row the player has. Run it twice within 15 seconds to confirm, because it can't be undone

<player> is #userid, part of a connected player's name, a SteamID64 or bot id, or bot:<name> for a bot persona. A SteamID64, a bot id, and bot:<name> also work for players who aren't on the server. Both corrections are written to the database straight away and logged with the admin, the player, and the XP and rank before and after.

Basic configuration

{
  "Database": {
    "Host": "cs2-mariadb.cs2.svc.cluster.local",
    "Port": 3306,
    "Database": "cs2",
    "User": "cs2",
    "Password": "change-me"
  },
  "Progression": {
    "BotXpMultiplier": 0.25,
    "KillXp": 10,
    "RareSkillShotXp": 25
  },
  "Panel": {
    "Mode": "Auto"
  }
}

Settings left out keep their defaults.

Advanced Usage

Tuning the economy

Progression holds every number the plugin uses:

• XP per event: hits, kills, headshots, assists, and skill shots by rarity.
• Bonuses: weapon level-ups and finished tiers.
• Curves: the rank and weapon level costs.
• Ladders: the five tier thresholds for each challenge kind.
• Detection thresholds: such as MovingTargetSpeed, QuickscopeSeconds, FlickDegrees, and EfficientReloadFraction.
• Record minimums: a kill must reach RecordMinimumDistanceShare (half) of its class's Long shot distance, or RecordMinimumNoScopeDistance for a no-scope, before it can set a record, and a life or map must reach RecordMinimumLifeKills, RecordAccuracyMinimumShots, or RecordMinimumMapSkillShots, so the first records aren't ordinary moments.

Panel placement

Floaties picks World (the default) or Hud mode, turns the floating XP text on or off, and sets how long it lasts, how far it rises, how quickly gains merge, how many one player can have at once, its colors, how big it's drawn by distance (SizePerUnitOfDistance, MinWorldUnitsPerPixel, MaxWorldUnitsPerPixel), and the outline (StrokeWidthPixels, StrokeColor, StrokeOpacity). In Hud mode a floatie appears just above the crosshair and stays at that spot as you move, and new XP adds to it while your crosshair stays within HudReuseDegrees of where it appeared. In World mode a floatie appears above the target, or in front of you for XP with no target. A floatie's size is set when it appears and doesn't change after, and it has a half-opacity black outline for contrast.

Panel sets the draw mode (Auto, WorldText, CenterHtml, or Chat), how many lines each mode shows, and the side panel's font size, scale, color, and offsets. The default placement suits a 16:9 display. CS2 has no client-predicted anchor for world text, so the side panel trails slightly behind fast turns.

Rank tags

RankTags turns the scoreboard clan tag (ClanTag) and the chat prefix (ChatPrefix) on or off. Both are on by default. The clan tag replaces any Steam group tag the player has. The chat prefix is added to the name in the chat message itself, so gags, team chat, and dead chat work as before, and CS2-SimpleAdmin's gag hook is unaffected.

Bot personas

Bots are players too. Each bot name is a persona with its own progress, kept across maps, days, and restarts: XP and rank, weapon levels and mastery stars, challenge ladders, skill shots, feats, contracts, the play streak, season XP, per-map totals, rivals, and kill positions. A persona earns by the same rules and numbers as a human, including BotXpMultiplier for its kills on other bots, and a human's XP for killing a bot is unchanged. A persona can be a human's nemesis, and it carries and collects bounties like a human.

Bots are tracked only while at least one human is on the server, so an empty server can't farm XP, streaks, or season standings.

Each persona's id comes from its name, from 10000000000000000 to 10000000099999999. That range sits below every individual-account SteamID64, so a bot id never collides with a human's, and the site can tell a bot from its id alone. A human using a bot's name is still a different player, keyed by their SteamID64. A bot with no usable name gets id 0 and isn't tracked.

A persona appears with the humans everywhere a player shows: the ranks, ladder, leaderboards, seasons, compare, rivals, the live scoreboard and map, !top, and !stats. The site marks it with a BOT pill after its name, and its share card draws the same pill. Where only text fits, such as chat, a page title, or a link preview, the name ends in [BOT]. A persona has its own player page, feed, fights map, and share card, but no Steam profile link.

Personas are left out of:

• server records, which stay human-only even with RecordsCountBots on,
• the home page's live feed, Discord posts, the weekly digest, and chat announcements of their own moments to the server, though each persona's moments still show on its own page,
• anything drawn or sent to a player, such as the panel, chat lines, and floaties, since a bot has no client,
• the admin panel (CSS-BANS and SimpleAdmin).

The bounty board is the exception in chat. The whole server still hears when a bounty is placed on a persona, grows, or goes unclaimed, and when a persona ends a human's streak and collects the bounty, with the persona's name ending in [BOT].

css_csp_grant and css_csp_reset take bot:<name>, such as css_csp_reset bot:Muhlik, or the persona's id, to correct or reset a persona whether it's on the server or not.

Kills between two personas are stored for the heatmaps under their own per-map cap, MaxBotFightsPerMap, so they never push out a human's kills (see Kill heatmaps). While the database is down, the plugin's queue of unwritten kills drops its oldest bot fights first, for the same reason.

Progression site

Site sends the server's live state to the progression site: the map and mode, the scoreboard with where each player stands and which way they face, the feed of skill shots, rank-ups, level-ups, and finished tiers, and each player's changed progress. With an empty Url, the default, the plugin sends nothing.

{
  "Site": {
    "Url": "http://cs2-progression-site.cs2.svc.cluster.local:8081/api/ingest",
    "PublicUrl": "https://cs2-progression.example.com",
    "Token": "change-me",
    "IntervalSeconds": 2,
    "QueueLimit": 20,
    "FullResendEvery": 15
  }
}

• Url: the site's ingest endpoint. A URL that isn't absolute http or https is logged and ignored.
• PublicUrl: the address players reach the site at, which the welcome line, !site, and !stats name, and which is announced to everyone at the start and end of each match. Chat shows only the domain (plus any port or path), never the scheme or a per-player link. Empty, the default, shows no address.
• Token: the shared token the site checks on every batch.
• IntervalSeconds: the seconds between batches. Values under 1 count as 1.
• QueueLimit: how many batches wait to send. When the site is slow or down, the oldest is dropped, so the game never waits on it.
• FullResendEvery: how many batches pass between full resends of every connected player's progress, which repairs the site after a dropped batch or a restart. 0 turns it off.

Sending runs on the thread pool with a 3 second timeout, and a failure is logged at most once a minute.

Discord announcements

Discord posts the server's big moments to a Discord channel through a webhook: server records, earned feats, epic skill shots, weapon mastery stars, and rank-ups from Gold Nova up, plus a weekly digest every Monday. It's off by default, because it sends player names and progress outside the server. With an empty WebhookUrl, nothing is posted.

{
  "Discord": {
    "WebhookUrl": "https://discord.com/api/webhooks/<id>/<token>",
    "Username": "CS2 Progression",
    "Records": true,
    "Feats": true,
    "EpicSkillShots": true,
    "MasteryStars": true,
    "RankUps": true,
    "MinimumRank": "Gold Nova",
    "WeeklyDigest": true,
    "WeeklyDigestPlayers": 5,
    "QueueLimit": 50
  }
}

• WebhookUrl: the channel's webhook URL, from the channel's Integrations settings in Discord. It must be https, and because it holds the webhook's secret it is never written to the log.
• Username: the name posts appear under. Empty keeps the name set on the webhook.
• Records, Feats, EpicSkillShots, MasteryStars, RankUps: which moments to post.
• MinimumRank: the lowest rank whose rank-ups are posted, either a whole rank such as Gold Nova (all of its stages) or one stage such as Gold Nova · III. A name that matches neither counts as Gold Nova.
• WeeklyDigest: whether to post a digest of the week before at the first map start after Monday 00:00 UTC: the top climbers by rank XP earned, the rank-ups from MinimumRank up, and the weekly contract that starts now. A row in csp_digests records each week posted, so a restart never posts it twice, and a week nobody played posts nothing.
• WeeklyDigestPlayers: how many top climbers the digest lists, from 1 to 10.
• QueueLimit: how many lines wait to post. When Discord is slow or down, the oldest is dropped.

Posting runs on the thread pool, at most one post a second. Lines that arrive meanwhile are joined into the next post, a post Discord rate limits is retried after the wait it asks for, and a failure is logged at most once a minute. Player names are escaped, and posts never ping anyone.

Kill heatmaps

Heatmaps records where kills happen, so the site can draw them over each map's radar at /heatmaps, for the whole server or one player (where they got their kills, or where they died). The Lines tab draws a thin line from where each killer stood to where the victim fell, fading in from nothing at the shooter and widening toward the victim, so its bright, thick end marks where the victim fell, and the lines add up, so a single kill is a faint stroke and a lane used over and over glows bright. For one player it draws their kills and their deaths in two colors. Lines are drawn only on a map that lines up with the game's radar. Kills with a human on either end and kills between two bot personas are kept apart. Each map keeps only its latest MaxPointsPerMap of the first and its latest MaxBotFightsPerMap of the second, and the oldest are deleted as new ones arrive, so the csp_kills table stays a fixed size and bot fights never push out a human's kills.

Each player's page also shows where that player wins and loses fights, above their XP feed. A won fight is a kill, placed where the player stood, and a lost fight is a death, placed where they died, against humans and bots alike. Each area of the radar is colored by the balance of the two, green where they win most, red where they lose most, and grey where it's about even, and an area with only one or two fights stays faint. Hovering or tapping an area shows its counts. This match shows the map being played since it started, and All time shows every stored fight on that map. The panel opens on This match while the player is online and on All time, for the map they last played, while they're offline, and each browser remembers the last choice for each. New fights arrive within a couple of seconds, without a refresh, and a map change switches the panel to the new map. A map with no radar calibration shows no fights.

{
  "Heatmaps": {
    "Enabled": true,
    "SampleEvery": 1,
    "MaxPointsPerMap": 30000,
    "MaxBotFightsPerMap": 10000,
    "QueueLimit": 5000
  }
}

• Enabled: whether kill positions are recorded.
• SampleEvery: keep one kill in this many on each map. 1 keeps every kill.
• MaxPointsPerMap: how many kills with a human on either end each map keeps. Values under 100 count as 100.
• MaxBotFightsPerMap: how many kills between two bot personas each map keeps, counted apart from MaxPointsPerMap. Values under 100 count as 100.
• QueueLimit: how many kills wait to be written while the database is down. Past this, the oldest are dropped.

Kills are written in one batch per save interval, on the thread pool. The heatmaps send cell counts on a 128 by 128 grid, and the Lines tab sends lines between the centres of those same cells, never exact kill positions. The official maps line up with the game's radar from each map's overview file; any other map gets a square fitted around its kills. Radar images aren't shipped, because they're Valve's art. Instead, point Site__GamePath at the game server's csgo folder (mounted read-only) and the site reads each map's radar out of that install's own pak01_dir.vpk the first time the map is shown, keeping a 1024 by 1024 PNG under <DataPath>/radar/game until the next game update. A PNG put at <DataPath>/radar/<map>.png by hand wins over it. Without either, the page draws an outline from where people fight.

The site

The site is a small ASP.NET Core app, published as the image ghcr.io/ktsu-dev/counterstrikeprogression-site:<version> with each release (and as latest). It shows the live scoreboard, the feed, and a live map of every player on /, the rank ladder on /ranks, leaderboards for every weapon (by level) and every skill shot (by count), plus the most feats and the rarest skill shots, on /leaderboards, a guide to every skill shot with its rarity, weapons, XP, tiers, and how many players have earned it on /skillshots, kill heatmaps on /heatmaps, and each player's profile on /players/{steamId} (a SteamID64, or a bot persona's id), with their XP feed, suggested next challenges, and a live map of where they win and lose fights. The home page's map draws everyone on the current map's radar, moving with each batch: humans as bright dots named and linked to their player page, bots as smaller, dimmer dots named on hover or tap (a bot persona's name links to its page, with the BOT mark), and nobody while dead. Each kill draws a thin line from the killer to an ✕ where the victim fell, brighter for a headshot, and fades out over about 10 seconds, so the map shows the recent fighting. Hovering or tapping an ✕ names the killer, the victim, and the weapon. Kills between bots show too. When the server goes offline, the last positions stay, faded. The fights map marks where the player is now while they're on the map it shows, and keeps their last known spot, faded, while they're dead or gone. Live positions are exact and public, held only in memory, and never stored. Ranks show as badges: the color and emblem mark the rank's family, and the pips along the bottom fill with the stage. Pages update live over server-sent events, and a server counts as offline after a few seconds without a batch.

The image listens on two ports:

• 8080 (public): /, /ranks, /leaderboards, /skillshots, /heatmaps, /players/{steamId}, /radar/{map}.png, /api/heatmaps, /api/live, /api/ranks, /api/leaderboards, /api/skillshots, /api/players/{id}, /api/players/{id}/fights, /api/positions, /api/stream, and /healthz. Route this port to visitors.
• 8081 (ingest): POST /api/ingest with the header Authorization: Bearer <token>, and GET /metrics for Prometheus. Keep this port inside your network, because only the plugin and your scraper need it.

Point the health probe at /healthz on port 8080. Port 8081 answers nothing but the ingest and metrics routes, so a probe there always fails.

/metrics has these series:

• csp_site_server_online: 1 when a batch arrived within the offline window.
• csp_site_players_online{kind="human"|"bot"}: players in the last batch.
• csp_site_last_batch_age_seconds: seconds since the last batch, or since the site started when none has arrived. Alert on this while the game server is up.
• csp_site_ingest_batches_total and csp_site_ingest_failures_total{reason="unauthorized"|"too_large"|"bad_request"}: batches applied and turned away.
• csp_plugin_send_failures_total, csp_plugin_batches_dropped_total, and csp_plugin_save_failures_total: the plugin's own counts since it loaded, as of its last batch. They reset when the plugin reloads, and are absent until a batch carries them.

The site reads progress from the plugin's database and never writes to it. Give it a user with SELECT on csp_players, csp_weapons, csp_challenges, csp_seasons, csp_records, csp_rivals, and csp_kills and nothing else. Until it has csp_rivals, player pages still load but show no rivals. The live state and the feed history live in the site's memory and in a file under /data, so mount a volume there if the feed should survive a restart. The image runs as the non-root user with UID 1654, so that user must be able to write to the volume (in Kubernetes, set the pod's fsGroup to 1654).

Configure the site with environment variables:

Variable	Default	Meaning
Site__Database__Host	empty	The database host. Empty keeps progress in memory, which starts empty.
Site__Database__Port	3306	The database port.
Site__Database__Database	cs2	The database name.
Site__Database__User	cs2	The read-only database user.
Site__Database__Password	empty	The database password.
Site__Database__RequireTls	false	Whether the database connection must be encrypted. When it's false, the site still uses TLS if the server offers it.
Site__Token	empty	The bearer token the plugin sends. Empty rejects every batch.
Site__DataPath	/data	The folder for the feed history file, and for radar images in its radar folder. It must be writable by UID 1654, the user the image runs as.
Site__GamePath	empty	The game server's csgo folder, holding pak01_dir.vpk, to read the heatmaps' radar images from. Empty uses only the images in <DataPath>/radar.
Site__OfflineAfterSeconds	15	Seconds without a batch before the server counts as offline.
Site__FeedLength	50	How many feed entries to keep and show.

Point the plugin's Site.Url at port 8081 and set Site.Token to the same value as Site__Token.

API Reference

Skill shots

Group	Skill shots
Movement	Moving target, Airborne target, Jumpshot, Air to air, Run and gun, Crouch kill, Ladder kill, Silent kill, Landing shot, Water kill
Distance	Long shot, Point blank, Pistol sniper
Penetration and visibility	Wallbang hit, Wallbang, Double wallbang, Through the smoke, Blind kill
Scope	No-scope, Quickscope, Flying no-scope, Scoped on the move
Utility and melee	Grenade kill, Fire kill, Grenade impact, Knife kill, Backstab, Zeus kill, Flash assist, Long flash
Timing and aim	Quick switch, Fresh mag, Last bullet, One tap, Flick, Spray transfer, Efficient reload, Marksman, Sharpshooter, Headhunter
Multi-kill and situation	Double kill, Triple kill, Rampage, Untouchable, 10-kill streak, 20-kill streak, Collateral, Opening kill, Trade, Revenge, Last stand, Bounce back, Defuse denial, Clutch

Storage tables

Table	Contents
csp_players	Steam ID, name, rank XP, rank, first and last seen
csp_weapons	Steam ID, weapon, weapon XP, level, kills, headshots, hits, shots
csp_challenges	Steam ID, weapon, challenge, count, tier reached
csp_seasons	Steam ID, season start, rank XP earned in the season
csp_kills	Map, killer and victim Steam IDs or bot persona ids (0 for a bot with no persona), weapon, headshot, whether both ends are bot personas (bot_fight), both positions, time
csp_rivals	Killer's Steam ID, victim's Steam ID, kills
csp_records	Record id, the holder's Steam ID, name, and value, when it was set, and the holder it was taken from
csp_schema	The schema version

Skill shot ids double as challenge ids in csp_challenges, so an id is never renamed once released.

Contributing

Contributions are welcome! Feel free to open issues or submit pull requests.

License

This project is licensed under the MIT License. See the LICENSE.md file for details.