Log inGet started
World

Powerplay: Abilities, Cooldowns and Status Effects Kit

Merged

abilitiesKit 1.1.4: build against controlsKit 1.3.1 so worlds keep one controlsKit

#2
Author
claude-code @ auraAgent
Opened
Nov 13, 2026
From
repin-controlskit
Into
main
Merged
Nov 13, 2026

abilitiesKit 1.1.3 installs its own controlsKit 1.2.8. A world that already has the current controlsKit (1.3.1, which navUiKit, menusKit and others bring) ends up with two copies, and ~controlsKit.controls becomes ambiguous (two packages answer to the name). Found while building Castaway Isle, where every other kit agrees on controlsKit 1.3.1.

Changes:

  • controlsKit updated from 1.2.8 (bcafee4) to 1.3.1 (963fd18) in this world.
  • abilitiesKit version 1.1.3 to 1.1.4 (package.yaml, AK.VERSION, README title), README pin line and a 1.1.4 release note.
  • @builtin moved to d736e1d (a world on an older @builtin is hidden from players).

No change to abilitiesKit's own code. The kit's 55-test suite passes against controlsKit 1.3.1.

7 files changed

  • ChangedabilitiesKit.packageFolderBeforeAfter
  • ChangedabilitiesKit.package/README.md36.2 KB → 36.5 KBBeforeAfter
  • ChangedabilitiesKit.package/api.moduleFolderBeforeAfter
  • ChangedabilitiesKit.package/api.module/init.luau18.2 KB → 18.2 KBBeforeAfter
  • ChangedabilitiesKit.package/package.yaml591 B → 591 BBeforeAfter
  • ChangedcontrolsKit.package.pull181 KB → 206 KBBeforeAfter
  • Changedlibs/@builtin194 B → 194 BBeforeAfter

Checks

No checks have been posted.

Reviews

No reviews yet.

Conversation

  1. claude-code @ auraAgentNov 13, 2026

    Review before merge: controlsKit moves 1.2.8 to 1.3.1; abilitiesKit's own code changes only its VERSION string; README version lines match what is installed; the 55-test suite passes against controlsKit 1.3.1 (its docs test reads the installed versions). Fast-forwardable, no conflicts. Merged.

Sign in to comment or review.