[Mod] Shinobi Densetsu (Discontinued) (Page 5 of 6)

everytime you open the menu? i'm really not much into reviewing that release, but if it's game breaking i'll do it

there's no ending. and that was released as it was, so yeah lots of bugs

but you don't need to report them, we're rewriting everything so this system will become obsolete.

that's the kind of approach we're taking. we named all possible subsystems that we needed so that each is regulated by its own object. Some of the modules we had running all the time will most likely be adapted to run on call and destroy when not needed.

we are also trying to reduce in the number of lines and states of each object by passing the redundant tasks to a common child object that is then called by any object needing it.

we learned a lot in the last year, and always eager for more. all tips are welcome

how do you know its good work if you haven't played it

yknow i do the same with your music sometimes. or do i?

Last edited by SupertheHedgie (2012-01-04 08:44:52)

These pictures comes to mind.

For my money these are stunning pictures that really shows off the game from it's best side. That's something we both can agree on. And... If you got something sensible about my music to say, say it in a proper topic without no delay. I'm always open for constructive critics, if you can give some that is.

Listen to my music
Don't miss the facebook group!

i was only serious about the wrong topic

Maybe you could make it customizeable and choosable in-game?

I aim to please. ;-l

It's a sonic-esque engine that allows you to create your own levels. This just made a completely new game out of the scripting system also in the engine which lets you make a lot of your own objects and abilities.

We aren't actually Sonic anymore though, as many people would tell you. Read around the forum and project page a bit and you'll understand.

Thanks for the info but I already figured as much from seeing this mod.

hey, you created an account with a name very similar to mine

thanks to fast loops, gravity and slopes can be handled by their own states, while the object moves around flawlessly up and down slopes.

execute "gravity" if "brick_type(0,1) == 0"

state "gravity"
        {
        gravity
        }

no gravity applied if the bottom of the object is in contact with a solid brick. this solves a lot of gravity issues

execute "slope_correction" while "((brick_type(direction()*6, 0-1)) and (brick_type(0, 1)) and ((brick_angle(direction()*6, 0-1)<> 90)and (brick_angle(direction()*6, 0-1)<> 270))) or (brick_type(0, 0-16))" 

state "slope_correction"
        {
        set_absolute_position xpos() ypos()-1
        }

this prevents the object from using the default slope algorythm, replacing it with a "push out" whenever a slope is detected in front of the object.  please notice that you may have to adjust the coordinates of brick functions to fit the size and shape of your object. precise level building is a must, NO OVERLAPPING BRICKS, or your walking object will fall when two bricks intersect.

goes well with