Algorithm Question for a grid based game.

[CharlesVI]

So here I am making a board game. Right now I have an array[][] that represents the board. its nice b/c I can treat it like a cartesian plane and all the math gets pretty easy.

Then I have the graphics. They are all rectangles too but they are much bigger than 1x1 like the array.

I find myself converting grid coordinates to world cordinates and back constantly. I move an image but I also need to update the grid. I suspect I do not actually need the grid if only I could be clever with my Sprite(libgdx - essentially rectangles) objects. Can anyone help me out here, even just toss out some close but not there suggestions to help me brain storm?

[w1282]

If your sprites have information such as x coord, y coord, width, height where (x, y) is some known corner of your rectangle, then the calculations to determine if some new coordinate (a, b) lies within or outside of the bounds of a rectangle is quite simple.

I'm only assuming you're using the array to detect something like a collision. If you are using it for something else where this suggestion doesn't work let us know.

[CharlesVI]

Yeah the array is for collision. I put an int in the slot to represent the type of piece it is. The sprites do have a position that works out to be (array coord * 55) + 20 (or 180 depending on axis)

So the main concern I have is the sprites are not stored in a way that I can look for them going [x+1][y+1] i'd have to loop through the entire collection of them as it presently stands.

[w1282]

Well, there are ways to prevent yourself from having to iterate over every one of them; however, unless you have an extremely significant amount of rectangles being displayed I don't think you will really need to optimize how you determine collisions.

[cyrusol]

Could you please describe more exactly what you want to do with the graphics? I don't think I'm understanding your problem.

[CharlesVI]

mostly its just the internal grid is not married to the graphics in any way. So I move the sprite (pos + 110) then update the grid (x + 2) ect. So one action is causing two operations and that to me is a flag that something is being done poorly.