rogueclone-devel — Discussion amongst rogue clone developers

[rogueclone-devel] interrupt on introduction prompt inquery

[Chris H. <ch...@gm...>]

Hello everyone,

I'[m trying to compile a fresh build of the rogue clone from source. I'm
currently reasearching on RNG behavior and figured that this would be a
good place to start. Unfortunately after compiling the makefile using
visual studio 2015 I find that my .exe stalls after the introduction line
prompt everytime I run it. I'm not so familiar with the library p[roperties
so I was hoping that maybe someone from the developers log could offer some
advice. Any help you could offer would be greatly appreciated.

Regards,
Chris Hoy

Re: [rogueclone-devel] [rogueclone-cvs] Fixes for Rogue Clone IV in the Windows 7 / 8 / 10 console environment

[William A. <wil...@au...>]

Michael:

 

Can you give me a procedure you would like me to follow to submit patches?
I'm generally familiar with linux tools (e.g. diff, cvs, etc.) but I've
never submitted to a SourceForge project.

 

Thanks,

 

Willie

 

From: Michael Lehotay [mailto:mle...@gm...] 
Sent: Friday, February 05, 2016 3:57 PM
To: William Anderson; rog...@li...
Subject: Re: [rogueclone-cvs] Fixes for Rogue Clone IV in the Windows 7 / 8
/ 10 console environment

 

Hi Willie,

Thank you for your efforts. Yes, I'm interested in any contributions you
have to the project!

Can you submit a patch with your changes?

Thanks,
Michael

On 2/3/2016 6:45 PM, William Anderson wrote:

Rogue Clone IV Developers,

 

I have a fix to an annoying issue in Rogue Clone IV for the newer Windows
environments. Evidently, around about Windows 7 and since, the Visual Studio
console environment has not supported a "bell" function. That is, there no
sound generated when you send ASCII 7 (or CTL-g or '\a', whatever your
preference) to stdout.

 

Moreover, on my system, when the bell character was sent to the console, the
console promptly dies, leaving a zombie rogue.exe process spinning in the
background. So you lose your game, and you are burning cycles; not good. If
you play Rogue at a reasonable pace (like me - my brain doesn't play the
game, my fingers do) then a bell will inevitably come, and there goes the
game. I have tested the download from sourceforge on my machine, and sure
enough, it exhibits this same behavior.

 

I have a relatively simple solution that I have implemented and  tested. It
uses the Windows multimedia system and plays a .wav file (my default file is
the sound of a metal-on-metal "clank") whenever the bell is invoked.
Admittedly, this is more like Windows than Unix, where I first played BSD
Rogue. But, hey, it works.

 

There are other issues to work around when compiling this code with a
modern language system like, ahem, Visual Studio 2015. The issue of const
string literals will kill you if you try to compile in a modern C/C++
syntax. Luckily, Visual Studio seems to have the flags that allows old,
crazy C code to be compiled. I spent most of a day figuring this out.

 

Since this is a structural change (one more source file, plus the .wav sound
file), I wanted to find out if this mailing list would approve this update.
Let me know.

 

Willie Anderson

 






----------------------------------------------------------------------------
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151
<http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140> &iu=/4140






_______________________________________________
rogueclone-cvs mailing list
rog...@li...
https://lists.sourceforge.net/lists/listinfo/rogueclone-cvs

 

Re: [rogueclone-devel] [rogueclone-cvs] Fixes for Rogue Clone IV in the Windows 7 / 8 / 10 console environment

[Michael L. <mle...@gm...>]

Hi Willie,

Thank you for your efforts. Yes, I'm interested in any contributions you 
have to the project!

Can you submit a patch with your changes?

Thanks,
Michael

