In the past, I tried to make an effect like this to see how it would turn out...RAM clear.  Instantly.
And for a game like this, which can get pretty complex...
It's possible, just highly impractical
Think about it.  How many times would I have to make the program loop through (TWHG loops to 96 ~4 times, which slows it down tremendously) to pxl-test all of the balls, and adjust any directions and such accordingly?  On top of that, I would have to put in a separate loop to find if something changed or not and update the positions.  The thing about walls...they're static.  The balls aren't.
(not to mention how much space it would take...)

I plan on adding some rather simpler stuff than that.

Yes, it's okay if there isn't collision. Hope to see an update soon

What you'll probably see is little things on other boards that are part of it...like the menu thing was my attemt at making a menu sysem that didn't take up a huge amount of space, or the character explorer which I've been using for months and it just occured to me yesterday to post it.
The update may not come for a few weeks for all I know...but it will probably be an unfortunately big one...I plan on doing something like the mockups as soon as I'm done with the menus.

EDIT speaking of mockups...look what I found

:O Fail

I was busy last night, and I think I have the menu done, the backgrounds for the different modes done, and the game about menu-ready.  So now, I just need to put it all together

In the next few days...coordinates inflated by 64 take me a while to work with for some reason...

I was busy last night, and I think I have the menu done, the backgrounds for the different modes done, and the game about menu-ready.  So now, I just need to put it all together

In the next few days...coordinates inflated by 64 take me a while to work with for some reason...

yay! I hope a menu comes soon, what options available at the moment?

Quote from: DJ Omnimaga on November 30, 2010, 02:47:06 pm

coordinate inflated by 64... what do you mean? Do you mean ball positions is 64 times larger than it appears on screen for more accurate collision detection?

Not quite.  It was how I figured out to do the varying angles the balls go at.  The speed is an inflated number as well.

Quote from: ScoutDavid on November 30, 2010, 03:58:37 pm

yay! I hope a menu comes soon, what options available at the moment?

See for yourself ↓↓↓
The first one is the menu interface, doesn't store anything yet.
The second one has potential backgrounds for the different types.

And yes, these ones are real

At this point, I'm planning on taking out the progress bar altogether.  I tried adding something like it to the four-part field and it bugged and slowed down quite noticeably...

Any other options ideas?

Loks really good, but doesn't the program quit when you set options?

You select quit.  After setting an option, it goes to the options menu.

On another note, how does one remove a poll from a topic?

Remove, on the right I think.

If not, tried 'Add a Poll'

This is looking great!  I think ball collision would actually *detract* from the experience, since 4 or more balls it might become really difficult to predict where they are going to be traveling, and it gets very difficult I am liking the balls moving at different angles though Everything is looking awesome! ^^

The second screenshot waits until the person press any key, and if it's not 2, 3 or 4, it quits.
The menu is planned, I just did the thing in the second one to clarify which mode went with which type.  In the menu, it's determined by the option "Types of balls".

It looks like I'll have to change the code so it redraws everything every frame, unless there's a way to do two extra buffers or store a greyscale background externally...
Or i can have it xor the balls back into nothing, I'm trying to think of a fast way to do it so what happened to TWHG (3-4 giant loops per frame) won't happen to this.

Update: I just need to fix the display issue ↑, involve an appvar and put the game in the menu.
The bar on top is done with, it slowed it down too much (now with greyscale and such) and it interfered with the design of the 3-type/4-type fields.  It looks a lot cleaner without it.
(One would hope the person would know when they're close to winning, anyway )