Archive for category Roguelike Development

Debug Binary Available

Since I’ve spent a cou­ple of days try­ing to get back to the point I was with the LibTCOD/Python ver­sion of Cyber­Rogue, I’ve man­aged to get there (or there­abouts). In hon­our of that mile­stone, I’ve decided to release a Win­dows binary to the pub­lic. I would never have got­ten this far with­out the help of jice, min­gos, and oth­ers at the Doryen Library forums, being the C++ new­bie that I am. To them, my eter­nal thanks.

Suf­fice to say that there are prob­a­bly many bugs with this, and I will update as time goes on. The cur­rent down­load con­tains 5 dif­fer­ent FOV algo­rithm ver­sions, used for test­ing (and fix­ing my errors).

[Down­load not found]

, , , ,

5 Comments

Boost? More like deflated…

After fight­ing for a day with Boost, I’m pretty much going to give up. I’ve finally man­aged to build the libraries, but I needed to upgrade gcc (MinGW) to 4.4.0 (from Code­Blocks default of 3.4.5, which still works with it, fortunately).

When I import the string algo­rithms into my own code I get a whole slew of errors (over 50), and when I try the demo code I still get errors (OK, not so bad, just “expected con­struc­tor, destruc­tor, or type con­ver­sion before ‘(‘ token” on two lines, but it should still work “out of the box” right?) (OK, I’ve got dain bra­m­age… I made a proper pro­gram (no out­put) but I’ve got the “test” work­ing — now to get it work­ing in Cyber­Rogue)

Am I doing some­thing wrong, try­ing to use two con­flict­ing libraries (LibT­COD and Boost, but I didn’t think they’d con­flict?), or is MinGW just not up to the job and I should try Cyg­Win (will LibT­COD work with Cyg­Win?) Maybe I should just stick with what I’ve already got as it works (ain’t broke, don’t fix it approach).

Fixed: OK, maybe I should have just checked my defines — it’s work­ing, yay! Now I just need to use it.

, , , , , , ,

No Comments

Moving moving moving…

[Sung to “Rawhide” — at least I think that’s what it is]

In case you hadn’t noticed, I’m mov­ing this project to a new domain — this gives me a lot more con­trol over what I can do with it, includ­ing proper anony­mous SVN access (I don’t have a real SSL cert yet though — not entirely sure about “anony­mous” in a browser, but it works in Tor­tois­eSVN) and a Trac data­base (same again, and still in the process of being added — this will let you down­load the source as a zip, how­ever). There will be more to come over the next few weeks, includ­ing my efforts on a C++ ver­sion of Cyber­Rogue (which, if I can actu­ally get my head around it enough, will become the main ver­sion I’ll work on — Python, while nice to work in, doesn’t appear to run fast enough, even with the use of Psyco)

Things might be a lit­tle “bro­ken” for a while (I had to change themes as it didn’t sur­vive the migra­tion, but I think this one looks cleaner, some­how) so I’m happy to receive com­ments on issues.

Your friendly neigh­bour­hood Scautura

No Comments

More Interface

I’ve finally had some time to grind some more code out, so I’ve man­aged to get the inter­face into a lit­tle more shape. Cur­rently, the lit­tle @ can move, cast a light (blue is a place­holder so I can com­pare with “unlit” space) and tell you he’s run into a wall (or some things — cur­rently, because of the way “fea­tures” are imple­mented, cor­ners cur­rently have two walls and tell you that you ran into “some things”) and save/load the game. The con­fig save/load is a bit “ehh” because Python’s con­fig file han­dling is a bit weird — it won’t deal with hav­ing upper­case in the vari­able name (so “KP8=north” ends up being “kp8=north” but “wibble=WoBbLe” stays the same). I’ll work around it.

Com­ments on the cur­rent inter­face are welcome.

[Gallery not found]

, , ,

No Comments

The Warrior’s Solution

Andrew Doull over at Ascii Dreams made a com­ment on The Warrior’s Dilemma and how they should dif­fer from magic users (he’s had fur­ther com­ments on this too) to which I responded with my own ideas. Now I’ve had more time to think about it, I fig­ured I’d flesh it out a bit fur­ther here. Read more after the break (for clar­ity). Read the rest of this entry »

, , , , ,

No Comments