On 2/3/2016 6:45 PM, William Anderson wrote:
>
> Rogue Clone IV Developers,
>
> I have a fix to an annoying issue in Rogue Clone IV for the newer 
> Windows environments. Evidently, around about Windows 7 and since, the 
> Visual Studio console environment has not supported a “bell” function. 
> That is, there no sound generated when you send ASCII 7 (or CTL-g or 
> ‘\a’, whatever your preference) to stdout.
>
> Moreover, on my system, when the bell character was sent to the 
> console, the console promptly dies, leaving a zombie rogue.exe process 
> spinning in the background. So you lose your game, and you are burning 
> cycles; not good. If you play Rogue at a reasonable pace (like me – my 
> brain doesn’t play the game, my fingers do) then a bell will 
> inevitably come, and there goes the game. I have tested the download 
> from sourceforge on my machine, and sure enough, it exhibits this same 
> behavior.
>
> I have a relatively simple solution that I have implemented and 
>  tested. It uses the Windows multimedia system and plays a .wav file 
> (my default file is the sound of a metal-on-metal “clank”) whenever 
> the bell is invoked. Admittedly, this is more like Windows than Unix, 
> where I first played BSD Rogue. But, hey, it works.
>
> There are other issues to work around when compiling this code with a 
>   modern language system like, ahem, Visual Studio 2015. The issue of 
> const string literals will kill you if you try to compile in a modern 
> C/C++ syntax. Luckily, Visual Studio seems to have the flags that 
> allows old, crazy C code to be compiled. I spent most of a day 
> figuring this out.
>
> Since this is a structural change (one more source file, plus the .wav 
> sound file), I wanted to find out if this mailing list would approve 
> this update. Let me know.
>
> Willie Anderson
>
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
>
>
> _______________________________________________
> rogueclone-cvs mailing list
> rog...@li...
> https://lists.sourceforge.net/lists/listinfo/rogueclone-cvs

[rogueclone-devel] Fixes for Rogue Clone IV in the Windows 7 / 8 / 10 console environment

[William A. <wil...@au...>]

Rogue Clone IV Developers,

 

I have a fix to an annoying issue in Rogue Clone IV for the newer Windows
environments. Evidently, around about Windows 7 and since, the Visual Studio
console environment has not supported a "bell" function. That is, there no
sound generated when you send ASCII 7 (or CTL-g or '\a', whatever your
preference) to stdout.

 

Moreover, on my system, when the bell character was sent to the console, the
console promptly dies, leaving a zombie rogue.exe process spinning in the
background. So you lose your game, and you are burning cycles; not good. If
you play Rogue at a reasonable pace (like me - my brain doesn't play the
game, my fingers do) then a bell will inevitably come, and there goes the
game. I have tested the download from sourceforge on my machine, and sure
enough, it exhibits this same behavior.

 

I have a relatively simple solution that I have implemented and  tested. It
uses the Windows multimedia system and plays a .wav file (my default file is
the sound of a metal-on-metal "clank") whenever the bell is invoked.
Admittedly, this is more like Windows than Unix, where I first played BSD
Rogue. But, hey, it works.

 

There are other issues to work around when compiling this code with a
modern language system like, ahem, Visual Studio 2015. The issue of const
string literals will kill you if you try to compile in a modern C/C++
syntax. Luckily, Visual Studio seems to have the flags that allows old,
crazy C code to be compiled. I spent most of a day figuring this out.

 

Since this is a structural change (one more source file, plus the .wav sound
file), I wanted to find out if this mailing list would approve this update.
Let me know.

 

Willie Anderson

 

[rogueclone-devel] Purpose of machdep.c

[Tinker T. <tin...@gm...>]

I found something in the source called Machdep.c but couldn't quite figure
out the purpose of it. What does this code do, and how careful should
someone be editing it?

[rogueclone-devel] Help with roguelike classics

[<car...@gm...>]

Love your app, it's why i bought an old droid with a keyboard instead of  
getting a new one for cheaper. I just beat rogue for the 2nd time ever, and  
when I opened it again it continued my winning game from level 1 so i was  
able to go back down with my awesome PC. The next game i played did the same  
thing, continued from where i died once. Is this a bug, or a prize for  
winning? It has not happened a third time. I spent the last hour trying to  
figure out how to do the old cheat of backing up my save, but android only  
seems to have a move function and no copy function. I know this probably is  
't why you provided this e-mail address in the text file, but any help would  
be greatly appreciated. Again, love your app. Thank you for the great port  
of my child hood favorite.
Carter McLaughlin
Connected by DROID on Verizon Wireless

Re: [rogueclone-devel] A little project

[Michael L. <mle...@gm...>]

Hey Tinker Toy,

