Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
rog-o-matic and rogue
110 views
Skip to first unread message
songbird
Jul 14, 2012, 10:30:42 AM7/14/12
to
dunno if anyone reads this group any more
anyways. :) reposted from rgrm...
> ...
>
> - Improved weapon handling in Rog-O-Matic to not cause
> problems with cursed weapons. Previously, at times a
> wield would fail part way through and then if the weapon
> letter happened to be a command letter it would send that
> to Rogue as a command instead of cancelling the command
> once it detected the wield didn't fail. This was causing
> a lot of other error messages to appear. I need make
> similar changes to the armor handling (not yet done).
>
> - Put the usleep delay feature I added a few versions
> ago under the control of Rog-O-Matic's '-w' (watched) option
> (makes testing go faster if it can run full blast).
>
> - Updated both Rogue and Rog-O-Matic to use the SEED
> environment variable (if set) to make it easier to replicate
> runs.
>
> Get the LATEST at:
>
> http://www.anthive.com/rog/rog.html
>
>
> - Major revision of the debugging tools/scripts. Many
> rewritten, a few added, directory structure redone.
>
> - This is not an upward compatible change, so the location
> is changed too. These allow me to run rogomatic/rogue in a
> replicable way and to turn on debugging tracing, and run
> things in series with learning on and off. Also included
> a script to compare two series runs of Rog-O-Matic/Rogue --
> helps to check if the changes I'm making actually improve
> things or fix the bug. Also was fun to run it comparing
> no-learning to learning to see how much of a difference the
> genetic algorithm actually makes. (I had a lot of fun
> writing these scripts but now that they are more mature and
> useful I can actually get back to fixing Rog-O-Matic and
> Rogue, now that I can replicate runs that hit errors at the
> deeper levels). Also, added a script to select a previous
> run from where they are stored so it can be started up
> again.
>
> at:
>
> http://www.anthive.com/rog/other/things.html
>
>
> Cheers,
>
>
> songbird
anyways. :) reposted from rgrm...
> ...
>
> - Improved weapon handling in Rog-O-Matic to not cause
> problems with cursed weapons. Previously, at times a
> wield would fail part way through and then if the weapon
> letter happened to be a command letter it would send that
> to Rogue as a command instead of cancelling the command
> once it detected the wield didn't fail. This was causing
> a lot of other error messages to appear. I need make
> similar changes to the armor handling (not yet done).
>
> - Put the usleep delay feature I added a few versions
> ago under the control of Rog-O-Matic's '-w' (watched) option
> (makes testing go faster if it can run full blast).
>
> - Updated both Rogue and Rog-O-Matic to use the SEED
> environment variable (if set) to make it easier to replicate
> runs.
>
> Get the LATEST at:
>
> http://www.anthive.com/rog/rog.html
>
>
> - Major revision of the debugging tools/scripts. Many
> rewritten, a few added, directory structure redone.
>
> - This is not an upward compatible change, so the location
> is changed too. These allow me to run rogomatic/rogue in a
> replicable way and to turn on debugging tracing, and run
> things in series with learning on and off. Also included
> a script to compare two series runs of Rog-O-Matic/Rogue --
> helps to check if the changes I'm making actually improve
> things or fix the bug. Also was fun to run it comparing
> no-learning to learning to see how much of a difference the
> genetic algorithm actually makes. (I had a lot of fun
> writing these scripts but now that they are more mature and
> useful I can actually get back to fixing Rog-O-Matic and
> Rogue, now that I can replicate runs that hit errors at the
> deeper levels). Also, added a script to select a previous
> run from where they are stored so it can be started up
> again.
>
> at:
>
> http://www.anthive.com/rog/other/things.html
>
>
> Cheers,
>
>
> songbird
narf_the_mouse
Aug 8, 2012, 7:34:27 AM8/8/12
to
Just happened to wander into .rogue and saw this.
Cool that there's still stuff happening with Rogue. :)
Cool that there's still stuff happening with Rogue. :)
songbird
Aug 8, 2012, 1:08:19 PM8/8/12
to
narf_the_mouse wrote:
> Just happened to wander into .rogue and saw this.
>
> Cool that there's still stuff happening with Rogue. :)
thanks, it has been fun to work on. :)
> Just happened to wander into .rogue and saw this.
>
> Cool that there's still stuff happening with Rogue. :)
i'm just finishing up a segfault bug fix
for rogue (mentioned in the TODO) and will
get that posted soon (tonight, or this
week sometime, i hope).
songbird
Red Blade
Aug 9, 2012, 9:19:36 PM8/9/12
to
release before I start going through the 2010 RRP trunk I have, but wanted
to know how your Rog-O-Matic worked and asked you a few questions before I
put it up.
BTW everyone here who remembers my old coredumpcentral.org site, I brought
it back last September.
Now called "Rogue Central @ coredumpcentral.org", most of the old material
was restored and some new stuff added (including "Play Online" and
"Utilities"), the page was made a lot less 1990s-Geocities-ish technically
and aesthetically, all while keeping the retro green-on-black HTML 4.01
Transitional look from last time :)
I have a few things pending my laziness to add to the site, and to go
through some stuff people sent me. If anyone hasn't seen
coredumpcentral.org, I'm back, check it out :)
--
Red Blade
President of alt.politics, alt.fan.rush-limbaugh, & talk.politics.misc
Fanfiction Committee Chairman of alt.tv.beavis-n-butthead
https://twitter.com/redblade7
http://www.libertycolumns.com/
songbird
Aug 10, 2012, 2:31:34 PM8/10/12
to
Red Blade wrote:
...
i had one e-mail from someone that sounds like you :)
7/12/12 and i sent a reply that day, but had no further
reply. send me an unmunged e-mail address and i will
gladly resend it (i don't use an unmunged address on
usenet so replying to me should get to me).
> I'm waiting for the next Slackware
> release before I start going through the 2010 RRP trunk I have, but wanted
> to know how your Rog-O-Matic worked and asked you a few questions before I
> put it up.
ok. i'm fine with answering questions here instead of
via e-mail. i much prefer it actually because then it
may help someone else out too sometime.
in that e-mail you asked about the Rogue Restoration
Project's version and how that compared, but i do not
have that version available to me at the moment to
give details (off-line at the moment).
the Rog-O-Matic version posted at:
http://code.google.com/p/rogomatic/
(let's call this AMR for Anthony Molinaro's Rogomatic) is
a direct decendant copy of what Michael L. Mauldin posted at:
http://robot-club.com/lti/
verified by me before I started making my own fixes.
AMR is effectively dead. while he's friendly when I sent
him a comment he hasn't done much with his code for years.
Which is why I copied it and set up my own local repository
in git and then have been working with that since.
the rogue version (5.4.4) that i'm using for testing
and debugging is what was also posted at:
http://code.google.com/p/rogomatic/
along with a version 3.6.3 of Rogue. i've never worked
much on it at all as i was more interested in getting
Rog-O-Matic to work with Rogue 5.4.4 instead.
> BTW everyone here who remembers my old coredumpcentral.org site, I brought
> it back last September.
>
> Now called "Rogue Central @ coredumpcentral.org", most of the old material
> was restored and some new stuff added (including "Play Online" and
> "Utilities"), the page was made a lot less 1990s-Geocities-ish technically
> and aesthetically, all while keeping the retro green-on-black HTML 4.01
> Transitional look from last time :)
>
> I have a few things pending my laziness to add to the site, and to go
> through some stuff people sent me. If anyone hasn't seen
> coredumpcentral.org, I'm back, check it out :)
i did take a look and i hope it will be helpful
to people doing work on rogues/roguelikes.
songbird
...
> Songbird, did you get my last email?
? when was it sent?
i had one e-mail from someone that sounds like you :)
7/12/12 and i sent a reply that day, but had no further
reply. send me an unmunged e-mail address and i will
gladly resend it (i don't use an unmunged address on
usenet so replying to me should get to me).
> I'm waiting for the next Slackware
> release before I start going through the 2010 RRP trunk I have, but wanted
> to know how your Rog-O-Matic worked and asked you a few questions before I
> put it up.
via e-mail. i much prefer it actually because then it
may help someone else out too sometime.
in that e-mail you asked about the Rogue Restoration
Project's version and how that compared, but i do not
have that version available to me at the moment to
give details (off-line at the moment).
the Rog-O-Matic version posted at:
http://code.google.com/p/rogomatic/
(let's call this AMR for Anthony Molinaro's Rogomatic) is
a direct decendant copy of what Michael L. Mauldin posted at:
http://robot-club.com/lti/
verified by me before I started making my own fixes.
AMR is effectively dead. while he's friendly when I sent
him a comment he hasn't done much with his code for years.
Which is why I copied it and set up my own local repository
in git and then have been working with that since.
the rogue version (5.4.4) that i'm using for testing
and debugging is what was also posted at:
http://code.google.com/p/rogomatic/
along with a version 3.6.3 of Rogue. i've never worked
much on it at all as i was more interested in getting
Rog-O-Matic to work with Rogue 5.4.4 instead.
> BTW everyone here who remembers my old coredumpcentral.org site, I brought
> it back last September.
>
> Now called "Rogue Central @ coredumpcentral.org", most of the old material
> was restored and some new stuff added (including "Play Online" and
> "Utilities"), the page was made a lot less 1990s-Geocities-ish technically
> and aesthetically, all while keeping the retro green-on-black HTML 4.01
> Transitional look from last time :)
>
> I have a few things pending my laziness to add to the site, and to go
> through some stuff people sent me. If anyone hasn't seen
> coredumpcentral.org, I'm back, check it out :)
to people doing work on rogues/roguelikes.
songbird
songbird
Aug 10, 2012, 2:40:46 PM8/10/12
to
i did get Rogue fixed and posted as:
http://www.anthive.com/rog/rogue5.4.4-ant-r1.0.5-src.tar.gz
Rog-O-Matic is still at:
http://www.anthive.com/rog/rogomatic-r1.0.2.tar.gz
songbird
Message has been deleted
songbird
Aug 11, 2012, 12:57:48 AM8/11/12
to
Red Blade wrote:
> itself, I am completely unfamiliar with it or how it works.
> Does it operate
> like a daemon that autopilots the game, or do you run it and it starts the
> game?
rog-o-matic is a C program which starts two processes
which talk to each other. one is the player process and
the other is the C program rogue, they communicate with
each other via stdin/stdout.
usually rog-o-matic will run without any input from
the screen, but if you want you can stop it and do
some things (but not all rogue commands are available,
like you can't tell the hero to quaff a potion or read a
scroll, but you can tell the hero to move in a certain
direction if it appears to be stuck). a large part of
the interface is geared towards debugging and displaying
what has been discovered.
> Also, will it work with other *n*x versions or only the one you
> maintain?
i have not tested rog-o-matic very much against any
other versions of rogue. i tried once to fire it up
against rogue 3.6.3 but it segfaulted and i didn't bother
sorting that out as i was more interested in working with
rogue5.4.4.
testing/fixing other versions of rogue is on my TODO
list for some time in the future when i finish up my
current planned fixes for rog-o-matic and whatever bugs
i come across in rogue5.4.4. right now i'm guessing i'll
start digging into these late fall or winter.
i'm hoping that any *n*x that has a C compiler,
make and curses should be able to compile and run both
of what i distribute. at present i have no reports
of anyone having trouble or having success. my
download/upload bandwidth is too limited to try
different *n*x distributions than what i have already
(Debian testing/wheezy).
songbird
>songbird wrote:
>> ok. i'm fine with answering questions here instead of
>> via e-mail. i much prefer it actually because then it
>> may help someone else out too sometime.
>>
>> in that e-mail you asked about the Rogue Restoration
>> Project's version and how that compared, but i do not
>> have that version available to me at the moment to
>> give details (off-line at the moment).
>
> The RRP version was never finished. My questions were about Rog-O-Matic
>> ok. i'm fine with answering questions here instead of
>> via e-mail. i much prefer it actually because then it
>> may help someone else out too sometime.
>>
>> in that e-mail you asked about the Rogue Restoration
>> Project's version and how that compared, but i do not
>> have that version available to me at the moment to
>> give details (off-line at the moment).
>
> itself, I am completely unfamiliar with it or how it works.
> Does it operate
> like a daemon that autopilots the game, or do you run it and it starts the
> game?
rog-o-matic is a C program which starts two processes
which talk to each other. one is the player process and
the other is the C program rogue, they communicate with
each other via stdin/stdout.
usually rog-o-matic will run without any input from
the screen, but if you want you can stop it and do
some things (but not all rogue commands are available,
like you can't tell the hero to quaff a potion or read a
scroll, but you can tell the hero to move in a certain
direction if it appears to be stuck). a large part of
the interface is geared towards debugging and displaying
what has been discovered.
> Also, will it work with other *n*x versions or only the one you
> maintain?
i have not tested rog-o-matic very much against any
other versions of rogue. i tried once to fire it up
against rogue 3.6.3 but it segfaulted and i didn't bother
sorting that out as i was more interested in working with
rogue5.4.4.
testing/fixing other versions of rogue is on my TODO
list for some time in the future when i finish up my
current planned fixes for rog-o-matic and whatever bugs
i come across in rogue5.4.4. right now i'm guessing i'll
start digging into these late fall or winter.
i'm hoping that any *n*x that has a C compiler,
make and curses should be able to compile and run both
of what i distribute. at present i have no reports
of anyone having trouble or having success. my
download/upload bandwidth is too limited to try
different *n*x distributions than what i have already
(Debian testing/wheezy).
songbird
Message has been deleted
songbird
Aug 14, 2012, 9:49:22 AM8/14/12
to
Red Blade wrote:
> On Fri, 10 Aug 2012 14:40:46 -0400, songbird wrote:
>
>>
>
> I just updated coredumpcentral.org with links to your site.
thanks!
we'll see if anyone reports any tests on other
systems than Debian or if the activity picks up.
previously, it was getting 50-100 downloads a
month.
in the meantime i'll keep working at the bugs
i know about and those i find in passing for both
rogue and rog-o-matic.
cheers,
songbird
> On Fri, 10 Aug 2012 14:40:46 -0400, songbird wrote:
>
>>
>
> I just updated coredumpcentral.org with links to your site.
thanks!
we'll see if anyone reports any tests on other
systems than Debian or if the activity picks up.
previously, it was getting 50-100 downloads a
month.
in the meantime i'll keep working at the bugs
i know about and those i find in passing for both
rogue and rog-o-matic.
cheers,
songbird
0 new messages