1) New courses
2) More achievements
3) ‘Challenge’ mode
4) Maybe a ’slight’ tweaking of some pars
5) Local multiplayer (may or may not have time to get to this one)
6) Shot addition powerdowns (opposite of shot subtractors)…. I’ve got some interesting ideas for hole designs with this one…
7) practice mode (practice any unlocked hole)
bug fixes
9) possibly an unlockable feature that allows you to change the color of your stickman and/or type of fireball shot

4 brand new courses
Pinch screen to zoom out (iphone version only)
Longer more accurate power meter
More responsive ‘Go’ button
More accurate arrows for aiming
A ‘restart course’ button
Improved collision physics
Fixes for background audio
Shot subtractor powerups
7 new achievements
New way to unlock courses
Courses grouped by difficulty
Bronze, Silver, and Gold star rating
Bug fixes and performance improvements

• 4 brand new courses! (which will include one more ‘beginner’ course)
• A course ‘restart’ button on the menu.
• Fine-tuning aim. (slower movement of the directional arrow)
• Longer and more accurate power meter.
• Shot bonus subtractors!!! (new special feature)
• Slight re-working of how courses are unlocked.
• More responsive ‘Go’ button.
• Wind tweaks in ‘hard’ mode.
• Control button ‘alignment’ settings.
• Various other small things…

Stay tuned…

UPDATE!!
Some screen caps from the next update:

A quick video of the gameplay:

Symptom:
You are a PHP developer who uses Eclipse PDT, or netbeans IDE, or something else and needs to debug via xdebug. If you have ever come across the problem where setting breakpoints ONLY seems to work in index.php, here is the solution:

Solution:
Simple explanation is if you have soft-links in your php include path, or if you are using a case-insensitive file system (OSX), the path of the breakpoint your setting in your IDE must EXACTLY match the path where php loads the file from. In my case, both of these conditions were the root cause of my debugger not stopping on my breakpoints in my IDE.

Here was my configuration:
I set the include path in my .htaccess file. Lets just say I set it to something like:
“/Applications/xampp/htdocs”

And lets say that in htdocs, I’ve got two files index.php and MyClass.php. Now, in my case the path “/Applications/xampp/htdocs” is actually a softlink to “/Applications/XAMPP/xamppfiles/htdocs” (notice the upper-case). Now, this is all fine and dandy. Php works fine, it finds the path on the filesystem, and loads up my files without php problems… However, when I debug in Eclipse PDT, breakpoints only work in the index file…. WTF? So I enabled xdebug logging, and I saw the that debug client was telling xdebug to break inside MyClass.php, but the path of the file it was breaking on was
“/Applications/XAMPP/xamppfiles/htdocs/MyClass.php”…
Php loaded the file at: (due to what my include path is)
“/Applications/xampp/htdocs/MyClass.php”

Yes, it’s the same file, but i guess xdebug just can’t figure that out. Simple solution, throw an xdebug_break() in the file you want to breakpoint on…. This should always work. Have a look at your stack and check the path of the file that the breakpoint is on… Make sure that that path is exactly the one your using in your include path in php…. CASE SENESITIVE AS WELL….

At first I thought this was a php 5.3 problem (as the problem just started when I upgraded to 5.3, however that’s when xampp project decided to use CAPITALS XAMPP instead of lower-case)… Then I thought it had something to do with mod rewrite…. Nope. If breakpoints work in your index file they should work everywhere else… If they’re not, it’s a PATH problem.

In my case, I just changed my php include path from
“/Applications/xampp/htdocs”
to
“/Applications/XAMPP/xamppfiles/htdocs”
and VOILA! All breakpoints work again.

Check out some of the reviews here!

Appmodo Review

Appmodo Top 3 Games in May

TouchReviews Review

Just Another iPhone Blog

Ok. I did the ones on the left… Moral of the story, get a designer. These screencaps really don’t even give the new designs justice. Was it worth the extra month? You decide.

So we finished up our last week of beta testing. There’s no show stopping problems, so we’re wrapping up and making our first submission to apple. Here’s hoping there’s no problems, and Stick Golf should be live on the app store within the next couple weeks!

Or course we still could be adding features, but at some point you just gotta stop and roll with it. If things work out, we’ll be adding new courses every couple weeks and trying to get new updates out often. Stay tuned…