﻿BASeCamp BASeBlocks Development log

Started far too long after the project was started (Sept 30th, 2010)

Oct 07 2010

Game is coming along nicely; recently added:

* Tally screen at the end of the level
*"Demo" mode, which is atm an option on the menu. will be removed, as it is mostly used for the next item...
*gameover and "demo" screens, whereby a certain "gameover" level is played, with appropriate music, of course (well, it will be).
Ideally, this will be a level with blocks that spell out gameover. Not sure how to get that working, either I can "hard-code" it or I can use something like a graphicspath.

November 12th 2010

Improvements: quite a number of them; fixed a few bugs here and there in various places, specifically tweaked the tally and gameover "dialogs" (the boxes in the screen when the rest of the screen is "darkened", etc)

New: "powerups" these are a derived GameObject type (GamePowerup) these are spawned randomly by normal blocks at the moment from a pool of Types. currently have three; one makes the paddle larger (and gives you points) one makes the paddle smaller (and you lose points) and one that I initially made to test image animation for powerups (which now works, both the paddle grow and shrink powerups also use it).

new: a new paddle, the "sticky" paddle. As I write this, it is actually a derived Paddle class, however, I have realized that this will not work in the long run.
The various "powers" that the paddle can have- being sticky, perhaps shooting freaking lazers, etc should be cumulative.

Therefore in the last 5 minutes I have conjured up a "fix" for this in my head; rather then derived Paddle classes, instead, a new Interface- "PaddleBehaviours" of which the base Paddle class stores a collection and fires "events" into said interfaces, with the appropriate information of course.

And it is completed; the iPaddleBehaviour interface is defined, The base "Paddle" class is calling into a List<iPaddleBehaviour> for "enhanced" behaviours, and there is a "StickyBehaviour" class that works perfectly as well.

next up: it already overrides Draw() but the next step will be to create "overlays" for each paddle "enhancement"; for example, perhaps a some cannons sticking out of the paddle for the laser behaviour (and shooting behaviours) and perhaps... a layer of slime for the "sticky" paddle. It's an open court!


But first, another thing has popped in my head: as it is now, the BEhaviours are literally hooking the Click event of the
main picturebox; ideally, there would be a more  generic way of receiving notifications about game events.

One can feasibly expect the following inputs:

