Skip to content

Releases: Tetro48/cambridge

Snapshot 24w27a

02 Jul 03:49
46d4475
Compare
Choose a tag to compare
Snapshot 24w27a Pre-release
Pre-release

cambridge_windows_x64.zip - For Windows 64bit.
cambridge_windows_x86.zip - For Windows 32bit.
cambridge_other.zip - For LOVE supported platforms.
cambridge_linux_x64.zip - For Linux 64bit, game contained within one file.
cambridge_linux_experimental.zip - For Linux 64bit, game contained within one file. Likely buggy.
cambridge_windows_aarch64_experimental.zip - For Windows for ARM. Likely buggy, and some functions won't work.

Full Changelog: 24w24b...24w27a

Notes:

  • Modes and rulesets shouldn't be placed into a resource pack.
  • Resource packs should be placed at <save directory>/resourcepacks/
  • Resource pack assets load from one mounted directory.
    • It's like this to mostly avoid path collisions and make priority loading possible.

Resource pack samples:

Snapshot 24w24b

11 Jun 16:50
4ec5eb7
Compare
Choose a tag to compare
Snapshot 24w24b Pre-release
Pre-release

cambridge_windows_x64.zip - For Windows 64bit.
cambridge_windows_x86.zip - For Windows 32bit.
cambridge_other.zip - For LOVE supported platforms.
cambridge_linux_x64.zip - For Linux 64bit, game contained within one file.
cambridge_linux_experimental.zip - For Linux 64bit, game contained within one file. Likely buggy.
cambridge_windows_aarch64_experimental.zip - For Windows for ARM. Likely buggy, and some functions won't work.

Fixed a minor bug with not being able to click to go back in key config

Notes:

  • Modes and rulesets shouldn't be placed into a resource pack.
  • Resource packs should be placed at <save directory>/resourcepacks/
  • Resource pack assets load from one mounted directory.
    • It's like this to mostly avoid path collisions and make priority loading possible.

Resource pack samples:

Snapshot 24w24a

11 Jun 16:25
a0ce53e
Compare
Choose a tag to compare
Snapshot 24w24a Pre-release
Pre-release

cambridge_windows_x64.zip - For Windows 64bit.
cambridge_windows_x86.zip - For Windows 32bit.
cambridge_other.zip - For LOVE supported platforms.
cambridge_linux_x64.zip - For Linux 64bit, game contained within one file.
cambridge_linux_experimental.zip - For Linux 64bit, game contained within one file. Likely buggy.
cambridge_windows_aarch64_experimental.zip - For Windows for ARM. Likely buggy, and some functions won't work.

Notes:

  • Modes and rulesets shouldn't be placed into a resource pack.
  • Resource packs should be placed at <save directory>/resourcepacks/
  • Resource pack assets load from one mounted directory.
    • It's like this to mostly avoid path collisions and make priority loading possible.

Resource pack samples:

Full Changelog: v0.4.3.9-pre1...24w24a

v0.4.3.9-pre1: Massive scope for a "patch" release

08 May 09:23
8bc16c1
Compare
Choose a tag to compare

cambridge_windows_x64.zip - For Windows 64bit.
cambridge_windows_x86.zip - For Windows 32bit.
cambridge_other.zip - For LOVE supported platforms.
cambridge_linux_x64.zip - For Linux 64bit, game contained within one file.
cambridge_linux_experimental.zip - For Linux 64bit, game contained within one file. Likely buggy.
cambridge_windows_aarch64_experimental.zip - For Windows for ARM. Likely buggy, and some functions won't work.

This is a rather huge update for what's considered a "patch" release.

Notes:

  • Modes and rulesets shouldn't be placed into a resource pack.
  • Resource packs should be placed at <save directory>/resourcepacks/
  • Resource pack assets load from one mounted directory.
    • It's like this to mostly avoid path collisions and make priority loading possible.

Resource pack samples:

Full Changelog: v0.4.3.8...v0.4.3.9-pre1

v0.4.3-arcade: Arcade Mode!

24 Mar 09:15
3ba72ae
Compare
Choose a tag to compare

cambridge_windows_x64.zip - For Windows 64bit.
cambridge_windows_x86.zip - For Windows 32bit.
cambridge_other.zip - For LOVE supported platforms.
cambridge_linux_x64.zip - For Linux 64bit, game contained within one file.
cambridge_linux_experimental.zip - For Linux 64bit, game contained within one file. Likely buggy.
cambridge_windows_aarch64_experimental.zip - For Windows for ARM. Likely buggy, and some functions won't work.

This is a modified Cambridge branch to make it more suitable to be used in arcades.
Test mode key is F2. Identity: cambridge-arcade

v0.4.4.0-alpha4

29 Feb 14:44
ecd87dd
Compare
Choose a tag to compare
v0.4.4.0-alpha4 Pre-release
Pre-release

cambridge_windows_x64.zip - For Windows 64bit.
cambridge_windows_x86.zip - For Windows 32bit.
cambridge_other.zip - For LOVE supported platforms.
cambridge_linux_x64.zip - For Linux 64bit, game contained within one file.
cambridge_linux_experimental.zip - For Linux 64bit, game contained within one file. Likely buggy.
cambridge_windows_aarch64_experimental.zip - For Windows for ARM. Likely buggy, and some functions won't work.

