Print

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

[Epithemius]

And that may be some of the prettiest ASCII I've ever seen.

The look of the game is pretty damn great. I like that when not actively moving your character, the environment is still moving, not frozen in time. The cloud shadows are a great idea. Same with the reflective water, it's still ACSII, but much more detailed and realistic.

[Lord Dullard]

Currently working on pathfinding for point-and-click maneuvering of the PC (and of course I'll need the algorithm later for NPCs, too). After that I'm going to be doing some more work on the regional map generator, which will probably take a significant amount of time, since I have to account for so many different potential biomes.

[Max White]

I thought libcod came with path finding algorithms for you to use.

[Willfor]

I thought libcod came with path finding algorithms for you to use.

Imagine how much libtcod clashed with how you wanted to work with the graphics and interface. Now imagine that same circumstance as applying to libtcod's pathfinding capabilities.

[Max White]

Eh, that had more to do with the horrid way it handled input. From my short testing of it, it did lighting and path finding alright.

[Lord Dullard]

Yes, it comes with path finding in both A* and Dijkstra's implementations.

I'm not terribly interested in using them, since I'm also probably not going to be using libtcod's FOV, and its path finding is dependent on the use of its FOV maps.

And the simple and short answer is: I'd rather do it myself.

[Max White]

Ah, an respectable answer if ever I knew one.

[Lord Dullard]

This does, however, bring me to an interesting impasse. Up until now I'd pretty much planned on making the game real-time as opposed to turn-based, since I have a number of ideas that would simply work better if that were the case. But, if anybody has any arguments as to why I shouldn't do this, now would be the time to put them forth, before I start writing time-based movement. Any thoughts?

[Max White]

You are only using libtcod for graphics, right? Not input?

[Lord Dullard]

The input has worked just fine and dandy, for me. No problems at all thus far.

[Max White]

Well see how it goes, but I love real time roguelikes.

[Knight of Fools]

I'm all for real time, as long as you can easily pause it.

[Lord Dullard]

A* algorithm complete, and appears to be working well thus far.

[nenjin]

I prefer turn-based in games like this. Imagine DF with no ability to stop and smell the roses.

I'm ok with real-time, but if I had my druthers it would have an active pause key like DF, where you can punch it to freeze time but you can still operate the UI, look around, gather information, ect....

[Lord Dullard]

I prefer turn-based in games like this. Imagine DF with no ability to stop and smell the roses.

I'm ok with real-time, but if I had my druthers it would have an active pause key like DF, where you can punch it to freeze time but you can still operate the UI, look around, gather information, ect....

That's pretty much what I had planned.

Real-time, but with a pause key that would allow the player to gather information and also make tactical decisions (a la Dragon Age or Mass Effect, albeit a lot more detailed than that). But I'd prefer the ability to maintain real-time combat with MMO-like hotkeys/shortcuts. As much as I love old-school roguelikes, I much prefer the fluidity of real-time combat.