Print

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

[Alexhans]

Oh... And If someone knows a nice clean algorithm to make animations based on time (like zapping a wand in ADOM) I would appreciate it.

Assuming you're using some sort of sprite-based animation, you could load all pictures into an array, set a variable to 0, load the first picture using the variable and increment the variable by one. Rinse and repeat, by putting the code that increases the aforementioned variable in the loop that gouverns the game.

oh no... im using curses with ANSII chars... my problem is with the time header of c++ time.h ... I couldn't use it easyly.  But later with a bit more time I may study it a bit more.

[Fenrir]

I'm going to continue level generation and design later; I just got a brilliant idea for handling skills.

[JoshuaFH]

If you guys finish your things, i'd be more than happy to test play them.

[Aqizzar]

Wow, this thread is exactly what I've been looking for.  I learned how to code in JAVA about six years ago, but I haven't touched it since then.  It's been hard getting back into things since JAVA changed in that time - but C++ works much the same way, at my newb level at least, and all the old logic is coming back to me.

Problem: I'm using the Terror In The ASCII Dungeon tutorial, and it's fantastic.  But, there's no link to Part 5 in the original thread.  I assume there is a part 5, anyone know where to find it?  I'm reading through the later posts, but there's indications the guy who wrote them never got around to finishing it.

[Sowelu]

I've searched the web, there's no trace of the next part.

[Fenrir]

Terror in the ASCII Dungeon was unfortunately abandoned after Part 4.

[deadlycairn]

Well I FINALLY managed to get my guy to walk around - there's a call to it at the end of the Draw function for the room (not sure if that's the right way to do it, but oh well). Of course, with no collision checking whatsoever, hilarity ensued when i went out of the room.

EDIT: Damnit can't upload the image. Lots of little smileys all floating about outside the room.

From here I'll work on collision checking, then attacking, then some (basic) AI for the duck.

[Fenrir]

Perhaps if the author was put under some degree of pressure, he would finish his tutorial. Let us all sign up on those forums and heckle that character!

[Aqizzar]

Considering the part 4 was put up a year and a half ago, I think he's made peace with being a failure on the Internet.

Man, why's every genuinely helpful tutorial have to die halfway through?

Well, now to figure this out myself.  Somehow, I know my version going to involve a giant pile of while loops...

[deadlycairn]

Join the club. I'm pretty sure mine will be glued together with generous usage of the switch statement, the while loop, hope, prayers, wasted hours and random button mashing - thats what happens when I try to do something without a tutorial - I manage, but it's not pretty.

[Sowelu]

Some suggestions on how to continue that tutorial:

- If it's your first roguelike, go ahead and do collision checking based on the graphics themselves.  Meaning...  Look at what's currently drawn in the tile you want to move into.  I think there's a command for that.  If it's one of the walls, cancel the move.  If it's not, assume that tile is walkable, and see if it contains a monster to fight; otherwise, just move.  Of course, this means that nothing can EVER be drawn over the walls, and you can only have one floor tile...  Still, it's an easy and very classic approach, and it's OKAY.

- Your loop, most likely, is going to be:  "Draw the screen.  Read player input, until they give you a key you want to handle.  Handle the player's turn.  Handle everything else's turn.  GOTO 10.  Oh yeah, and make sure the user can press a key like Q as their input to break out of the loop, because games you can't quit are annoying."

[Fenrir]

I'm having a wee bit of difficulty. I read somewhere that global stuff is bad, so I have a Game class that holds my map. The trouble is, I need to store my vector of objects in said class, but then how do I loop through them to draw them? Should I just make the class do that itself, or should I perhaps have a function that returns a copy of the vector?

[Aqizzar]

- Your loop, most likely, is going to be:  "Draw the screen.  Read player input, until they give you a key you want to handle.  Handle the player's turn.  Handle everything else's turn.  GOTO 10.  Oh yeah, and make sure the user can press a key like Q as their input to break out of the loop, because games you can't quit are annoying."

Yeah, that's one programing trick I never go into - pseudo code.  For some reason I just a have violent aversion to writing down anything I think I could fit in my head.  I know I'm going to need to map this out to keep the logic moving properly.

Hmm...  Maybe, I should set the entire map system up as a separate function, so I can have a chargen frontend...

[qwertyuiopas]

Join the club. I'm pretty sure mine will be glued together with generous usage of the switch statement, the while loop, hope, prayers, wasted hours and random button mashing - thats what happens when I try to do something without a tutorial - I manage, but it's not pretty.

I don't even use switch statements, or even for loops...


Also, I personally am finding that a global array for the screen works well. Maybe it's just what I'm using (C and openGL).

[Granite26]

Yeah, that's one programing trick I never go into - pseudo code.  For some reason I just a have violent aversion to writing down anything I think I could fit in my head.  I know I'm going to need to map this out to keep the logic moving properly.

Hmm...  Maybe, I should set the entire map system up as a separate function, so I can have a chargen frontend...

Technically, every 'mode' you've got should be totally independant of the 'main' function  (So you could window up a 'start' screen that launches chargen or worldgen, or whatever, do that and 'save' it, then return.  Play should be exactly the same way.