Beleriand VS bracket-lib

This week I had what I hope was a moment of clarity about the Beleriand map. Previously it was pretty big; 12x15 map grids, each map grid 49x49 miles, each square mile 10x10 chunks, each chunk 22x22 game grids, which made a grid notionally 8 yards on a side. But I've been feeling for a while that that is too big for adjacent things to be in contact. So I considered what would happen if I cut that size down to 2 yards on a side. I was happier with that size in terms of realism, but it does multiply the number of total grids in the map by 16, and there were already 20 billion. What to do?

I have done some "wilderness generation" in FAangband by having a base type of terrain for each biome type, and then adding "formations" (random groups of selected other terrain types) and then maybe some other areas (grassed clearings in forest, for example). FAangband has discrete wilderness levels, so the scaling/zooming doesn't apply. I am, though, coming up against similar problems to yours in Beleriand, which has a fixed world map with set biomes at the top level, but has to fill in all the terrain in a natural way. Note that Beleriand is still in its very early stages.

I think having to use a terminal is the scary part for many people. rltk/bracket-lib can be used to get a similar look and feel if that's what's important, but it is geared toward roguelikes.

Maybe bracket-lib from the amethyst authors? I‘m currently working through that book and find the library quite intuitive and simple to use. It started out as a toolkit for rouge-like games but has been getting more general. On that note, I recommend the hands-on-rust book which teaches rust concepts while building games with bracket-lib. As you have read the book, I‘m sure you would get through the first chapters quickly.

https://github.com/amethyst/bracket-lib has a great integration with Bevy, designed for exactly this sort of thing.

I've been doing some experiments with terminal based games and landed on https://github.com/amethyst/bracket-lib It's not exactly terminal based in the sense that it actually runs on OpenGL by default. But that's a plus imho because dealing with the bits of the terminal window that can change outside of your control (like fonts, window resize, etc) is a giant pita. It does let you swap the backend to run on crossterm if that's what you really want to do but if what you're after is the aesthetic like I am having bracket_lib handling all that makes life so much better.

Bracket-Lib for Bevy Github

Bracket-Terminal/RLTK for Bevy Github Branch | Twitter | Patreon

bracket-lib 👈🏻 (using this now)