~Screenshot Central!

[Felix-0]

Nah, it's not intractable, more screensaver-ish.

But it now has 100% more knights

I like the large amount of RNG usage and everything about this.

[Donut]

Waw that's just bang on. Looking forward to playing something like that.

[Meiscool]

Does it use plugins or scripting?

[Momeka]

Nah, no plugins. Just scripting, but the system is pretty limited and would more or less just work on turn based stuff.

Written a tutorial about it if anyone is intrested (Still kinda wip)

[Donut]

Not really a screenshot, but I'm trying to get some pixel art done for a shooter I'm working on with Unity. Mostly spaceships for now.Those are my first real attempts at pixel art other than charas, so any advices are appreciated

[Felix-0]

Not really a screenshot, but I'm trying to get some pixel art done for a shooter I'm working on with Unity. Mostly spaceships for now.Those are my first real attempts at pixel art other than charas, so any advices are appreciated

Doing a rail shooter type deal? My favorite of this genre is a really old TurboGraphix game called Blazing Lazers.
Overall the pixels are pixely fur sure. I'd have to see how they held up in game/on a background to see how they really shape up.


Oh yeah. I havent' posted much about Ruby Quest:Undertow. The game I've been doing music for/testplaying as well.



Here's some of em.
http://rpgmaker.net/games/6935/
and the project page as well.

[Zoltar]

*Sees Mr Felix's screens.....rips up his plans to be a RPG Maker* Those are so mondo tubular! *__*

[Momeka]

Looks great! Keep the style consistent and I'm sure it will look good.

Edit:
Sorry, kinda spamming this thread. Got started on the last pathfindng example.

[Felix-0]

Yoo how in the **** is that arrow controlled, thats inane.

[Prpl_Mage]

I get the arrow itself, I just don't get how it makes the bends/corners

[Momeka]

Yoo how in the **** is that arrow controlled, thats inane.

I get the arrow itself, I just don't get how it makes the bends/corners

The gist of the pathfinding is that each tile has a number associated with it, we'll call this number the cost. Then we pick the tile we want to path to and set it's cost to zero and all the others to 9999 (some high number, doesn't really matter). Then we go through each tile in the map and check their neighboring tiles, if one neighbor has a cost that is lower by two we set the current tiles cost to one above that. We keep doing this until no more changes is made. In the end we will have something like this:



Now each tiles cost is basically the number of moves it is from the goal tile. We simply follow the lowest numbers until we reach the goal.



As for the arrow, instead of moving something I just take a piece of it and set it's graphic to point in the right direction.

I'll be posting the whole thing somewhere once I finished it.

[Felix-0]

You're an absolute madman.

[Moosetroop11]

Oh that is cooooool. And weirdly obvious once you explain it.

[zuhane]

That is awesome, Momeka! I'm really impressed with the technical side but also the whole aesthetic and way the project looks.

Keep up the good work!

Also, would you say it's a lot easier to implement A* pathfinding if it uses a tile-based system instead of points?

[Momeka]

Thanks Z.

Not sure actually, only done A* for top down tile systems. But I don't think it would be that much harder, the principle is the same except that you might have to take distance into the equation if the points aren't evenly spaced.

Edit:

I love that you can code your own title screen in the steam rm2k3