What is important in a sprite library ?

[Bean]

I am working on a sprite library for the 16K ZX81.
It uses a video interrupt handler to place the sprites, when you move the sprite it puts back what was under the sprite.

Right now it only handles a single 1 character sprite, but I plan to make it handle two 1 character sprites and two 3x2 sprites.

I am thinking that the single character sprites should be able to move on their own and detect if they hit something.

What would you like see in a sprite library ?

I'll post some code once it gets a little further along...

Thanks, Bean.

[Bean]

Here is just a simple demo of how it will work.

Bean

[GCHarder]

This may have been done already.

Available here, published in Your Computer Sept 84

https://archive.org/details/your-comput ... 1/mode/2up


http://www.users.globalnet.co.uk/~jg27p ... _name8.htm

Regards;

Greg

[Bean]

Thanks Greg, I'll take a look at it.

Bean

[Spinnetti]

Sprites as a "thing" are well defined. Hi-rez, collision detection, pixel movement etc. Having clearly documented functions in machine language would be great - The referenced article provides a tool to do from basic so no need to reinvent that wheel, but just clear modular ML routines would be handy for me for sure. Me and a buddy have been doing our own, but not happy with the results yet.