Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Derakon]

I've been spending more time looking for a job lately, and thus less time working on this. However, since it's clear that once I get a job, I'll have even less time for this project, I've been working on cleaning up the codebase in preparation for making it an open-source project. I spent a great deal of time writing Doxygen documentation for everything, and then even more time working on refactoring the Player class to split out the collision-detection and terrain-following logic in it into more sensible locations. Right now all that remains to be done before I can find a project website is finishing up some work on the map feature I'd been working on before all this started: environmental effects. Specifically, in this case, water.

[Sowelu]

Derakon, you are a god among men.

[Derakon]

Okay! The Jetblade project site is now online, so feel free to check it out! You'll need Mercurial to download the source code (Mercurial is a VCS like git, and very easy to use). There's Doxygen documentation for the project in the 'html' directory of the source, which should give you a starting point for figuring out how things are organized. I've also included all of the Blender files for the models I've made so far (minus the file for the terrain blocks, which is too big and needs to be split up).

[SolarShado]

If this were being written in Java instead of python, I'd be on it like a rabid rheus... but i don't know python.

EDIT: You might should edit your OP.

[IndonesiaWarMinister]

python, uh? It is 2.x version, right? Cause all I have in this computer is 2.6...

BTW, n00b at programming, me.

[Derakon]

SolarShado: yep, Python. It's not at all hard to learn; you should check it out. If nothing else, you'll be able to add another language to your résumé.

I'll update the first post now...

IndonesiaWarMinister: Yeah, it's using Python2.5. It occurs to me that maybe the shebang line should be updated (it currently assumes you have Python at /usr/local/bin/python2.5).

[IndonesiaWarMinister]

Eh, so it's defaulting to Linux's My Document?
Damn...

[Derakon]

Er, I'm afraid I don't know what you mean by that.

If you have Python and PyGame installed, you should be able to run the game by doing "python jetblade.py".

[IndonesiaWarMinister]

'K, I'll do it tomorrow then... I need to hoard ANY knowledge I can get!

[Tahin]

I have a little experience with Python and may be interested in helping. That said, I have another project I'm working on that I really should have been done with sometime last year, so this may have to wait. Looks really cool, though. Installing Mercurial as we speak.

[Derakon]

Just a quicky this time: I've added my first "explicit" jumping puzzle.



(In case it's hard to tell, there's water between the narrow vertical platforms)

[qwertyuiopas]

I saw the roadmap and thought "I might be able to do that".

My idea, having not viewed the source yet:
I believe I should be able to make a powerup system for mapgen.
The idea would be to add limits to the nodes saying if the player could get there with a certain set of powerups, then transfer the lowest access set to child nodes, maybe multiple sets allowed at once, if there are two acces routes of differing difficulty(though at first it should simply disallow connecting to differing requirement nodes).
Powerups cannot be placed in an area that requires their use to access.
One powerup of each major type should be generated, at least initially, and placed in an accesable node.
Also, I don't know if I know enough about python..


Edit:
Tried running, but it stops when it can't "import featuremanager", as featuremanager does not exist...

[Derakon]

Oh, gorram it. I forgot to add featuremanager.py to the project when I created it. And of course it worked for me because the (non-added) class was still there in the directory. Sorry about that. Redownload the source and give it a shot, please?

As for your plans for powerup placement, they sound like the vague ideas I was toying with; basically, have levels of accessibility, with each level requiring a powerup found in a previous level to access. Level 0 is accessible from the start, level 1 requires a powerup in level 0, level 2 requires a powerup in level 0 or level 1, etc. The trick really is in enforcing the requirements by creating roadblocks; I haven't quite figured that part out yet.

Python's easy to read even if you don't know it specifically.

[qwertyuiopas]

Well, I found that you can teleport up through the ground at a point like this:

Code: [Select]

##
/`
``
``
`#(` is empty space)
It generated a platform that blocked entry to a tunnel, although it could be accessed by crawling off the blocking platform.

Multiple times it generated a one-way drep, fortunately giving another way around at those points. Once by putting a platform in the way of climbing up, the other as pictured.

It also completely blocked a passage with two platforms leaving barely a gap between them

Code: [Select]

---`|
````|
`---|

[SolarShado]

Please PM me when there's a playable version or you need someone to do some playtesting. I love metroid-vania games...