Out of interest: are there missiles like the 83+ version?

(as that's the only version I play)

Ah, sorry


I just... didn't really follow as closely as I should of...

IMO it doesn't seem as much as hell as the 83+ version, but the sprites and everything look awesome!

I think it's good it doesn't start too insane, because in CaDan you can't even survive more than 3 seconds after the cutscenes unless you played Danmaku shooters before. >.<

Quote from: DJ Omnimaga on August 14, 2014, 01:11:46 pm

I think it's good it doesn't start too insane, because in CaDan you can't even survive more than 3 seconds after the cutscenes unless you played Danmaku shooters before. >.<

I managed to beat it with no experience with the "Netham45" ship... with mostly bombs...

Are you serious??


That reminds me, the Netham45 ship would be a nice easter egg in nKaruga

Hey ! This is not dead ! Holy shit !

As school has been violent on me lastly, I quite put this on hold. But now it's back, because that one project I really want to get done !

So what I did first is implementing an idea I had had since quite a long time, that is, a "drawing candidates" system.
So what is that ? Basically, it's a way of ensuring that every drawing is synced together and with the screen refreshes. So instead of directly drawing a sprite to the buffer, I create a drawing candidate with the X, Y coordinates of the sprite and the sprite itself (and a few more things, like angle of rotation, if rotation is needed at all etc). It acts kind of like a "drawing hook", meaning I can make special things happen each time a drawing is being performed. That's not the only advantage : since I use frameskipping, bringing all drawing in a single loop means I can do only one check to see if we actually have to draw anything or not, instead of one test per drawing !

I also started on the boss system, as I FIIIINALLY figured out how to do it. It's been hard, and it'll be even harder to code but brace yourselves for impact when it's done

So yeah, I don't have anything new to show, but my future life has been made a lot easier today (drawing candidates will be extremely useful, if not needed, in levels 2, 3 and 4).

But but wait what am I talking about ! I also set up this nice procedural explosion generation engine !



Can someone with a color Nspire tell me what the speed is like ? http://www.mirari.fr/eTV6

Woah matref, that explosion was beautiful and I like the intro banners

Btw, will Netham45 be a playable character finally?

Bump,

I'm done with the boss system !

It's actually a pretty complex system, that allows for nearly infinite customization and flexibility for bosses. It takes advantage of the fact that bosses have definite, non-modular behaviors, and thus always know exactly what hitbox to check or things like this. So let's see how that works :

• First, when cmd_boss is encountered in the level stream, a new boss is created and initialized. Upon creation, an initialization hook is executed, in the form of a function pointer. The goal of this hook is basically to set the boss up, and having it in the form of a function pointer allows me to use very generic code, while actually doing purpose-written tasks, since each boss is initialized differently.
  
• When the boss is created, the game enters "fight boss" mode, meaning that in addition to enemies and bullets, the boss will also be handled and updated when necessary.
• When the handle() function of the boss is created, a really simple process takes place : what it does is only call its callback code (you can call it an "update hook") and return whether the boss is dead or not. That way, I can do everything I want in the callback itself, and it works for every boss, even if they have so little in common ! For example, I can make the boss have several behaviors by simply testing the amount of HP left, and doing different things depending on the result.
  
• Exceptionally, drawing is handled within the callback (via drawing candidates, which is normal). This allows me to have whatever graphical complexity I want !
• When bullets are handled, no collision is checked between them and the boss ; a collision callback (call it a "collision checking hook" if you want) is executed, allowing the boss to have special or esoteric hitboxes - or even special or esoteric ways of checking collisions -, instead of checking collision the way I do it with any other objects, by simply testing if the images of both objects intersect.

As I said, all of this allows me to have virtually infinite liberty on what the bosses do, so wait for them, 'cause it's going to be awesome