Yes, I fully support anything you want to do with this code. There aren't
really any developers anymore, it's been a few years since anything has
happened with this project. Somebody else has worked on ANSI C compliance
in the past. Their work is on a branch in the cvs repository. I can't
remember the details right now, but if you need any help I would be happy
take the time to refresh my memory and lend a hand getting the updated code
into your working copy.

Cheers,
Michael


On Mon, May 7, 2012 at 12:35 PM, Tinker Toy <tin...@gm...> wrote:

> Hello, everyone! I've undertaken an endeavor to clean up the source code a
> bit, beginning with installing ANSI C compliance. I'm a relatively new to
> the programming game, but I feel that this will be a good way for me to
> learn. Therefore, I want to inform the remaining devs, AND ask for their
> support.
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> rogueclone-devel mailing list
> rog...@li...
> https://lists.sourceforge.net/lists/listinfo/rogueclone-devel
>
>

[rogueclone-devel] A little project

[Tinker T. <tin...@gm...>]

Hello, everyone! I've undertaken an endeavor to clean up the source code a
bit, beginning with installing ANSI C compliance. I'm a relatively new to
the programming game, but I feel that this will be a good way for me to
learn. Therefore, I want to inform the remaining devs, AND ask for their
support.

Re: [rogueclone-devel] Compiling Rogue Clone IV problems

[Michael L. <mle...@gm...>]

I'm not all that surprised it doesn't work anymore. I'll take a look at 
it in a day or two and get back to you.

If you can't wait, my initial advice that you need to fiddle with the 
HAVECURSES or ROGUECURSES macro (depending on which version of the 
source code you have), or to link with a curses library like ncurses or 
pdcurses.

-Michael


Donovan Rogers wrote:
> I am trying to compile Rogue Clone IV with Open Watcom and I am not 
> having much success.
> 
> Here are some of the details:
> 
> Open Watcom version 1.8
> I believe i have the latest code from sourceforge
> I changed the Makefile to use the file named "wcc386.exe" as the version 
> of Watcom I have didn't have a "wcc.exe"
> If I follow the instructions in the compile.txt I get a whole bunch of 
> compiler errors from the curses.c file which I attached as file 
> compileresults.txt
> 
> Any advice would be greatly appreciated.  Thanks in advance.
> 
> 
> Donovan
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and 
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today. 
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> rogueclone-devel mailing list
> rog...@li...
> https://lists.sourceforge.net/lists/listinfo/rogueclone-devel

[rogueclone-devel] Compiling Rogue Clone IV problems

[Donovan R. <dr...@gm...>]

D:\downloaded\applications\games\rogue source>wmake
Open Watcom Make Version 1.8
Portions Copyright (c) 1988-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
See http://www.openwatcom.org/ for details.
        wcc386 src\curses.c -bt=dos -mm -zq -w2 -ox -fr -fo=o\
