#andengine

.btn { background: #3498db; background-image: -webkit-linear-gradient(top, #3498db, #2980b9); background-image: -moz-linear-gradient(top, #3498db, #2980b9); background-image: -ms-linear-gradient(top, #3498db, #2980b9); background-image: -o-linear-gradient(top, #3498db, #2980b9); background-image: linear-gradient(to bottom, #3498db, #2980b9); -webkit-border-radius: 28; -moz-border-radius: 28; border-radius: 28px; font-family: Arial; color: #ffffff !important; font-size: 20px; padding: 10px 20px 10px 20px; text-decoration: none; } .btn:hover { background: #3cb0fd; background-image: -webkit-linear-gradient(top, #3cb0fd, #3498db); background-image: -moz-linear-gradient(top, #3cb0fd, #3498db); background-image: -ms-linear-gradient(top, #3cb0fd, #3498db); background-image: -o-linear-gradient(top, #3cb0fd, #3498db); background-image: linear-gradient(to bottom, #3cb0fd, #3498db); text-decoration: none; color: #ffffff !important; } .conts img{max-width:500px;} .conts a.but{margin-bottom:15px;} .conts a.btn{margin-bottom:25px; display:block;} .conts a.btn:first-child{background:none;border:0;}

Download Now

The Walking IronRam,

It is a colossal walking weapon, why their creators didn’t use wheels for it? It could fall to its side anytime! Anyway, don’t let it hit you with its front side, it will definitely crush you to pieces in a single pass.

That might *sound * like a silly question. After all whenever something is on camera in your game you should hear a sound for whatever action that object is doing i.e. water drippling, a rock falling, an enemy patrolling, a car passing by, you get the point. Well, turns out that constantly checking if a given object in your game is on camera and fully visible is very resource intensive specially if you are targeting your game for a mobile device. Also letting sounds run wild would cause a mess.

My solution is far simpler. The player has an area of effect. A Light radius if you will. If your player gets near an object you should hear the sound. How to do it?

On the update loop of a given enemy, object that should constantly make sounds. Do a substraction like this.

-------------------------

visibleX = Math.abs(Player.position.x - Enemy.position.x); visibleY = Math.abs(Player.position.y - Enemy.position.y);

if ( visibleX <= 20 && visibleY <= 20) SFXManager.playSound(enemy.sound);

-------------------------

So over the last 3 years I’ve been a user of this game engine for Android. I believe it is a very good entry point for most novice game developers out there, I found great posts both in the official forum and stackexchange, some good books, some good and useful examples. 

However on the less brighter side I am not quite sure why the engine seems to be stagnant. It feels a bit dated by now. Performance could be better. It could definitely be better documented by now and with more extensions, maybe even learn / borrow a thing or two from LibGDX as in being able to port to iOS or PC. Its main site well hmm it is not updated frequently most blog posts by the developer are from months ago. The engine needs more love no doubt.

Don’t get me wrong it is a good engine and has produced some very good quality games such as Greedy Spiders, but by the time you finish your game you feel like you have a niche market and  you will need to learn again another engine, that allows you to put your game out there in more places than the Google Play store.