Paintown 3.6.0 is almost ready to be released. I put up builds for windows, linux, and osx in the pre-release folder of the sourceforge downloads section. Once I am satisfied that all the platforms work relatively well I will move them over to the 3.6.0 folder, thus officially performing the release. Builds of the ps3 and wii will take a little more time just because I want to test them at least once before they are released.
I have pretty much blogged about most of the new stuff in this release in previous posts. Most of the work this time went into the mugen engine. It is now quite playable and somewhat enjoyable to watch the AI fight itself. Recently I added 7z support so mugen characters and motifs can be stored in 7z files. This improvement also affects other parts of the system that load compressed files, such as the paintown mod system.
I would have done the release a bit earlier but I had some difficulty getting the OSX build in shape. I spent a few hours this week fixing some problems with the build but once I finally got a working app I discovered that the new gatekeeper in OSX 10.8 threw a wrench into my wonderful plans. Apparently Apple wants all apps to be signed using a certificate issued by Apple themselves and if an app is not signed then the default action of clicking on an app is an error which says ‘this app is damaged’. That error message is reused for a number of other issues such as a malformed Info.plist file inside the app so its not clear to the end user that the issue is related to it not being signed. Anyway there are three workarounds for this issue:
1. The user can allow untrusted apps to be run by changing a global setting
2. The user can cd to paintown-3-6-0.app/Contents/MacOS and run ./paintown-3-6-0 directly
3. I can sign the paintown app with a certificate issued by Apple
I don’t expect a lot of people will go with option 2 so I hope that OSX users can tolerate running untrusted apps. Its not like thats new or anything, gatekeeper didn’t exist versions of OSX earlier than 10.8. Option 3 is possible but to get a certificate I need to enroll in the Mac Developer Program which costs $99 a year. This amount of money isn’t a lot but I feel its quite unnecessary to be subjected to a rather arbitrary fee to work around an artificial problem. If someone wants to donate the money to me I am more than happy to use it to sign up for the program and get a signing certificate.
It may be possible to sign the app with a self-issued certificate but all the advice and googling I have found so far indicate that this will not work.
I asked some other OSX developers if this new gatekeeper thing will effectively destroy free/open source software on OSX. I didn’t get a direct answer but someone did say that apps built on the same machine that will ultimately run the app don’t have to be signed. While probably true that is an onerous task that extremely few users would be willing to put up with. The Paintown OSX build is pretty difficult even for me. I could make it slightly easier but still I doubt many people would bother doing it. I haven’t found out yet what other open source projects are doing / going to do about this signing issue but I would like to find out.
Anyway I am excited for this release because there are new features/bugs I want to fix that would have delayed the release had I done them earlier. I hope everyone enjoys it.