Fixes a problem where the game would not start if antialiasing was switched on on Mac Minis.
Universal binary, native for both Intel and PowerPC processors. (Only the editor is still a PowerPC application).
Uses OpenGL for graphics.
Full screen at any resolution, with much sharper graphics at higher resolutions, and millions of colors.
System requirements are now officially MacOS X 10.4, although you can always try on earlier versions, you may be lucky (let me know!). Classic is no longer supported, but I can always send the old version 1.5.2 on request.
On popular request, keyboard control using the arrow keys, although I personally feel this is a lot more difficult than using the trackpad on a laptop. Some people would not believe me, so now they can see for themselves! I tried to find a balanced acceleration setting so you can move slowly (with precision) and quickly (fast reaction) depending on how long you hold down the arrow key, yet it is still too slow in some situations and too fast in others, especially when trying to follow a ball at the same speed. You'll get better results with some practice using the trackpad or, even better, an external mouse.
Sound volume can be adjusted. This is multiplied with the system sound volume. The number of sound channels is no longer adjustable, since this was only necessary on low end systems running MacOS 9 or earlier.
The standard location of the preferences file "Colibricks preferences" has changed. The game first looks in the user's preferences folder, then in the global preferences folder, and finally in the Classic preferences folder. If none is found, a new file is created in the user's preferences folder. If you want multiple users to share the high score table, just move "Colibricks preferences" to "/Library/Preferences". You can also place it anywhere else and put an alias (shortcut, symlink,...) in the preferences folder.
Fixed a small cosmetic bug saving and reloading games with moving textured bricks on them (like the Mona Lisa level, for example). The bricks would carry the wrong part of the picture after reloading, because the original starting coordinates of the brick were not remembered.