Train Skills
Level gathering and production skills with continuous idle-friendly activities and offline progress.
Train skills, craft better equipment, fight increasingly dangerous enemies, build wealth, and grow a shared clan with your friends β all from your browser.
No Limit Idle is currently in Early Access. Balance, progression, interface elements, and multiplayer systems may continue to change as the game is developed.
Progress your character through gathering, production, combat, equipment, quests, trading value, and long-term account progression.
Level gathering and production skills with continuous idle-friendly activities and offline progress.
Your equipped weapon determines whether you train Attack, Strength, Sharpshooter, or Mage, with Defense trained through Mixed XP.
Smith weapons, craft ammunition and magic gear, cook food, and build toward stronger combat setups.
Gather valuable materials, manage equipment, sell exact quantities, and build up your gold reserves.
Complete personal and clan objectives for rewards while working toward long-term account milestones.
Create an account and carry your progress between supported browsers and computers.
Every archived release note is now kept here. Scroll through the history and expand any version to see its changes.
NaN / NaN XP.supabase_v116_clan_claim_xp_totals.sql once after the existing V113 migration.assets/... references are verified before packaging.No new Supabase migration is required for v114.
skill_xp_decrease false positives seen in live anti-cheat logs.Run supabase_v113_single_session_offline_pacing.sql once after the V112 migration and deploy the V113 client alongside it.
Run supabase_v112_clan_raid_rewards_countdown.sql once after the V111 contribution migration.
Contribution is derived from server-validated killTracker deltas. Players cannot submit an arbitrary contribution value from the browser.
Run supabase_v111_clan_raid_contributions.sql once after the V110 systems migration.
nolimitdev now has a server anti-cheat event dashboard.Run supabase_v110_systems_expansion.sql after V108 and all earlier required migrations. V109 has no SQL migration.
No new V109 migration is required. Keep the V108 XP-rebalance migration installed.
Run supabase_v108_xp_rebalance.sql after V107 and deploy the V108 client alongside it.
game_saves.nolimitdev account keeps its server-authorized Dev Tools bypass.Run supabase_v107_anticheat_and_player_resets.sql once after V106 before deploying V107.
Run supabase_v106_fixed_xp_curve.sql once before deploying V106. Keep all earlier migrations installed.
No new Supabase migration is required for v105. Keep migrations through v104 installed.
Run supabase_v104_golden_title.sql once after migrations through v101.
No new Supabase migration is required for v103. Keep all migrations through v101 installed.
No new Supabase migration is required for v102. Keep all migrations through v101 installed.
nolimitdev account is completely isolated from the live Player Market and cannot send items to other players.nolimitdev is excluded from all-time leaderboard results.nolimitdev cannot create/join clans, donate Gold, contribute quests/Clan Skills, claim clan rewards, or use Clan Vaults.Run supabase_v101_dev_isolation_market_edit.sql once after the V100 Dev Tools migration.
nolimitdev account.nolimitdev Supabase auth UUID by the v100 migration.Run supabase_v100_dev_tools.sql once after the nolimitdev account exists and has a cloud save.
Run supabase_v99_buy_offers_item_mail.sql once in Supabase before deploying this build. The original Player Market SQL remains required for normal sell listings.
PATCH_NOTES.md, which will remain cumulative in future releases.storeUpgrades defaults safely for older saves.CLIENT_RELEASE_VERSION is now v98.No new Supabase SQL migration is required for v98.
CLIENT_RELEASE_VERSION is now v96.No new Supabase SQL migration is required for v96.
Combat-gear recipes now use only their primary material, following a 4/6 pattern for each two-piece tier:
All previous board, bar, herb, and gemstone requirements were removed from these eight combat-gear recipes.
CLIENT_RELEASE_VERSION is now v95 for the existing backup/recovery versioning behavior.No new Supabase SQL migration is required for v95.
CLIENT_RELEASE_VERSION is now v94, so the existing v86 backup system can take its normal pre-release snapshot behavior.No new Supabase SQL migration is required for v94.
No new Supabase SQL migration is required for v93.
PASSWORD_RECOVERY auth event opens a dedicated Set a New Password modal.auth.updateUser({ password }) is called.game_saves row or cloud backup history.No new SQL migration is required. Password reset uses Supabase Auth.
Make sure the deployed game URL is allowed in Supabase β Authentication β URL Configuration β Redirect URLs. For the current production site this should include the game route, for example:
https://nolimitidle.netlify.app/gamehttps://nolimitidle.netlify.app/game.html as well.Supabase must also be able to send Auth emails. For production-volume email delivery, configure SMTP in Supabase rather than relying on the low-volume default sender.
Keep the existing v77/v80/v86/v91 migrations installed. v92 itself adds no database tables or RPCs.
Run supabase_v91_multiplayer_chat.sql once in Supabase β SQL Editor before deploying v91.
The chat tables are not directly writable/readable by browser clients. Authenticated players access chat through security-definer RPCs that validate Global, Clan, and DM visibility server-side.
This update does not replace the earlier clan or cloud-backup migrations. Keep v77/v80/v86 installed.
No Supabase SQL changes are required for v90.
Deploy the full v87 folder/ZIP. If the v86 cloud backup migration has already been installed, no additional SQL is needed.
Run supabase_v86_cloud_backup_recovery.sql once in Supabase β SQL Editor before deploying v86.
public.game_saves.public.game_save_backups.v86, future v87, etc.).1. Find the player's UUID in Supabase β Authentication β Users.
2. In SQL Editor, list their backups:
select *
from public.admin_list_game_save_backups(
'PLAYER-UUID-HERE'::uuid,
50
);
3. Copy the backup id you want to restore and run:
select public.admin_restore_game_save_backup(
'PLAYER-UUID-HERE'::uuid,
'BACKUP-UUID-HERE'::uuid
);
Before a restore, the current live save is automatically preserved as a pre_restore backup. The restored save's internal offline-progress timestamp is reset to the restore time so an old backup cannot award unintended offline progress.
Every future release should update CLIENT_RELEASE_VERSION in game.html (for example v87). The first save on that release then automatically snapshots the previous release before overwriting it.
No Supabase SQL changes are required for v82.
No new SQL migration is required beyond the existing v77/v80 migrations.
If v77 clan progression SQL is already installed, run:
supabase_v80_sunday_clan_weekly_reset.sqlFor a fresh database setup, the included supabase_v77_clan_progression.sql has also been updated so its weekly quest function uses Sunday noon Eastern directly.
Run supabase_v77_clan_progression.sql once in Supabase β SQL Editor before deploying v77 if you want Clan Skill Levels and scaled/noon-reset clan quests.
The game gracefully falls back to the older clan quest RPC if the migration is not installed, but Clan Skill XP will remain pending until the migration is available.
The current cumulative archive covers v77 through v126. Future releases will append new notes without deleting older versions.
Create a clan, share an invite code, combine quest progress, use a shared clan vault, and talk with other players through Global, Clan, and Direct Message chat.
Invite friends using a shared clan join code and see everyone in the same online roster.
Deposit and withdraw eligible high-value items through the clanβs shared online storage.
Daily and weekly quest progress combines contributions from every clan member.
Talk in Global Chat, keep clan conversations private, or message individual players directly.
Create your account, train your first skill, and start building your character.