There are a couple of things that need clarification here. First thing, the cell size of your world is needed as well as the size of the tile images and the size of the image for your character. Second thing, it is unclear if your character is to be moving adjacent to or actually on the tiles. Next thing, a brief description of what your code is supposed to be doing (as least a run-down of what each line is intended to do for one of the keys -- be specific;). Then, a brief of which direction each key is intended for ("d", "e", "w" and "f" are not standard movement keys) -- like "'f' is used to move right", etc. As the code is right now, it appears your character, if moving at all, is moving on the tiles and only along the diagonals. This diagonal movement (1) is not standard and (2) was not mentioned; so, I feel it may not be the type of movement that you want for the character. All in all, posting the code that creates your world along with image sizes would help immensely along with a detailed description of how your character is supposed to be moving (what each key is intended to do and what each line of code for one of the keys is supposed to do).

Cell size is one pixel per cell, I can't find the pixel height and width of the image at the moment, but the tiles are diamond shapes. The tiles are all touching each other at their edges, and I think the detect method object isn't working because it's looking for things in rectangular image areas. The box is intended to move diagonally ON the tiles, with the center of the box being on the center of the tile by the end of the keypress. "w"moves the box up and left, "e" moves the box up and right, "d" moves the box down and left, and "f" moves the box down and right. (I can't get the image size right now because my schools system prevents me from obtaining certain properties of downloaded files) Sorry for being so vague.

As the tiles are diamond shaped, the overlapping of the images would be presumably in a state that the corners of one would coincide with the location of its adjacent tiles (the center point of the adjacent tiles). Therefore, you do not have to go all the way to the edge to detect an adjacent tile. I am referring to the offsets provide in lines 17, 37, 57 and 77. One or two pixels offset would probably be sufficient; however, half the distance offset of what you are currently using would work fine (change '/-2' and '/2' to '/-4' and '/4'). This should limit the number of possible tiles detected at any point to one. To code you have given is a bit bulky; plus, the behavior of the character might be a bit off if more than one key was held down at one time. Adding 'else' for subsequent key checks (lines 18, 38, 58 an 78) would only cause some keys to be favored over others, which is not preferable. We can deal with both these issues by making sure only one key is down before moving:

Sorry. I was mistaken in the above. The check on line 10 limits the number of tiles that could be detected to two -- which will not work. The other tile detected will be the tile that the character is current at. If you import java.util.List into the class you can replace my lines 10 through 12 above with the following: Here, line 4 will remove the tile the character is currently on from the list created on line 3.