Monsters wouldn't be coming after the player in this game either: each monster is bound to a room, and combat is turn based upon entering the room. So speed is irrelevant. Evasion, Crit, and First strike would be relevant.

_________________
I ain't pushing no moon buttons.

So basically there's no movement other than of the room-to-room variety?

In that case, then yeah -- speed is less important (though I would still say it wouldn't be a horrible idea. YMMV.).

_________________
What most people don't understand about "enlightenment" is that it is not an end-goal; but where you find yourself just before taking a new "first step."

The player will walk from room to room, and walk to pick up items. It also means that the player can't zip through the dungeon at lightning speed.

_________________
I ain't pushing no moon buttons.

I got the OGL type library thing working. I'll mess around with it when I have time.


Cool, fair enough. I still think the idea has merit, but I'll save it for another day, maybe for a non-RPG setting

_________________
Whatever the mind can conceive and believe, it can achieve

Adding my particle system into the demo, and creating a lantern.

Two completely different programs bought together with ease. Behold the power of modular code.

_________________
I ain't pushing no moon buttons.

Looking nice there, Jas.


I love bundle deals, too! I just wish I could find a sale where I could get two items I need together at the discount... x_x

_________________
What most people don't understand about "enlightenment" is that it is not an end-goal; but where you find yourself just before taking a new "first step."

Looking good! I'm intermittently reading "Interactive Computer Graphics - Using OpenGL" and "3D Math Primer for Graphics and Game Development". I've lost my OpenGL primer book somehow. I started reading it a few months back and now it's disappeared.

_________________
Whatever the mind can conceive and believe, it can achieve

What other scenery should we have?

Floor blocks, Wall blocks, Door Arches, Lanterns


~~~~

For scenery things I think we should organise the data like this:

Vertex(a).X -- holds the X coordinate of vertex a.
Vertex(a).Y
Vertex(a).Z

Polygon().Vertex(b) -- holds the index of the b'th vertex. b=0,1,2,3
Polygon().TexU(b) -- holds the texture U coordinate for the b'th vertex.
Polygon().TexV(b)

Object().Start -- the index of the first polygon in the polygon list, that belongs to this object.
Object().Length -- the number of polygons in the polygon list that belong to this object.
Object().Texture -- the index of the texture to use for this object.

_________________
I ain't pushing no moon buttons.

Pillars, at the least. Other than that, maybe braziers/cauldrons, bookshelves, and weapon/armor racks.

What about floor decorations? Rugs, magic symbols, graffiti... that sort of thing?

_________________
What most people don't understand about "enlightenment" is that it is not an end-goal; but where you find yourself just before taking a new "first step."

Yes, they're all good ideas.

Crates, Rocks, Stalagmites, Fountain of Health

I'm also considering adjustable floor elevation, so we can have steps, and possibly water/lava pools.

_________________
I ain't pushing no moon buttons.

Well, if you want a big list to just cherry-pick from...

*consults the Geeky Gamer's Dungeon Dictionary (aka. D&D Dungeon Master's Guide)*

Altar
Balcony
Barrel
Bed
Bench
Cage
Carving
Casket
Catwalk
Chair
Chandelier
Chasm
Chest
Chest-of-Drawers
Chute
Coat rack
Collapsed Wall
Cupboard
Curtain
Door (broken)
Dung heap
Fallen Stones
Fire Pit
Fireplace
Forge
Gong
Hay (pile)
Hole
Hole (blasted)
Idol
Iron bars
Iron maiden (the *other* one... not the metal group)
Kiln
Ladder
Ledge
Manacles
Manger
Mirror
Mound of rubble
Oven
Overhang
Pedestal
Pillory
Portcullis
Rack
Ramp
Sconce
Shrine
Statue (standing or toppled)
Stuffed Beast (i.e. taxidermy-style)
Table
Tapestry
Throne
Trough
Tub
Wall Basin
Wardrobe
Well
Winch and Pulley
Workbench

---

Note that I omitted a number of items that either didn't fit or has already been mentioned in some form. The complete table has 100 different 'major' room features, but the ones I listed above would be a more than sufficient source for choosing actual map elements.

_________________
What most people don't understand about "enlightenment" is that it is not an end-goal; but where you find yourself just before taking a new "first step."

I made a model editor at the weekend and recreated the arch.

_________________
I ain't pushing no moon buttons.

Very nice. How are you building your GIFs?

_________________
10 PRINT "Bad Monkey ";
20 GOTO 10

Output to bitmap sequence, then import the sequence to Animation Shop Pro, and save as gif.

Here are Steps... 5, 6, 7, 8

_________________
I ain't pushing no moon buttons.

What model 3D formats are nice to work with Codehead?

There are two which stand out:
.obj, seems quite intuitive for static models. But I'm tempted to use my own model format for static models.

There's also .mdl which was used in quake, and it seems more intuitive for animating.

_________________
I ain't pushing no moon buttons.

.OBJ is fine for static objects, the text based versions are easy to read for humans and machines, I often hand edit objects on the fly with a text editor.
My only reservation is that the material detail is held in a seperate file. However, there's nothing to stop you adding your own custom tags into the files.

There is a complied version of the format too (.MOD), but it's rarely seen and a pain to work with.

I've used MD2 for animated models, but the format had some serious accuracy issues. MD3/MDL may be better, but I found that due to the way the animation data is stored, the file sizes became huge very quickly.

In the end I went for a custom skeletal system using .OBJs for the 'chunks' that made up the character. My mech figures don't need flexing organic joints, you can get away with using distinct lumps to build them.

_________________
10 PRINT "Bad Monkey ";
20 GOTO 10

The editor I made at the weekend is for hand editing objects, and it updates the model as the text is typed.



As long as I don't have too many frames, I should be okay.



Sounds like the characters in Minecraft.

_________________
I ain't pushing no moon buttons.

For one of my older C++/OpenGL projects ('HyperCop', IIRC) I made a custom format. It was simply a file with multiple OBJ data, divided into keyframes. Each keyframe had an index, and to start a transition from one keyframe to the next, the game would read the OBJ data from the given index, and then LERP the model's vertices over to the new keyframe.

The format assumed a few things -- mainly that each keyframe had the exact same vertex count. Also, the vertices had to be entered in the same order for each keyframe, or else things would get *very* messy.

EDIT
And, really, you could just do the same with separate OBJ files, no need to lump them together. Just make sure the vertex count is the same, and that all vertices are in the same order!

_________________
What most people don't understand about "enlightenment" is that it is not an end-goal; but where you find yourself just before taking a new "first step."

The Mechs are a little prettier, but the principle is the same.

_________________
10 PRINT "Bad Monkey ";
20 GOTO 10

That looks quite a bit like rollin

_________________
"Education is what remains after one has forgotten everything he learned in school."
"If you can't explain it simply, you don't understand it well enough."
"Anyone who has never made a mistake has never tried anything new."
~Albert Einstein