Why is your name DeafTV? 

After the A* calculations are done you have a closed list.  This is the list of all the tiles that you can reach.  cycle through those and find the one that is closest to the destination (aka: your tree).  You can use a simple calculation to figure out how close it is to the destination like Math.abs(nX - dX) + Math.abs(nY - dY);

Here's how I would do it, in somewhat pseudo code:

A Node has an x, y, cost, and parentNode.  parentNode is the Node that got you to this Node.
Create a 2d array Node nodeMap[][]; equal to the width and height of the map (in tiles).
Create an ArrayList<Node> openList = new ArrayList<Node>();
Create another ArrayList<Node> path = new ArrayList<Node>();
Add your starting tile to the nodeMap in the X and Y coordinate, set the x and y, cost = 0 and parentNode = null;
Add it to the openList, openList.add(nodeMap[ x ][ y ]);
Now your loop while(!openList.isEmpty()){
   for(int n = 0; n < openList.size(); n++){
      examine the possible reachable neighbors of openList.get(n)
      if this node already has data (check the parent value), see if your cost is better and update it.
      add them to the nodeMap and fill in the values
      Then add that entry to the openList.
      remove the current tile from the openList, openList.remove(n);
   }
}
When you've gotten to this point you've mapped out all reachable tiles.
If the nodeMap[destinationX][destinationY].parent is null, you can't reach the tile
   so scan through your nodeMap and find the tile that is closest to the destination and assign it as the destination.
Otherwise we'll start at the destination.
Work your way back, from destination parent (in nodeMap) to parent to parent until you've reached the start node.
Using 0 as the index will ensure it gets placed at the beginning of the list, path.add(0, thisNode.parent);
Now you have an arraylist that is traceable from start to the destination (or close as you can get to the destination).

If you can't reach the tree, it shouldn't be in your open list.

Examine the tiles in the closed list, calculate the distance to the destination and pick the one that has the least.

If you're using any sort of timer that updates (or allows updating) of the sprite position when time's up, then you can just use the speed of the sprite to calculate the new timer time.  Each sprite would need it's own timer, but that's normal.

I completely understand what 65k is saying.  I thought about this in a Street Fighter scenario.  Maybe your custom character starts out with flat speed, strength, etc...  As you progress you can better fit your character to your style of game play, Increasing one aspect at the penalty of another (each level up, allows you to move x aspect points).  Some prefer fast players with combo moves, others the big brutes, and then there's the lamers who prefer sitting in a corner throwing shuriken the whole time.

I think it's a good idea, as long as it doesn't become a game of rock-paper-scissors (strength beats speed, speed beats stamina, stamina beats strength).
 

Works fine here with Ubuntu 10.10, however you failed to mention that arrow keys moves and rotates the camera.

>> 8 gives you green, because green starts at the 8th bit (it's address, if you will).  >> shifts in bits,  so to get red it's >> 16 (3rd byte) and so on.

33, Caucasian, Male, heavy metal & techno.

This whole time I was passing 'this' to it, saving it as 'that'.  I never knew I could use that.createImage().  Thank you for the pointer.

Oh My.  I didn't know this existed...  Time to usurp Zove's post:
http://web.archive.org/web/20041206233914/http://gbeebe.com/index.php?date=2004-08-11 When I aspired to do a web comic.
http://web.archive.org/web/20030803062838/http://www.gbeebe.com/ Hey, my old logo!

That was meant as a joke, actually, I think everyone understood that.  I was going to reference Microsoft in the joke, but figured not everyone has the hatred that I do towards them.

The look on your face when you actually do it... oh, wait...

Story line/Plot, Mini/side quests, Rare Items with cool powers.  I've played some decent RPGs that didn't have great sound or music.
I also think that if you can keep the player involved, for say 50 total hours, until the game is won, you've done a good job.

And what happens when you get some Read/Write access error, due to some bad multi-thread programming.  Could you accidentally split the atom?

where is g.clearRect(0, 0, width, height); ?

... As long as it's not another Phantom Console.

but it's working fine... maybe it's an OpenJVM thing.  I have to try it on a windows machine.

I had setIgnoreRepaint(true); then called repaint(); in the main loop each frame.  Kinda' the same thing, I guess.

My Paint method looks, like this:


Note:  My main class extends Frame, and a canvas is added to it.

Well, IMHO, I think they're wrong.

Yea, I was just being cheap.

I would do something to what ra4king is saying, but I would make a Followable interface with .getX() and .getY().  Have any class that you want to be able to follow implement the interface.  You then could do something like this:



You could then have fancy stuff, like a Camera class that can be followed.  It could move over to where something is going on, and then move back to Player1.  etc... 

It's java, so it's all up to your imagination.

Yea, I've thought about that too, but then I get into the physics behind it and deem it all impossible with the electricity outside being paused in time and not being able to reach the computer to make it work.

I love it when the alarm clock goes off waking me up early, walk towards the bathroom to take a shower, pause for a sec... run back to the bedroom, grab my cellphone, pull up the calendar...  Today is my day off!   And I'm up before the kids are.  Time to get in some decent programming hours.  I love that feeling.  But then the wife comes down stairs shortly after and asks "Have you been on that thing all night long?"  

I do the whole laying in bed, plotting the next couple of procedures and coming up with solutions to problems, I've even coded in my sleep.  I remember waking up in the middle of the night thinking "that would totally work", but I never get up to type the code... If only I could type in my sleep.

When I was younger, I used to gauge what day it was based on the amount of code that I had.  I remember the feeling of sadness when a 3 day weekend was over and it seemed that I had accomplished squat.  Getting home from school and opening my math book to pull out a quiz that I had jotted pseudo code on the back of, to implement it.  A lot of my coding is done this way now.   I'll bring home, from work, drawings, diagrams, formulas, pseudo code, game maps, etc on blank paper swiped from the fax machine.  When the wife and kids are in bed it's code time.  Sometimes it'll be midnight and I tell myself "I can wrap this last bit up in a couple of minutes before bed" then when I get it done it's like 3:00.

I assume that I'm not alone, when deciding on a super power, I'd pick the ability to create a bubble around me with about a 6 foot radius.  Everything on the inside would work as normal, everything on the outside would be paused in time.  I could code forever and sleep as much as I want, and still have time to do the things that I must do.

If you already know how to tell if 2 images at given coordinates overlap, then scan the overlapping pixels in each image in that box, using Image.GetRGB().  If both overlapping pixels contain a solid color then the images have collided.  You could speed this up by making an array of 1's and 0's for each image prior to playing and checking those for collision.  I haven't done this in Java, but from my experiences in other languages, pixel perfect collision is very costly, especially if you have lots of blank pixels in your image, and many on screen images to check.  There are other shortcuts that that aren't as costly, such as bounding vectors (an array of points that outline your shape).  Do you necessarily need pixel perfect collision?

It's an onboard video card in my linux machine     I installed in on my Acer A500 tablet, it works great on it.  My 5yo son likes it.  A few questions though:  When the people move, the appear to be "animated" so they aren't 1x3 pixel sprites are they?  What does it mean when it says "slow down"?  Did I manage to get a power up, or is it telling me I'm going too fast?

meh, new error:

Can't play in linux?

It needs to have Component so i can use createImage(), and didn't want to rename some of the methods, but that's what I'll do.