Bay 12 Games Forum

Thank you all so much!

Here is the new plan:

I'm going to stop work on WorldJem until I've mastered classes, structs, and pointers.
Then, I'm going to rewrite the whole thing with the new information.

Please bare with me through this learning process.
I promise it is necessary for the future of my projects.

I'll come back to this as soon as I know all of these things.
Hopefully it will only take a few days.
The major problem, is that my RL is getting pretty busy lately,
so it might be a while before I have time to put towards this.
I'm going to start picking apart the examples people have given me,
and learn them in and out.

I can do this.

Oh. I think I know what you are asking.

It is called:

int water[][][];

Okay?

I have an array called wat[150][150][150] that stores all which is water.
Different positions in this array contain the information, the rest have zeros in them.
How would I go about adding the positions to the list which need to be tested?
On top of that, how would I add a new tile to the list?

Can I give you the information you need, and you set up a system for me?
I will give you due credit.
I'm just not ready for a headache right now, and I would really like to get on with this.

I can keep programming as is, and when the system is ready,
we can add it in in place of the looping position system, boosting the FPS.
I don't understand a ton of what I see down there,
and I'm won't be in the right mindset to tutorial-chug any time soon.

Sorry everyone.

I don't think I'm up to it.
If that is the only way, it is going to take me forever.

The only way I could see that happening, is if somebody else helped me with it.

Otherwise, I'd rather drop super-dynamic water for now, and only have these calculations happen when
water is upset.
So a bunch of pre-existing lakes, and if you F with any of them,
there will be water flowing at around 10 FPS until the water resolves itself.

My game already does that sort of.
It tests each tile and depending on the tiles around it, a change is made.
No movement happens, the tile is deleted and replaced.
That doesn't slow anything down though.
The part about testing each point is the slow part.
It has to test EVERY point in the local map (150x150x150 tests) to see if that tile is unstill water or not.
The test goes like this:

If this tile is water and has moved recently, do something to it.

That simple test, applied to every tile, even if you leave out the part where it does something, takes too much time.
The only way I could think of is that it doesn't have to test the points, it just knows where they are somehow.
That would be super complicated, and take weeks of playing around with to get working right.
I have no experience in these techniques, so I'm hoping there is a better way.

What I said is pretty wrong.
In fact, the opposite is true.
Water is super-uber slow right now.
Any ideas?
I've been brooding over the code for two hours and I have only remorse.
I'll have to think of something.

They could be naturally occurring and a good source of food.
I like it.

I fixed a ton of stuff since then, before creating a new, more painful problem.

The gravity is fixed.
The tags are fixed.
A noblock tag was added. (Tree trunks and orange have it now)
Some other misc stuff.

Frame rate has been reduced during regular game mode so you can actually observe things falling very fast,
instead of instantly.

Problem:
During falling, turn based mode doesn't work right.

I'll upload when I get it all fixed.

EDIT:
Great ideas everyone!
Keep 'em coming!