Notes:

  • Modes and rulesets, even within mod packs will fully reload every time you enter replay selection screen.
  • When you add a new mode or ruleset when the game is still launched, reload all modules by executing CTRL+R to make a new mode or ruleset appear.
  • Modes and rulesets shouldn't be placed into a resource pack, since there's now a mod pack system for that.
  • Mod packs will load independently unless they're linked together. (though not sure why would you use that?)
  • Mod packs should be placed at <save directory>/modpacks/
  • Resource packs should be placed at <save directory>/resourcepacks/
  • Resource pack assets load from one mounted directory.
    • It's like this to mostly avoid path collisions and make priority loading possible.

Mod pack samples:

Resource pack samples:

Full Changelog: v0.4.4.0-alpha3...v0.4.4.0-alpha4
I'm kinda lazy there...

v0.4.3.8

04 Feb 15:07
9f30237
Compare
Choose a tag to compare

cambridge_windows_x64.zip - For Windows 64bit.
cambridge_windows_x86.zip - For Windows 32bit.
cambridge_other.zip - For LOVE supported platforms.
cambridge_linux_x64.zip - For Linux 64bit, game contained within one file.
cambridge_linux_experimental.zip - For Linux 64bit, game contained within one file. Likely buggy.
cambridge_windows_aarch64_experimental.zip - For Windows for ARM. Likely buggy, and some functions won't work.

This is a... rather awkward release. If you see some changes that indicate of preparing to the eventual merge of v0.4.x-dev at cambridge-stacker/cambridge, oh well.

Notes:

  • Modes and rulesets shouldn't be placed into a resource pack.
  • Resource packs should be placed at <save directory>/resourcepacks/
  • Resource pack assets load from one mounted directory.
    • It's like this to mostly avoid path collisions and make priority loading possible.

Resource pack samples:

Changelog from v0.4.3.7:

  • Credits has changed
  • Modules now have to be manually reloaded (exception at replays menu)
  • Title screen has changed
  • Added Join Discord and Report Bugs to main menu
  • Mouse release event now triggers even if it hasn't moved in 2s as long as it's pressed
  • Now only makes file backup if both loading and deserialization succeeds instead of just loading

v0.4.3.7

28 Jan 18:17
cdf2721
Compare
Choose a tag to compare

cambridge_windows_x64.zip - For Windows 64bit.
cambridge_windows_x86.zip - For Windows 32bit.
cambridge_other.zip - For LOVE supported platforms.
cambridge_linux_x64.zip - For Linux 64bit, game contained within one file.
cambridge_linux_experimental.zip - For Linux 64bit, game contained within one file. Likely buggy.
cambridge_windows_aarch64_experimental.zip - For Windows for ARM. Likely buggy, and some functions won't work.

1200th commit milestone.

Notes:

  • Modes and rulesets shouldn't be placed into a resource pack.
  • Resource packs should be placed at <save directory>/resourcepacks/
  • Resource pack assets load from one mounted directory.
    • It's like this to mostly avoid path collisions and make priority loading possible.

Resource pack samples:

Changelog since v0.4.3.6:

  • Now using LOVE 11.5, and added AppImage of it
  • Patched a bug with Tutorial Keybinder

v0.4.4.0-alpha3

01 Jan 05:25
5076d00
Compare
Choose a tag to compare
v0.4.4.0-alpha3 Pre-release
Pre-release

cambridge_windows_x64.zip - For Windows 64bit.
cambridge_windows_x86.zip - For Windows 32bit.
cambridge_other.zip - For LOVE supported platforms.
cambridge_linux_experimental.zip - For Linux, appimage contained within. Likely buggy.
cambridge_windows_aarch64_experimental.zip - For Windows for ARM. Likely buggy, and some functions won't work.

Notes:

  • Modes and rulesets, even within mod packs will fully reload every time you enter mode or replay selection screen.
    Partly for the hash system, and also to allow modifying a mod file and see changes when you go back to selection screen.
  • Modes and rulesets shouldn't be placed into a resource pack, since there's now a mod pack system for that.
  • Mod packs will load independently unless they're linked together. (though not sure why would you use that?)
  • Mod packs should be placed at <save directory>/modpacks/
  • Resource packs should be placed at <save directory>/resourcepacks/
  • Resource pack assets load from one mounted directory.
    • It's like this to mostly avoid path collisions and make priority loading possible.

Mod pack samples:

Resource pack samples:

Changelog since alpha2:

  • Path text now fades out vertically
  • Added drawWrappingText function
  • Fixed secret inputs not saving properly in replay re-recording
  • Fixed a bug with randomly setting replay speed while in re-recording
  • Show invisible now works in re-recording mode. Note: While re-recording, you'll not be able to turn it off.
  • Refactored input naming

v0.4.3.6

01 Jan 05:23
5913717
Compare
Choose a tag to compare

cambridge_windows_x64.zip - For Windows 64bit.
cambridge_windows_x86.zip - For Windows 32bit.
cambridge_other.zip - For LOVE supported platforms.
cambridge_linux_experimental.zip - For Linux, appimage contained within. Likely buggy.
cambridge_windows_aarch64_experimental.zip - For Windows for ARM. Likely buggy, and some functions won't work.

Notes:

  • Modes and rulesets shouldn't be placed into a resource pack.
  • Resource packs should be placed at <save directory>/resourcepacks/
  • Resource pack assets load from one mounted directory.
    • It's like this to mostly avoid path collisions and make priority loading possible.

Resource pack samples:

Changelog since v0.4.3.5:

  • Added drawWrappingText function
  • Fixed secret inputs not saving properly in replay re-recording
  • Fixed a bug with randomly setting replay speed while in re-recording
  • Show invisible now works in re-recording mode. Note: While re-recording, you'll not be able to turn it off.
  • Refactored input naming