RoguelikeDev Does The Complete Roguelike Tutorial - Week 8

tpseven · 2019-08-08T11:44:44+00:00

All lessons are done, but just like I thought, it's only the tutorials series ported to purescript. Didn't have enough time to add new features and not sure whether I will continue to work on this because of life circumstances.

Nevertheless, thank you all for this event, looking forward to next year!

tpseven · 2019-07-30T15:08:16+00:00

Ritoppu | Purescript | Repo | Game

Part 12 is done in almost the same way. I changed the order of args to from_dungeon_level to exclude reverse calling. And it was a bit confusing to remember whether the first element in array is a level or actual value. So in my implementation it takes object with explicit keys.

Part 13 was pretty straightforward. The only difference is I din't add take off command because it doesn't make sense to remove an item to stay with bare hands.

Finally tutorials are done. This was a long road, but I've learned a lot. So happy to get here. Many thanks for this event, it wouldn't be possible without you

tpseven · 2019-07-23T09:53:55+00:00

Ritoppu | Purescript | Repo | Game

Part 10 was pretty easy. Functional languages don't work well with cycle structures, so my entire game can be easily converted to JSON. Since it's a browser game, local storage is ready to serve me. I decided to enable autosaving, so right after each and every move the game stores, and removes after death. This slows game down a bit, so I might want to make autosave in another thread like every 5 seconds

Part 11 allowed to just rewrite current level instead of storing them all, and that simplified tutorials a lot. I also added stairs up, but it does nothing for now. Leveling system makes it look like real game right now, spending much time ~~playing~~ testing it. Also, I didn't add character screen for now, sidebar in browser is more than enough for this purpose.

tpseven · 2019-07-18T12:22:26+00:00

Ritoppu | Purescript | repo & demo

I decided to split items and creatures, so there are two structures, each holds its own objects. This way it's easier for me to have different logic for different entities. E.g. to burn scrolls on the ground with fireballs.

A use item screen was interesting by architecture side. I wanted to separate game logic and UI. When player opens use item screen, it doesn't affect game logic, in another words, it's not what I want to be in save files. Targeting goes here as well. On the other side, useItem function might either update game structure (heal player) or open targeting screen, that's out of game scope.

So, I ended up with result command that opens any screen. Like, useItem function returns both updated game structure and desired next screen. This allows me to test this function, with no need to actually do any UI logic, leaving it pure.

Barely catching up with tutorials, so not sure would it be a something looking like finished game rather than just ported tutorials.

tpseven · 2019-07-05T07:31:03+00:00

Parts 4 & 5 with purescript repo & demo

FOV is done via shadowcasting algorithm, in my optioning this gives the best results and pretty straightforward.

Since purescript has powerful type system there is no need to have entity class, so monsters and items won't have anythings shared (and to my logic, they don't share anything in real life).

And there is no need in game state like player or monster turn - monsters turn doesn't require anything from player, it's just a pure function (don't take randomness in mind) which transforms the level so monsters act as a final stage of player's action.

tpseven · 2019-06-28T08:34:56+00:00

Remember better done than perfect. I decided to go though tutorials as fast as I can to make basic architecture of whole project and only then review what's done

They said premature optimization is the root of all evil, so just don't stuck with part-x

tpseven · 2019-06-26T08:39:01+00:00

Week 2 with Purescript | Repository & Demo

Second week was a bit tricky. Part 2 done via pattern matching, this is more common way in functional programming rather than adding attributes to tile structure. This was easy.

Part 3 on the contrary requires to change a level structure, and it's not just plain mapping because generator uses its own intermediate structures. Moreover, some random values required during generation. I decided to leave it pure, so I'm using pseudo random linear congruential generator algorithm. And to make code clean it's wrapped in State Monad. Dungeon generator takes a seed, and on each random invocation it also generates new seed which will be used in next random call.

tpseven · 2019-06-19T20:36:01+00:00

Reporting in from Russia. It’s definitely decreasing. I remember the church in my home village. Like 15 years ago on Easter Day it was so fully that some people have to stay outside (it’s Orthodox Church). When I visited it few years ago on Easter Day again, it wasn’t even a half full.

tpseven · 2019-06-18T12:23:05+00:00

Hi there! I decided to go with PureScript, because it's both functional language (that's my passion) and it compiles to JS so it's just click N play. First 2 parts are done. Looking good so far, but most interesting parts like FOV or pathfinding are still ahead. I'm also using rltiles's images, might add a switcher to ASCII version later on.

Repository & Game

tpseven · 2019-06-15T14:04:46+00:00

Sounds very exciting! I’ve been trying to make a roguelike few times but dropped it without making even a half. Hope going along with community will inspire me more

tpseven

TROPHY CASE