src\curses.c(232): Warning! W131: No prototype found for function 'save_screen'
src\curses.c(266): Warning! W107: Missing return value for function 'initscr'
src\curses.c(275): Warning! W107: Missing return value for function 'move'
src\curses.c(288): Warning! W131: No prototype found for function 'addch'
src\curses.c(290): Warning! W107: Missing return value for function 'addstr'
src\curses.c(299): Warning! W107: Missing return value for function 'mvaddstr'
src\curses.c(308): Warning! W131: No prototype found for function 'addcch'
src\curses.c(311): Warning! W107: Missing return value for function 'addstr_in_color'
src\curses.c(318): Warning! W107: Missing return value for function 'mvaddstr_in_color'
src\curses.c(326): Warning! W107: Missing return value for function 'addcstr'
src\curses.c(333): Warning! W107: Missing return value for function 'mvaddcstr'
src\curses.c(354): Warning! W107: Missing return value for function 'addch'
src\curses.c(360): Warning! W107: Missing return value for function 'mvaddch'
src\curses.c(372): Warning! W107: Missing return value for function 'addcch'
src\curses.c(378): Warning! W107: Missing return value for function 'mvaddcch'
src\curses.c(394): Warning! W107: Missing return value for function 'colorize'
src\curses.c(428): Warning! W107: Missing return value for function 'refresh'
src\curses.c(432): Warning! W107: Missing return value for function 'redraw'
src\curses.c(463): Warning! W107: Missing return value for function 'clear'
src\curses.c(475): Warning! W107: Missing return value for function 'clrtoeol'
src\curses.c(485): Warning! W107: Missing return value for function 'standout'
src\curses.c(490): Warning! W107: Missing return value for function 'standend'
src\curses.c(539): Warning! W107: Missing return value for function 'endwin'
src\curses.c(543): Warning! W107: Missing return value for function 'crmode'
src\curses.c(547): Warning! W107: Missing return value for function 'noecho'
src\curses.c(551): Warning! W107: Missing return value for function 'nonl'
src\curses.c(661): Error! E1031: Name 'cx' not found in struct/union REGPACKX
src\curses.c(666): Warning! W107: Missing return value for function 'put_color_char_at'
src\curses.c(689): Warning! W107: Missing return value for function 'put_cursor'
src\curses.c(708): Warning! W107: Missing return value for function 'clear_buffers'
src\curses.c(732): Error! E1031: Name 'ax' not found in struct/union REGPACKX
src\curses.c(733): Error! E1031: Name 'bx' not found in struct/union REGPACKX
src\curses.c(736): Warning! W107: Missing return value for function 'cls'
src\curses.c(770): Warning! W107: Missing return value for function 'wrefresh'
Error(E42): Last command making (o\curses.obj) returned a bad status
Error(E02): Make execution terminated

D:\downloaded\applications\games\rogue source>

[rogueclone-devel] curses patch

[Michael L. <mle...@us...>]

I managed to link with pdcurses, but it's still a bit buggy. I don't 
expect to have very much free time for a little while now, so I've 
uploaded my efforts to the patch tracker. If anybody wants to have a look, 
there it is.

ML

[rogueclone-devel] ncurses & control characters

[Michael L. <mle...@us...>]

I don't think anybody actually reads this mailing list but I will post my 
message anyway. Maybe it will be funny in a year or two.

I am trying to make rogue clone use curses again. The following program 
works just fine in Windows (win2k, djgpp, pdcurses). But in Linux 
(knoppix, gcc, ncurses) some of the characters are printed as control 
characters (like backspaces, not like ^D). If anybody can offer any 
insights, I'd appreciate it.

I have a feeling the mailing list may do something crazy to the single 
quotes in my code when it puts this message in the web archive. That would 
be the funny part, I guess.

-ML


#include <curses.h>

#define CLR_YELLOW 1
#define CLR_BLUE 2
#define CLR_RED 3
#define CLR_WHITE 4
#define CLR_GREEN 5
#define CLR_MAGENTA 6
#define CLR_STAIRS 7

struct _screenchars {
 	chtype unx;
 	chtype ibm;
 	attr_t color;
};

struct _screenchars rchars[] = {
 	{ '@', 0x01, COLOR_PAIR(CLR_YELLOW)|A_BOLD },
 	{ ']', 0x08, COLOR_PAIR(CLR_BLUE)|A_BOLD   },
 	{ ')', 0x18, COLOR_PAIR(CLR_BLUE)|A_BOLD },
 	{ '?', 0x0D, COLOR_PAIR(CLR_BLUE)|A_BOLD },
 	{ '!', 0xAD, COLOR_PAIR(CLR_BLUE)|A_BOLD },
 	{ '*', 0x0F, COLOR_PAIR(CLR_YELLOW)|A_BOLD },
 	{ ':', 0x05, COLOR_PAIR(CLR_RED) },
 	{ '/', 0xE7, COLOR_PAIR(CLR_BLUE)|A_BOLD },
 	{ '=', 0x09, COLOR_PAIR(CLR_BLUE)|A_BOLD },
 	{ ',', 0x0C, COLOR_PAIR(CLR_BLUE)|A_BOLD },
 	                 /* vga blink = bright background */
 	{ '%', 0xF0, COLOR_PAIR(CLR_STAIRS)|A_BLINK },
 	{ '-', 0xCD, COLOR_PAIR(CLR_YELLOW) },
 	{ '|', 0xBA, COLOR_PAIR(CLR_YELLOW) },
 	{ '-', 0xC9, COLOR_PAIR(CLR_YELLOW) },
 	{ '-', 0xBB, COLOR_PAIR(CLR_YELLOW) },
 	{ '-', 0xC8, COLOR_PAIR(CLR_YELLOW) },
 	{ '-', 0xBC, COLOR_PAIR(CLR_YELLOW) },
 	{ '+', 0xCE, COLOR_PAIR(CLR_YELLOW) },
 	{ '.', 0xFA, COLOR_PAIR(CLR_GREEN)|A_BOLD },
 	{ '#', 0xB1, COLOR_PAIR(CLR_WHITE) },
 	{ '^', 0x04, COLOR_PAIR(CLR_MAGENTA) }
};

