36 replies to this topic

[Desert Dog]

Golfing Block
♫♪ by Desert Dog ♪♫

Swing your way through 16 bite-sized levels in this wacky arcade golfing game. Try to get hole in ones!

Play Now

Some screenshots:




Designed to (hopefully) work on mobile phones. Please try it in one, if you can, and let me know of any issues, if any!

Cheers!

Edited by Desert Dog, 09 February 2012 - 09:46 PM.

[thegame]

I did it! Good game. Didn't play it on mobile though

Spoiler

Edited by thegame, 09 February 2012 - 10:30 PM.

[Desert Dog]

Wow, good job on that! :D I thought I'd be the only one able to get them all! D:

Thanks for trying!

Edited by Desert Dog, 09 February 2012 - 10:46 PM.

[nujuat]

I haven't played for that long yet, but it seems to work well on my ipod touch gen 4. It is a little bit slow, but it's definitely playable. It would also be faster on iphones as well. The screen is the right size and everything (well, that is if you save it to the home screen).

Good job!

[YellowAfterlife]

HTC Wildfire S:
Part of game appears to be hidden by the menu.
Could not get past the menu screen - any attempt to interact with game resulted in it's being selected (with color, as happens to text or images) and deselected in a moment.

Judging from PC experience, nice game though.

[Desert Dog]

I haven't played for that long yet, but it seems to work well on my ipod touch gen 4. It is a little bit slow, but it's definitely playable. It would also be faster on iphones as well. The screen is the right size and everything (well, that is if you save it to the home screen).

Good job!

I left blank(ish) spaces at the top/bottom of the game, for any URL bars, if any. Do they still drop down yet further, into the game?! D:

Thanks for playing! Any feedback on the controls would be sweet, I've gotten to wondering if I shouldn't make the finger point in the opposite direction of the ball, so the player can see where he's hitting. What do you think?

Part of game appears to be hidden by the menu.
Could not get past the menu screen - any attempt to interact with game resulted in it's being selected (with color, as happens to text or images) and deselected in a moment.

Well.. that isn't good. My memory game loaded for you, right? Although I have updated GM, since then... I'll see what I can find out about this. D: The html is just straight GM-output, I haven't made any changes.

Thanks for testing guys, and glad you like!

[allex24]

Nice game and good graphic, it's pleasure to play it on pc. I tried it on my samsung GT-P1000 - it works fine but slower suppose due to my slow internet speed on tablet.

[Desert Dog]

Thanks for testing! Glad to know it works alright, even if it's running a bit slow. :D Step in the right direction.

And yes! I got a "good graphics" comment! Achievement unlocked.

[Zesterer]

VERY nice! I played it on my iPod, and I can truthfully say that it was really quite fun, even if there was a general lack of items and other gameplay objects. I would love to see more games like this in the future!

Zesterer

[Desert Dog]

Thanks! Seems I'm pretty iCompatible then. Glad you liked! :D

Managed to try it myself on an Android of some description. Quite slow, but buttons and that worked. Which is great, but doesn't help me fix the HTC Wildfire problem. Might just have to like&lump that bug. :s

[benetonmovie]

It doesn't work in Google Chrome 19.0.1036.7. I get the following errors in the console:

Viewport argument value "device-width;" for key "width" not recognized. Content ignored. (golfingblock.html:7)
Viewport argument value "1.0;" for key "initial-scale" was truncated to its numeric prefix. (golfingblock.html:7)
Viewport argument value "1.0;" for key "maximum-scale" was truncated to its numeric prefix. (golfingblock.html:7)
Viewport argument value "0;" for key "user-scalable" was truncated to its numeric prefix. (golfingblock.html:7)

[YellowAfterlife]

It doesn't work in Google Chrome 19.0.1036.7. I get the following errors in the console:

Viewport argument value "device-width;" for key "width" not recognized. Content ignored. (golfingblock.html:7)
Viewport argument value "1.0;" for key "initial-scale" was truncated to its numeric prefix. (golfingblock.html:7)
Viewport argument value "1.0;" for key "maximum-scale" was truncated to its numeric prefix. (golfingblock.html:7)
Viewport argument value "0;" for key "user-scalable" was truncated to its numeric prefix. (golfingblock.html:7)

To note, those are not errors. They are warnings, caused by slightly incorrect way of writing <meta> tag in GameMaker:HTML5.

[Desert Dog]

Thanks for the report. Not sure what do do about that. Is this, like, a bug report that Mike D should know about?

I have chrome 17.0.963.46 (which says it's up-to date) and it works fine.

[Dangerous_Dave]

Doesn't load at all on my Android phone (LG Optimus GT540). The loading bar goes right across, then the screen goes grey. Weird.

Cool game, though

[Desert Dog]

Hmmm, thanks for the report.

The first room( well, I have a rm_init, but that goes instantly to the menu) is a wide room. 3 screens wide, and I'm just using the view to shift between them. Maybe that's what is causing the grief. (somehow). I'm not doing anything fancy in those first rooms, otherwise. Ah, well, cheers!

[GameDevDan]

I've gotten to wondering if I shouldn't make the finger point in the opposite direction of the ball, so the player can see where he's hitting. What do you think?

Definitely a good idea. My finger keeps getting in the way on my iPhone. Runs fast though

Played through all the levels on Chrome, 'twas fun. Well done :D

[thegame]

Well... If you make the finger go the opposite direction of the ball you can't aim away from the side of the screen. Correct?

[Desert Dog]

I do have a 32 pixel buffer on the edges, but yeah, there is that. Well, I've got something to chew on. An idea would be to make it you can click&drag ANYWHERE, and it'd figure out the initial click spot, and where you are now, and aim from that. But that isn't so intuitive.

Thanks for checking it out&testing!

[mazimadu]

Very, very nice. Tested it on my Herotab C8 and it works very well. Addictive and extremely playable on a tablet.

Now if only yoyo could fix the sound issues with GMHTML5. Then we will have true tablet gaming.

[Desert Dog]

Yow, I love not having sound. :D O.k. I'm lazy, but phones often have limited(and expensive!) internet connection.. sounds files are comparatively LARGE. Right now this game is under 1 mb (I think..) add a music track+a few sound fx, and we could easily be hitting 3+ mb. So I think design wise, a web mobile game is fine without sounds. (if the game is really good, make it an app!)

Thanks for testing!!