Move left
move right
move absolute (fired to move/when moved to an absolute location (this would be the case for mouse movement)
Button A (for releasing the ball from sticky mode, etc)
etcetera buttons

//therefore, this could be a interface:

//iGameInput
//



edit: I finished a working implementation. It doesn't use an interface, but instead has a series of events exposed by iGameClient; the form implements this interface and fires said events when the mouse is moved clicked, etc.
works well. This will make adding keyboard controls and stuff easier later on, as I can just add a class that recognizes the appropriate inputs and fires those events as necessary.


other ideas: more powerups, more blocks, (of course) paddle behaviours, etc.

probably make a change so that the various powerups don't have an equal chance to spawn; make some powerups more rare.

November 15th 2010, 9:06PM

added the above self-suggestion: powerup chances are now "weighted"; ideally, each block could also have a varying chance. For now I leave it as is.
Also, the paddle being used is still subject to the "sticky" behaviour; this should be changed to a powerup of some sort.

I am zipping up the project as it stands now and uploading it to my site to allow for some previewing by a select few; note however, that
there are a number of "testing" bits that I can't be bothered to change atm; for example, the StickyPaddle behaviour mentioned above, which can be found on line 192 of BCBlockGameState:

PlayerPaddle.Behaviours.Add(new StickyBehaviour(this));

That in and of itself (the "StickyBehaviour" class, that is) has a small but mostly asthetic bug that I have yet to fix as well. This isn't even to note the fact that I am yet to add quite a number of different blocks, as well.




Music/Sound information:

All Music and Sound is loaded and managed by the "SoundManager" class, found in SoundManager.cs.

On the downside, however, many of it's methods are not exactly polymorphic in a way that would facilitate replacing the core library
with another; some of them return "ISound" and "ISoundSource" interfaces as defined in the wrapper library. For shame.

So, what would be necessary to replace the library with another? More then I would like to admit. ideally, of course, all the changes would be only in the SoundManager class; but since the SoundManager class 
contains a number of methods that return Sound library objects. These are used in various locations, and the return values are also used by the main game in a few locations.

One concept  that might work would be to replace the ISoundSource and other interface returning methods so that they instead return an abstract class; this abstract class can be derived from in new Sound-oriented objects for each "type" of sound library; for example, FMOD could have it's own "Driver" class that derives from SoundManager, and has a nested class
that derives from the abstract class. It's probably possible to jury-rig it to use another sound interface, it will probably require modification in the main program. Later versions will likely implement a better Sound framework that supports at least two sound "driver" objects; one for the current irrklang library, as well as the equally powerful (if not more so) FMOD wrapper I found. Further "wrappers" could be added later for other wrapper libraries.

(perhaps even conditionally compile some of them depending on platform, if that is possible).



*ADDITIONAL INFORMATION ABOUT MONO/LINUX*

Aside from the clear fact that the irrklang sound library has no .NET wrapper for Linux (which means t hat to get it to compile will mean vast changes and commenting out/removal of a lot of code dealing with the sound)
there are a few other considerations.

Application Data folder: inside the zip, there will be two directories; a "BASeBlocks" directory, and a "Appdata" directory. the contents of the Appdata directory should be copied to %APPDATA% on windows systems. On Linux systems, 
the contents of the directory should be copied to /home/usr/.config .

With Linux, you might need to edit the INI file; probably not though, as I just changed it to recognize %APPDATA% and replace it regardless of wether it is running on windows or Linux.


Wednesday, November 17th 2010

Finally "buckled down" and rewrote a new SoundManager class that uses a more "plugin-like" architecture; the SoundManager accepts a instance of a driver interface in it's constructor; that interface is used to load sounds, and the interface returns further objects that it's wrapped into neat little interfaces.

The idea here is so that even when the sound libraries in question differ greatly in how they are used, I can use it the same way for all of them.



Also: new credit where credit due: many new block designs are in the works by Mulreay; 
from the sounds of things they should be pretty good, and make a nice addition
 (and a motivation for creating) further block types.


*Yet more Linux info*

as the new SoundManager (correctly dubbed "cNewSoundManager") is now written, and I have created "driver" adapter classes so that it can use either the same irrklang as always or it can use nBASS, it's now
feasible to consider Linux support; this is partly due to the fact that while nBASS isn't specifically written to be Linux compatible, Mono has some things that can be done
so that imports from the win32 bass.dll are instead being imported from bass.so (from my understanding, .so files are the equivalent of dll files on linux).

Steps:

First, Of course, the Sound system will have to be Set to use nBASS. this can be configured via the INI file, which can be found
in the application data folder I noted earlier (%APPDATA%\BASeBlock\BASeBlock.ini on windows, /home/usr/.config/BASeBlock/BASeBlock.ini in linux- replace usr with your user name, of course)

Once the game is set to use the BASS library, another change needs to be made; as I noted the nBASS library tries to import and use functions from "bass.dll". however, we can simply remap those functions to bass.so on linux and they will import fine.
The mechanism to do so is to use the Mono DLLmap feature (info here: http://www.mono-project.com/Config_DllMap)

As it stands now, I've created the BASeBlock.config file with the appropriate block:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<dllmap dll="bass.dll" target="bass.so"/>
<dllmap dll="irrKlang.dll" target="irrKlang.so"/>

</configuration>

this "redirects" the attempts to load "bass.dll" to "bass.so"... 

actually this could probably work with the irrklang library as well, but that warrants some further testing. Might require a config file for the actual
wrapper dlls instead (for example, irrKlang.NET2.0.dll (a .NET library) would need irrKlang.NET2.0.config that contains the second <dllmap> tag shown above.


November 18th 2010 10:31 PM

Modified "BoundedMovingBlock" so that it no longer impacts balls multiple times... at least not as often.


Dec 8th 2010 12:26PM

TODO: add StickyPaddle powerup; add Powerupblock that drops a specific powerup (displaying the powerup image on it's face).

Optimize... it runs far to slowly. No idea how to speed it up but there has got to be a way.


Dec 24th 2019 4:41 PM

managed to greatly increase the speed of the game by performing some refactoring; as it was, if an animated block needed to be redrawn, then all blocks would be redrawn.

so- if a single waterblock was in the game- poof. Every single frame, every single block was redrawn.

Now it is much speedier, and the framerate for the default level is around 80fps, and that is with the debug.Print() statements present.

Dec 27th 2010 5:54 PM

Adding Plugin support via a new interface. Good thing I wrong the "LoadedTypeManager" class to be generic and able to manage various types, rather then making a more specific
one for iLevelBuilder.


Dec 28th 2010 3:24AM

Doing further work on a basic Updating architecture. The update information works on the server side (from what I can tell) and I even have a somewhat-working Visual Basic 6 form that acquires the update data.

Creating a C# version should be pretty easy. It should support the following:

Viewing All available Updates
Viewing updates for a particular game (or set of "games") (gameid corresponds 1 to 1 to a application program, so BASeBlock LevelBuilder "Packs" (I'm under the crazy idea that they might be worth distributing separately) could 
be "filed" under a different ID.
ability to check for and start an update in the background with a simple function call; the form would then be simply a small progress bar, perhaps even with a Notification icon.
this will be integrated into each application- that is, BASeBlock and BASeProgramX will both use the same Code .cs class for updating, and they will probably both accept say a /doupdate or /update switch,
but there will be no need for a central "download manager" (unless I create that as yet another separate application, but it won't be necessary).

January 19th 2011 11:06 AM

Work has slowed down on BASeBlock somewhat; although it's more likely I've simply forgotten all the changes. I made some changes to the bobbingtextanimator on the intro screen, the sizing is now more
consistent even with different amounts of text (which was a necessary change since I also made that text be randomly selected from a larger group of strings). I added a "Demonblock" which shoots a new Fireball entity, and I have made a seemingly innocuous change that caused the "mysterious lose life for no reason bug" to appear seemingly out of nowhere. I changed the rayblock so that it can selectively shoot out of any of it's four sides; as well as making some architectural changes to the way IsTempBall was handled in the ball (previously it was a variable, now it is a lambda that returns true only if there is one or more TempBallBehaviour objects "installed" to that ball.
That appeares to be what triggered the issue, but now that it's more common I may be able to trace it down once and for all. The alternate solution is the "brute force" it, and actually look on every frame wether we have any balls, but I'm not sure if that would be ideal.

February 07 2011 4:29 PM

Added Up and Down arrow usage to the cheat input "dialog"; it now navigated through recent entries much like a command history.

February 08 2011 6:07 PM

Spent the last three hours trying to get BASeBlock working on my laptop (via a installer)
There seem to be some strange issues during load, originally it crashed hard during the bootstrap (splash screen) but now it handles some ReflectionTypeLoadExceptions that occur for seemingly no reason.

They seem to occur when the LoadTypes() method of the LoadedTypeManager class tries to iterate through the types of the BASeBlock assembly itself.
I hacked in a fix by making it manually check afterward (in the initgamestate) wether the Levelman list was empty, and if so it simply adds in typeof(defaultlevelbuilder) and typeof(ArkanoidLevelBuilder).

Would like to get to the bottom of the typeload error, though. It might be related to how the assembly references DirectInput, but my laptop doesn't seem to have the assembly present to load.


Fixed Sound volume bug; was using BASS.BASS_SetVolume, rather then setting the channel volume.

Added Terminator Paddle Behaviour and Powerup.

February 10 2011 6:48 PM

I noticed a pattern emerging with a few powerups; namely, I would have a iPaddleBehaviour implementation that gave the paddle a specific power, and 
then I would create a power up that would instill that behaviour to the Paddle; I have adopted this "pattern" into an abstract generic class; as it stands now it still needs to be derived from in another class, but now there is no code repeating in each instance, and each
derived class is no more then a few executable lines.

Wednesday February 16th 2011 8:51 PM

Finally decided to tackle some of the issues occuring when attempting to install on other machines (such as my laptop). Some of the issues had been fixed, but a good summary:

-Sound volume refuses to stick to computer's volume, and continues to max out the system volume (not pleasant on a laptop, let me tell you)
-Update "applet" refused to work at all; would merely state that it encountered an error attempting to execute the file, without downloading it.
-Some pretty major bugs related to my use of reflection (specifically, it seems that although I was able to load BASeBlock.EXE fine to start the program, I couldn't load it
for reflection-based purposes because I was missing some dependencies. The Fix was to actually remove those dependencies from the project entirely (I wasn't using them)
-The Splash screen, when shown as the about box, wouldn't show at all but would steal the focus.


I have so far fixed all of these issues; the sound "bug" was a bug in the BASS sound driver class, I was setting the master volume rather then the channel volume when playing sounds;
The update applet was trying to use the GetTempPath() API, but it kept giving me an empty string. I assume it worked in the IDE for... well, damned if I know. But I have very little doubt that 
this wasn't the cause of at least part of the update problem.
Splash screen "fixed" by making it set it's opacity to 100 right off when shown as the About box. Bit of a hack but oh well.

new issues I noticed:

-Cheat input "dialog" seems unresponsive

Tuesday March 1st 2011 12:01 AM

Finally "buckled down" and created the Editing form; it at the moment has very rudimentary Editing capabilities- the ability to add new blocks, drag blocks around (including the ability to snap to a grid) drag a group of selected
blocks (selected by dragging a box around them) as well as using a propertyGrid to change the properties of the blocks. This adds a new dimension to the implementations of blocks, though, since
they now should expose "interesting" features through that propertygrid. Right now many things cannot be edited (such as brushes and pens), which leaves a bit to be desired.

Still needs better ability to Edit the levels themselves.

Wednesday march 2nd 2011 12:05 AM

Fairly good progress on the editor; now has ability to edit the balls as well as blocks. Still needs some tweaking about to try to get the balls to "highlight" properly (size of highlight is wrong).

Also added a quick "behaviours" form that allows the editing of a Ball's behaviours. Seems to work a treat, too.

Thursday March 3rd 2011 12:15 AM

EXCELLENT progress on the editor. Now supports editing of Balls, Blocks, provides a flashing indicator of what balls and blocks are selected,
provides a method to generate a level consisting of a given number of blocks. May add a "Paint" routine where pressing the mouse paints
all blocks that the mouse touches a certain colour. Currently attempting to resolve issues with the editor and Animated blocks... and No, I don't mean animation of those blocks. 

the problem with "PerformFrame()" of the blocks is it would require me to construct a BCBlockGameState so that the blocks can "evaluate" their environment. This may be doable (just set it to the EditBalls and EditBlocks and away we go)

The problem with animated Blocks I am attempting to resolve is that they are unmovable; the BlockRectangle can be moved but it only moves the selection flash.


Friday March 4th, 2011 11:56 AM

Even more great progress; I had to recreate the form due to some designer glitching that corrupted it but, it was pretty much just re-adding the same controls
and linking up the events properly. Changed the "level" listview to be more feature-complete; it now shows a thumbnail of the level (AWESOME), and so far the level name, number, and the number of blocks.

also added "auditing" of levels; currently it's fairly simple but the idea will be to have a sort of "subsystem" (set of classes) designed solely for auditing levels. By which I mean, scanning the Set for possible issues. Currently it detects missing balls and blocks, as well as when there are no blocks that can be destroyed (which would mean the level lasts forever).

Additional possible "audits" might be detecting when there are balls but none of them have a non-zero speed, when there are blocks outside the game area, etc.

The "idea" will be to display the errors in a list; allowing the user to double-click on an issue to be taken to the level where the issue resides, or for some of them have a "fix it for me" type of feature that for example adds a block to empty levels, adds a default ball to levels without balls, gives balls speed, etc.

Friday March 4th 2011 9:56 PM

WAY progress... not on the Editor (which is more in the rough polish stage) but rather on executing an idea that was presented to me.
Graham suggested a "Creeper" block, that would move around and hunt the paddle. It intrigued me; more or less, because I had been considering some sort of enemy.
Because the Block "API" (if you will- the way the Block code can interact with the game) is relatively limited in that manner, I decided instead to make a Abstract class, GameEnemy, which would make managing various "States" easier.
A "state" generally indicates how the AI of an enemy will perform; for example, when the enemy is in the "Attack" state, it may be more aggressive, wheras there could be fleeing states, and so forth. Often, these are accompanied by having a different set of animation frames.


So, the GameEnemy base class has several Dictionaries, most of which are indexed by the key of the current EnemyState, that provide state-unique things like the animation frames and the delay times (which are both per-state as well as per-frame).

For a test, I created a Megaman "enemy" that walks slowly using the standard blue sprite, but after 750 frames he turns green and speeds up both in horizontal speed as well as reducing the delay times.

After smoothing out a few bugs, it seems to work like a charm.

I was considering the first enemy to be a "muncher" type enemy, which looks like pacman and whose AI attempts to eat balls. THis would also be a "test" of sorts since
the plan will be to neglect the GameEnemy's Default behaviour in which it uses Image frames, instead going for a Pie shape that animates a opening and closing mouth (like pacman) and can point in any direction.
No doubt I will have to dust off some of my trig skills (particularly since I want the ball to "bounce off" the cruncher if it hits them away from the mouth).

Saturday March 5th 2011 8:13 PM

fixed some long standing issues with the animated blocks, highlighted by the editor (in that DemonBlocks, Black Hole Blocks, etc were all loaded with an empty blockrectangle; seems that while it serializes and deserializes the values properly, it doesn't actually set it's own BlockRectangle to that of the base Blocks. (long story, animated blocks are really
just a wrapper around another block)

The Editor (and subsequently the LoadedLevelBuilder) Now load the levelsets via a new "EditorSet" class designed to make it easier to store stuff that might be editor specific; such as author, creation time, etc- that is,
stuff that would be blatantly irrelevant if I were to place them within the LevelSet itself.

Tuesday March 08 2011, 2:26AM

added a "chomper" gameenemy, as noted earlier; doesn't work as well as I would like. Might not use it in-game.

fixed an editor bug that prevented levels from being saved at all. Also fixed an additional bug that prevented normalblocks from saving properly.

Added a new  "life" powerup that restores "health". This brings me to another issue;

the fact that, in many levels, health is entirely vestigial. ideally, there needs to be some sort of omnipresent hazard that damages the paddle on any level. Perhaps the Chomper enemy
could be adapted to try to shoot the paddle instead of hunting balls?


Friday March 11th 2011 1:23 PM

removed "chomper" enemy (the code is still there, it just never get's spawned) it's just to buggy.

I did add "eye guy" which is a "suzy" from Megaman, that moves in one of four cardinal directions. Basically, it moved in one direction until it hits a edge, all the while smashing right through any and all bricks in the way, it's direction changes if it get's hit by a ball, etc.
also, I made it shoot fireballs while it's eye is open.

trying to enhance the editor- added new classes so that the EditorSet (the class that get's serialized/deserialized) also contains a "cache" of sound data/key names and so forth so it can store sounds that the levels in the set require, and make sure they are "loaded" so to speak when the Set loads. Same for images.
Currently just need to write the appropriate interfaces for editing. Currently going with a ridiculous form-based approach since the PropertyGrid isn't exactly catering to this sort of thing.

Friday March 11th 2011 9:19 PM

Created a new installer. Will test on "Training computer" at work; it should have the required .NET install; with any luck it will work there
(being a relatively "virgin" system it will make for a good test; also, it's specifications are about average for a modern machine, so I'll be able to see if performance is an issue (it's a constant worry, really)


Either way, I have Sound Embedding functional; the UI needs some touching up and polish (and I need to add a similar UI for Images... sigh) But it works (I tested it; the file embedded, and was retrieved successfully).

How it works: 

Since I don't recall adding a lot of comments regarding the how (yet) I put this here mostly for my later refreshing on the topic.

The BCBlockGameState keeps instances of a SoundManager and ImageManager class, which are populated when the InitGameState() routine is called (it used to be a static constructor but apparently Mono didn't like that... although to be honest I've given up trying ot get it working in Mono)
In any case, Playing sound or drawing/requesting images is performed at that level; the various Block classes for example use the ImageManager to acquire Image resources, and the Sounds are requested "by key" via the Sound Manager (which itself delegates the actual playback to a previously defined
"Sound Driver" interface implementation; Currently I've been using the BASS.NET driver a lot, but IRRKLANG worked when I last tried as well. Future versions may include more "drivers".

In any case, sounds are acquired "by key" in that a dictionary/hashtable is kept with a String key being used to lookup the appropriate SoundSource (used to represent a single sound object)


With Embedding sounds in levelsets; there are two things to consider:

During the phase of "editing" when the embedded sounds are defined, those same sounds aren't loaded by the driver; previews may have to be done "manually" if I ever implement them; I'm not to keen on the idea
of forcing Sounds to load during the primordial stages while such sounds are just being defined; perhaps I could create a new instance of the sound manager class, I don't know.

In any case, the data is persisted; basically a Key, some sound data, and the extension of the file (ogg, mp3, wav, etc) When the data is "reconstituted" (via the IDeserializationCallback interface that is implemented)
the Sounds are "loaded" into the static Sound Manager class, replacing any existing items with the same key (which could be used to "replace" sound for specific levelsets, or even be used wit an otherwise empty levelset to merely redefine those sounds for later games during the same session)
this is accomplished by writing the data to a temporary file and loading it that way. It uses the recently (as in just now I thought of it and added it) changed TempDeleter Class used to delete the temporary Zip Directory created during load when the object is disposed to delete the file when appropriate. Generally, this means after the application ends. Obviously
unexpected crashes will cause files to remain strewn about, but hey, fixing that might not be worth it.


Saturday March 12th 2011

"fixed"- or rather, seem to have accidentally prevented- a issue that has been plaguing me all morning.

It started innocently enough; I wanted to run the program on a Win7 computer at work so I could show off my leet skillz... although mostly the splash screen commentary.
So I installed it, tried to start it... And nothing.

For the longest time- it did nothing. And then- System.Net.WebException.


 WTF! I thought. All the code that would raise that error is in a try block.
 
 When I got back to my dev machine- this one,  I continued my tests in a VM. Same problems. and yet, it ran perfectly on my laptop!
 
 It took me a while, but suddenly it clicked- all the computers it worked on had internet- those it didn't work on did not. (which makes sense in a way, given the errors) I disconnected the laptop from the network and tried to start the same install of baseblock I had seconds earlier.
 
 and it crashed. Success, the reason seems to have been found. (although why the hell it takes almost a full minute just to show the splash screen I haven't a clue)
 
 So I fuddled about with the Main() routine, added a extra if() to proceed only if a network connection is detected, etc







[10:59] <+Mulreay> A gaping mouth/eye/black hole that eats the ball and spits it out somewhere else on the game
[10:59] <&BC_Programming> like a warp block
[10:59] <&BC_Programming> I actually was thinking of something along those lines
[10:59] <+Mulreay> yeah
[11:00] <&BC_Programming> but now I have to worry about "how will they be dealt with in the editor" and that... well actually that might be perfectly doable
[11:00] <&BC_Programming> if I learn a bit more about the propertygrid thing
[11:00] <+Mulreay> would be cool
[11:00] <&BC_Programming> going to fix the eyeguy collision code and probably do a setup build for upload
[11:01] <&BC_Programming> um... let's call it a beta
[11:01] <&BC_Programming> wtf I can call it whatever I want
[11:01] <+Mulreay> hahaha thought of another one but would be crazy
[11:01] <&BC_Programming> oh crazy is good 
[11:01] <&BC_Programming> I mean come on I'm stealing enemies from megaman
[11:01] <&BC_Programming> if that's not crazy I don't wanna be sane
[11:02] <&BC_Programming> ...and reading that back I have no idea what I just said
[11:03] <+Mulreay> It enters a block/gate that makes the ball go NUTS it turns opaque and just runs for like 5secs but add double speed, you don't have to hit it, it just bounces around and hits random blocks... 
[11:04] <&BC_Programming> hmm I think I like that but not sure if I understand fully
[11:04] <&BC_Programming> let's say- it's a block right
[11:04] <+Mulreay> yes
[11:04] <&BC_Programming> what happens when it hits a ball
[11:04] <&BC_Programming> or I should say when a ball hits it
[11:04] <+Mulreay> heh
[11:04] <+Mulreay> yeah was thinking there
[11:05] <+Mulreay> The ball changes to say a different type.. I just used opaque for an example
[11:05] <&BC_Programming> ahhh
[11:05] <&BC_Programming> I see
[11:05] <&BC_Programming> so- a new block, and a new BallBehaviour
[11:05] <&BC_Programming> See I already wrote stuff to cover these sorts of features
[11:05] <&BC_Programming> that is how awesome I am
[11:05] <+Mulreay> cool
[11:05] <&BC_Programming> but wait a second.. the ball already is opaque?
[11:06] <&BC_Programming> maybe change to some other distinct color
[11:06] <&BC_Programming> colour*
[11:06] <+Mulreay> The ball then goes crazy and zips around at like 2x speed, you don't have to use the paddle as it will bounce anyway.. probably 5secs or so
[11:06] <&BC_Programming> ok I like this, I do
[11:07] <+Mulreay> You don't have to use colour. I get color, even though it's soooo wrong
[11:08] <+Mulreay> hahahah just thought of something that would be cool, and it's from chatting with you on skype
[11:08] <&BC_Programming> so- let's think this out- so a standard, everyday ball hits this new block, and it get's given- well I guess some new behaviour(I'm thinking  "crazyBall") and what crazyball does is make the ball go faster and when it bounces it doesn't bounce "predictably" and sorta just bounces in a random direction, and it lasts for a specified time and then it is removed
[11:09] <+Mulreay> perfect
[11:09] <&BC_Programming> but there is only one problem
[11:09] <&BC_Programming> and I've had to find silly ways to deal with it- such as with the black hole block-
[11:09] <&BC_Programming> what if there is only one ball
[11:09] <&BC_Programming> and it hits that block
[11:09] <&BC_Programming> if it goes "crazy" it will remove itself right
[11:10] <&BC_Programming> leaving no balls at all
[11:10] <&BC_Programming> ....Actually... come to think of it, that <could> work
[11:10] <+Mulreay> The ball will still be the ball in play... not a new one
[11:10] <&BC_Programming> oh oh!
[11:10] <&BC_Programming> so after the specified time it's not removed from play
[11:10] <&BC_Programming> it just goes back to normal?
[11:10] <+Mulreay> yeah
[11:10] <+Mulreay> after a set amount of time
[11:11] <&BC_Programming> I was sorta liking the it dies idea as well, since then if you hit it with your only ball you better hope that the craziness causes the creation of more balls or else you lose a life
[11:11] <&BC_Programming> wouldn't be too hard to do both, see which is more "playable"
[11:12] <+Mulreay> yeah, best way is to test
[11:12] <+Mulreay> I did have another idea but don't want to overload you
[11:13] <&BC_Programming> no no this is good
[11:13] <&BC_Programming> see I run out of ideas
[11:13] <+Mulreay> heh
[11:13] <+Mulreay> ok
[11:13] <&BC_Programming> that's why I just end up stealing enemies from megaman
[11:14] <+Mulreay> Remember when you do the euargh noise on skype playing minecraft, when you spew bones at me?Well why not have a 'mouth block' that when it enters there is like a 2sec wait and then you hear euargh and 3 balls shoot out... as if it's being sick
[11:15] <&BC_Programming> HAHAHA
[11:15] <&BC_Programming> awesome
[11:15] <&BC_Programming> LOVEIT
[11:15] <+Mulreay> heh
[11:15] <&BC_Programming> I already have demon blocks, I think those are in the vid, they make a rather funny noise
[11:15] <+Mulreay> cool
[11:15] <&BC_Programming> but a BLECH noise
[11:15] <&BC_Programming> that would rule