The Beginners Guide to Roguelikes (v 0.0.0.0.0.0.1a)

On 2007-11-21, Craig <craig.stickel RemoveThis @gmail.com> wrote:
> Articles One and Two are complete and ready for critique. I apologize
> for the delay. Feel free to let me know what you think and please
> point out any gramatical errors or stuff that just doesn't make sense
> or rambles. With everything that has gone on, I'm actually finding it
> hard to think straight lately.
>
> Given it's nature, newbie/lurker opinions carry double weight. So
> stand up and be heard!
>
> Link:
> http://files-upload.com/files/633676/Release.zip
>
> Previous Post/Thread (background/preview of what's coming up):
> http://groups.google.ca/group/rec.games.roguelike.development/browse_t...ad/thre
> - Craig
>
> PS. If anybody knows a better @#^! home for the files, please let me
> know. I hate these free upload places, but I am rather useless when it
> comes to web stuff.

I'd be happy to host it for you on crawl.akrasiac.org if "ad-free hosting
by specific stranger" is a significant upgrade in your mind. You might
also look at Google Pages or something, though I don't know if they'll
let you post just random Word and source files. I flipped through the
first two chapters and they look very promising.

-r.

(Obligatory because I do this for a living: But they're in _Word_! Have
you considered some sort of structured and publishable (HTML, print,
whatever) format like DocBook, LaTeX, or even FrameMaker or Indesign?
 >> Stay informed about: The Beginners Guide to Roguelikes (v 0.0.0.0.0.0.1a) 

On 22 Nov, 00:21, Craig <craig.stic....TakeThisOut@gmail.com> wrote:
> Articles One and Two are complete and ready for critique. I apologize
> for the delay. Feel free to let me know what you think and please
> point out any gramatical errors or stuff that just doesn't make sense
> or rambles. With everything that has gone on, I'm actually finding it
> hard to think straight lately.
>
> Given it's nature, newbie/lurker opinions carry double weight. So
> stand up and be heard!
>
> Link:http://files-upload.com/files/633676/Release.zip
>
> Previous Post/Thread (background/preview of what's coming up):http://groups.google.ca/group/rec.games.roguelike.development/browse_...
> - Craig
>
> PS. If anybody knows a better @#^! home for the files, please let me
> know. I hate these free upload places, but I am rather useless when it
> comes to web stuff.

Thanks for your time, I'll be checking trough the files whenever I get
home.
 >> Stay informed about: The Beginners Guide to Roguelikes (v 0.0.0.0.0.0.1a) 

On 22 Nov, 14:11, sPlaTH <robin.horne... DeleteThis @gmail.com> wrote:
> On 22 Nov, 00:21, Craig <craig.stic... DeleteThis @gmail.com> wrote:
>
>
>
> > Articles One and Two are complete and ready for critique. I apologize
> > for the delay. Feel free to let me know what you think and please
> > point out any gramatical errors or stuff that just doesn't make sense
> > or rambles. With everything that has gone on, I'm actually finding it
> > hard to think straight lately.
>
> > Given it's nature, newbie/lurker opinions carry double weight. So
> > stand up and be heard!
>
> > Link:http://files-upload.com/files/633676/Release.zip
>
> > Previous Post/Thread (background/preview of what's coming up):http://groups.google.ca/group/rec.games.roguelike.development/browse_...
> > - Craig
>
> > PS. If anybody knows a better @#^! home for the files, please let me
> > know. I hate these free upload places, but I am rather useless when it
> > comes to web stuff.
>
> Thanks for your time, I'll be checking trough the files whenever I get
> home.

Well, I didn't wait and I read through your articles. I guess I found
one or two mispelled words, but I can't even remember where I found
them. I will certainly use these articles when making my own
roguelike. Thanks! However, as a few others pointed out. You should
use another format than doc for your articles.
 >> Stay informed about: The Beginners Guide to Roguelikes (v 0.0.0.0.0.0.1a) 

On Nov 21, 10:51 pm, Brog <cryskn....TakeThisOut@gmail.com> wrote:
> Omg, they're in WORD? Glad I didn't download them then. Recommend
> fixing if you want anyone to.- Hide quoted text -
>
> - Show quoted text -

Although you lose the images, you can open them in Wordpad.

-- Shanya Almafeta
 >> Stay informed about: The Beginners Guide to Roguelikes (v 0.0.0.0.0.0.1a) 

On Nov 21, 6:21 pm, Craig <craig.stic....TakeThisOut@gmail.com> wrote:
> Articles One and Two are complete and ready for critique. I apologize
> for the delay. Feel free to let me know what you think and please
> point out any gramatical errors or stuff that just doesn't make sense
> or rambles. With everything that has gone on, I'm actually finding it
> hard to think straight lately.
>
> Given it's nature, newbie/lurker opinions carry double weight. So
> stand up and be heard!

Thoughts:

"Release"... could you please give it a more descriptive name like
"Craig's Roguelike Tutorial" or something? ^^;

Article two. "Never once do you see the "levels" in these games
spanning a horizontal region larger than the screen size." I can
think of three games off hand that DO have levels like this...
although for simplicity's sake, and for the sake of new programmers,
screen-sized is probably best.

Comments! This is very handy, and (newbie) I've already learned some
things, but I don't use C++. For the sake of those who have to
convert your code into their language of choice, could you add a few
more comments to your code, especially in the snippets we see in the
article?

Thanks!

-- Shanya Almafeta
 >> Stay informed about: The Beginners Guide to Roguelikes (v 0.0.0.0.0.0.1a) 

On Nov 22, 8:48 am, "almaf...@gmail.com" <almaf....RemoveThis@gmail.com> wrote:
>
> Thoughts:
>
> "Release"... could you please give it a more descriptive name like
> "Craig's Roguelike Tutorial" or something? ^^;
>
> Article two. "Never once do you see the "levels" in these games
> spanning a horizontal region larger than the screen size." I can
> think of three games off hand that DO have levels like this...
> although for simplicity's sake, and for the sake of new programmers,
> screen-sized is probably best.

My wording should be better/cleaner. The statement was intended for
the games I mentioned earlier like ADOM, Rogue, NetHack, etc.

> Comments! This is very handy, and (newbie) I've already learned some
> things, but I don't use C++. For the sake of those who have to
> convert your code into their language of choice, could you add a few
> more comments to your code, especially in the snippets we see in the
> article?

Hmm.. I honestly thought that my comments would be able to do that.
Problem is - and I don't want to seem like I'm blowing my own horn
here - but I know over 9 different programming languages (nearly all
of them low-level) and when you get to that state they start bleeding
into one and the only real difference you start noticing is syntax
primarily.

What I'm trying to get at is I'm not sure I know *how* to comment in a
way that might make sense to programmers who specialize in higher-
level languages (C#, Python or Lua for instance). It's a completely
different world, trust me. (I used to have a hard time with Java, for
pete's sake). Could you possibly give me an example? Like from the
Article One source?
 >> Stay informed about: The Beginners Guide to Roguelikes (v 0.0.0.0.0.0.1a) 

Never knew that the Word thing would be an issue, but thinking about
it, yes. I apologize for that. Here's the HTML version.

http://www.megafileupload.com/en/file/24960/Beginners-Guide-to-Rogueli...-zip.ht
 >> Stay informed about: The Beginners Guide to Roguelikes (v 0.0.0.0.0.0.1a) 

On Nov 21, 8:42 pm, Rachel Elizabeth Dillon <rac....RemoveThis@akrasiac.org>
wrote:
> I'd be happy to host it for you on crawl.akrasiac.org if "ad-free hosting
> by specific stranger" is a significant upgrade in your mind.

It would be a very significant upgrade. I would appreciate that. And
I'm sure that those who download it would be even more grateful for
the change. Thank you!

Kind of off-topic, but it was your post on Krice's legendary "Tiny
Roguelike Scene" thread (of which I think it was a turning point for
the RL scene as a whole) that convinced me to try my hand at this
guide. So thank you.
 >> Stay informed about: The Beginners Guide to Roguelikes (v 0.0.0.0.0.0.1a) 

On Nov 22, 11:54 am, Paul Donnelly <paul-donne... RemoveThis @sbcglobal.net>
wrote:
> I could try my hand at that.

Thank you!

> I wouldn't bother to cover the language basics, but as a reader when
> I come to a case statement labeled "processing phase" I would like
> to know in general terms what we plan to process.

Good point. I cover the concept in the articles lightly, which means
that those who are "source-surfing" would be lost in the shuffle.

> Of course, I'm experienced enough to understand what this code is going to
> do, but presumably your main audience isn't.

That's my primary fear: that those who actually do understand what
I'm writing are too experienced to find it useful.
 >> Stay informed about: The Beginners Guide to Roguelikes (v 0.0.0.0.0.0.1a) 

> > Of course, I'm experienced enough to understand what this code is going to
> > do, but presumably your main audience isn't.
>
> That's my primary fear: that those who actually do understand what
> I'm writing are too experienced to find it useful.

I have taken basic classes in C++ and Java. I understand the code
discussion, but the theory on how to create the base of a roguelike is
still interesting. I assume it will get even better once we get into
rudimentary AI (i.e. placing monsters, and having them move). My 2 zm.

I notice some "this isn't the most effective way to do it, but it's
easy", though. A bit jarring for me as a backseat r.g.r.d. follower.
Maybe necessary to make the tutorial both understandable and concise,
though.

Looking forward to the upcoming chapters.

/Hällzon
 >> Stay informed about: The Beginners Guide to Roguelikes (v 0.0.0.0.0.0.1a) 

Quoting almafeta DeleteThis @gmail.com <almafeta DeleteThis @gmail.com>:
>On Nov 21, 10:51 pm, Brog <cryskn... DeleteThis @gmail.com> wrote:
>>Omg, they're in WORD? Glad I didn't download them then. Recommend
>>fixing if you want anyone to.- Hide quoted text -
>Although you lose the images, you can open them in Wordpad.

If you happen to be afflicted with Windows, yes.

I was going to say "if you've written an article about roguelike
development post it here, don't make people jump through hoops", but if
they're in some nutjob format that may be a non-starter.
--
David Damerell <damerell DeleteThis @chiark.greenend.org.uk> flcl?
Today is Second Monday, November.
 >> Stay informed about: The Beginners Guide to Roguelikes (v 0.0.0.0.0.0.1a) 

On Thu, 22 Nov 2007 09:06:54 -0800, Craig wrote:

> On Nov 22, 8:48 am, "almaf...@gmail.com" <almaf....DeleteThis@gmail.com> wrote:
>>
>> Comments! This is very handy, and (newbie) I've already learned some
>> things, but I don't use C++. For the sake of those who have to
>> convert your code into their language of choice, could you add a few
>> more comments to your code, especially in the snippets we see in the
>> article?
>
> Could you possibly give me an example? Like from the
> Article One source?

I could try my hand at that.

// This is the minimalist console output class I mentioned.
#include "ExtendedWin32Console.h"
// Please tell me what this is for.
#include <conio.h>

int main( void )
{
console.Clear(); // Blank the screen.

int nPlayerX=40, nPlayerY=12; // Set the player's starting position.

while( true )
{
// Output phase: set the write position to the player's position
// then print "@" to represent the player.
console.SetPosition( nPlayerX, nPlayerY );
console << '@';

// Input phase: wait for a key to be typed.
char nKey = getch();

// Erase the character from the previous position
console.SetPosition( nPlayerX, nPlayerY );
console << ' ';

// Processing phase: choose an action based on the key pressed.
switch( nKey )
{
// Move down
case '2':
nPlayerY++;
break;

// Move left
case '4':
nPlayerX--;
break;

// Move right
case '6':
nPlayerX++;
break;

// Move up
case '8':
nPlayerY--;
break;

// Quit
case 'Q':
case 'q':
return 0;
break;
}
}

return 0;
}

I'm thinking it would be nice to insert a note saying what a function or
#include does the first time it is encountered, as well as what variable
names are for, and what a particular technique is doing (like the
console.SetPosition then console << "*" technique, the "read a character
then act on it technique", and so on). I wouldn't bother to cover the
language basics, but as a reader when I come to a case statement labeled
"processing phase" I would like to know in general terms what we plan to
process.

Of course, I'm experienced enough to understand what this code is going to
do, but presumably your main audience isn't.
 >> Stay informed about: The Beginners Guide to Roguelikes (v 0.0.0.0.0.0.1a) 

On 22 marras, 19:49, Craig <craig.stic... RemoveThis @gmail.com> wrote:
> I apologize for that. Here's the HTML version.

Don't you have anywhere to put that? Like home page
or something?
 >> Stay informed about: The Beginners Guide to Roguelikes (v 0.0.0.0.0.0.1a)