int main(void) {
     int i;

     initscr();
     start_color();

     init_pair(CLR_YELLOW, COLOR_YELLOW, COLOR_BLACK);
     init_pair(CLR_BLUE, COLOR_BLUE, COLOR_BLACK);
     init_pair(CLR_RED, COLOR_RED, COLOR_BLACK);
     init_pair(CLR_WHITE, COLOR_WHITE, COLOR_BLACK);
     init_pair(CLR_GREEN, COLOR_GREEN, COLOR_BLACK);
     init_pair(CLR_MAGENTA, COLOR_MAGENTA, COLOR_BLACK);
     init_pair(CLR_STAIRS, COLOR_BLACK, COLOR_GREEN);

     for(i=0; i<21; i++) {
 	mvaddch(i, 0, rchars[i].unx);
 	mvaddch(i, 2, rchars[i].unx | rchars[i].color);
 	mvaddch(i, 4, rchars[i].ibm | A_ALTCHARSET);
 	mvaddch(i, 6, rchars[i].ibm | A_ALTCHARSET | rchars[i].color);
     }

     refresh();
     endwin();
     return 0;
}

[rogueclone-devel] 3 patches submitted

[Michael L. <mle...@ko...>]

Steve has finished his known items patch, and an anonymous constitutor has 
submitted two small patches to fix some inefficient routines. I will look 
at these patches sometime soon-ish and sort out what I want to do with 
them. Most likely, they will be brought into the main branch of the source 
tree.

-ML

[rogueclone-devel] status report

[Michael L. <mle...@ko...>]

Hopefully I'll find some time to work on rogue soon, maybe over the
Christmas holidays. I have two things I'd like to do:

1) Link with ncurses and release a Linux port based on the current stable
code.

2) Take a closer look at all of steve_ued's patches, and probably bring
them into the main branch of the source tree.

[rogueclone-devel] release imminent

[Michael L. <le...@po...>]

I've finished everything I wanted to do with the source code and
documentation. Tomorrow I will get started on the web page, which
hopefully won't take very long. I'll get at least a preliminary version
finished and then will release version 2.1!

Michael

[rogueclone-devel] version 2.1 almost ready

[Michael L. <le...@po...>]

I think I've finished all the coding for version 2.1. I'm just going to
give it a day or two of playtesting and then get started on the
documentation and web site.

Michael

[rogueclone-devel] Windows build, name change

[Michael L. <le...@po...>]

After a long period of inactivity, I have gotten interested in rogue clone
again. I guess something about the winter makes me want to work on rogue!

I built rogue as a Windows console application (using VC98) and put my
changes in cvs. Now that DOS Rogue Clone is not just a DOS application, it
really needs a new name. I think a good one is "rogue clone IV" since it
follows Tim Stoehr's roman numeral version naming scheme. Also, IV is an
abbreviation for intravenous, which is a joke about how addictive rogue
can be.

I found a few bugs in the colour DOS code and will work on fixing them
next. Then I'll finish bringing the docs in line with the actual game
features, and make a new web page for the site. After that I think a file
release is in order!

Michael

[rogueclone-devel] Welcome to rogueclone-devel

[Michael L. <mle...@ho...>]

This is a mailing list for programmers to talk about the development of
rogue clone. Feel free to discuss game features and future directions of
rogue, implementation details, cvs setup and usage, and anything else you
can think of.

_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*.  
http://join.msn.com/?page=dept/features&pgmarket=en-ca&RU=http%3a%2f%2fjoin.msn.com%2f%3fpage%3dmisc%2fspecialoffers%26pgmarket%3den-ca