i already written functions to create gradients, outlining images,color tinting, drawing simple shapes(a star and a diamond so far.) and such.

Embedding meshes/music/textures and such is not the point. For my understanding the point is to create things in runtime.(though i dont know how d we be able to create sounds at runtime.)

Can we create something like an particle editor, let the user load a particle file from his HDD and then create a .c file with the code for the particle effect?
Edit: And later load the generated .c file again to edit the effect?

that was what i was planning >.<

modifying "beep;"?

But, you are right, there are functions for creating bmaps and modify them, but there is nothing for creating sounds.

To get aware of such things is probably one of the purpose of the contest!

nice as always, added to AUM Online and AUM Search. now with 845 indexed pages ;-)

We'll have to wait for JCL's input - this contest was his idea.

Not allowing any buffer dta is cheesy.

In principal any array is some sort of buffer. So if I mix some values in an array and then sort them in correct order it's no buffer anymore, if the order is correct it is?

What is alloeed and what is not?
Limit code size to 50KB or so and that's it.

Back to the roots, I like it and have some ideas for the contest, thanks again jcl.
Arcade games is the reason and not the data dumping, maybe.

Thanks George for the Aum too.

Imho there are good reasons to use buffered data to some extent, especially for such a contest.
I agree that it defeats the purpose if we're allowed to store 10 meg models inside the source, but for small stuff which cannot be created on the fly this is a great feature.

Some answers to the contest:

- Can we use plugins? - Yes, but only when including the source.
- Can we create 3D objects with some tricks? - Yes.
- Can we define the content of textures, meshes etc. in the source code? - No. You can use images and meshes, but their content must be procedurally generated at run time.