angband
DOOM
Our great sponsors
angband | DOOM | |
---|---|---|
20 | 91 | |
1,257 | 12,516 | |
1.8% | 2.8% | |
9.4 | 3.6 | |
4 days ago | 2 months ago | |
C | C++ | |
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
angband
-
How I installed the Linux version of angband from the aur repository on to my steam deck.
And it worked, it downloaded and installed angband however with a font glitch that can be resolved with a command I found from ( https://github.com/angband/angband/issues/4575 )
-
Working on my first procedural-level generator.
Broge, Angband, C:DDA, Dungeon Crawl Stone Soup, are some options.
- C Roguelike Resources?
-
Reading source code for learning purposes.
Angband
-
People To Make Games With: A Free Resource
There is a way to get many people contributing and collaborating to a single project over extended periods, even as individual people come and go. That way is called free and open-source software. See e.g. Dungeon Crawl: Stone Soup, Brogue: Community Edition, Angband, Cataclysm: DDA.
- Suggestions for games that can be played on the terminal
-
Angband 4.2.2: A free, single-player roguelike dungeon exploration game (Mar-21)
It's notable that a big reason that Angband has a large number of variants is because a lot of its data is in easily readable, editable flat text files. For instance:
https://github.com/angband/angband/blob/master/lib/gamedata/...
This allowed people to start work on variants without having to write C or even recompile. Also, Angband's source code has a reputation for being pretty clean and easy to understand and modify.
Oook. The original link went straight to Github and was date gated. For the sake of posterity: [0].
Since this project doesn't seem to have been discussed on HN before, I've switched the URL from https://github.com/angband/angband/releases/tag/4.2.2 to the main project page.
DOOM
-
Doom Released Under GPLv2
commercially exploit or use for any commercial purpose."
[1] https://github.com/id-Software/DOOM/commit/4eb368a960647c8cc...
This Github repo was previously released with this license:
https://github.com/id-Software/DOOM/blob/77735c3ff0772609e9c...
-
GTA 5 source code leaks online
The original Doom had third-party audio playback routines, so the source came with a rewritten sound server: https://github.com/id-Software/DOOM/tree/master/sndserv
The bad news: this code only compiles and runs on linux. We couldn't
-
Software Disenchantment
Here's a repo for you with no test coverage and no auto-generated DI. They using unsafe pointers all over the place, too!
https://github.com/id-Software/DOOM
Shall I prepare the postage for the letter in which you'll call John Carmack an MBA? Should we send another to Chris Sawyer? I heard he didn't even write a formal design doc for Roller Coaster Tycoon!
-
Ask HN: Good practices for my first C project
cURL is one of the most used C libs and is an example of good quality C code. If you follow the style used there, see e.g. https://github.com/curl/curl/blob/master/lib/dynhds.h (and associated dynhds.c) you will be good.
Looking at the source of some of the old game-engines from the era that have since been released as open-source can also be helpful, like https://github.com/id-Software/DOOM.
In both cases notice how simple and elegant a lot of the code is. There is already enough complexity inherent in the problem they are solving, and that is where the focus should be.
Any IDE with a working language server to make it easy to jump around and refactor should work fine. Limitations might be due to the C language itself?
Error handling on such a fixed platform does not need to be super-advanced. You should always be within the confines of the system so there shouldn't be much that can go wrong. If stuff goes wrong anyway just being able call a function Fatal("FooBar failed with code 34") when unexpected stuff happens and have it log somewhere to be able to dig around should be enough. You never need to be able to recover and retry.
Make sure to use https://clang.llvm.org/docs/AddressSanitizer.html or a similar tool when developing outside of the PSOne.
That said, consider statically allocating global buffers for most stuff and avoid using the heap for most stuff.
Good luck working within the confines of the PSOne! Many hackers have pulled the hair from their head on that platform ;)
- Ask HN: Where do I find good code to read?
-
Running Stable Diffusion in 260MB of RAM
Probably more easily than you'd think. DOOM is open source[1], and as GP alludes, is probably the most frequently ported game in existence, so its source code almost certainly appears multiple times in GPT-4's training set, likely alongside multiple annotated explanations.
-
Some were meant for C [pdf]
I'd define an arena as the pattern where the arena itself owns N objects. So you free the arena to free all objects.
My first job was at EA working on console games (PS2, GameCube, XBox, no OS or virtual memory on any of them), and while at the time I was too junior to touch the memory allocators themselves, we were definitely not malloc-ing and freeing all the time.
It was more like you load data for the level in one stage, which creates a ton of data structures, and then you enter a loop to draw every frame quickly. There were many global variables.
---
Wikipedia calls it a region, zone, arena, area, or memory context, and that seems about right:
https://en.wikipedia.org/wiki/Region-based_memory_management
It describes history from 1967 (before C was invented!) and has some good examples from Apache ("pools") and Postgres ("memory contexts").
I also just looked at these codebases:
https://github.com/mit-pdos/xv6-public (based on code from the 70's)
https://github.com/id-Software/DOOM (1997)
I looked at allocproc() in xv6, and gives you an object from a fixed global array. A lot of C code in the 80's and 90's was essentially "kernel code" in that it didn't have an OS underneath it. Embedded systems didn't run on full-fledges OSes.
DOOM tends to use a lot of what I would call "pools" -- arrays of objects of a fixed size, and that's basically what I remember from EA.
Though in g_game.c, there is definitely an arena of size 0x20000 called "demobuffer". It's used with a bump allocator.
---
So I'd say
- malloc / free of individual objects was NEVER what C code looked like (aside from toy code in college)
- arena allocators were used, but global vars and pools are also very common.
- arenas are more or less wash for memory safety. they help you in some ways, but hurt you in others.
The reason C programmers don't malloc/free all the time is for speed, not memory safety. Arenas are still unsafe.
When you free an arena, you have no guarantee there's nothing that points to it anymore.
Also, something that shouldn't be underestimated is that arena allocators break tools like ASAN, which use the malloc() free() interface. This was underscored to me by writing a garbage collector -- the custom allocator "broke" ASAN, and that was actually a problem:
https://www.oilshell.org/blog/2023/01/garbage-collector.html
If you want memory safety in your C code, you should be using ASAN (dynamically instrumented allocators) and good test coverage. Arenas don't help -- they can actually hurt. An arena is a trivial idea -- the problem is more if that usage pattern actually matches your application, and apps evolve over time.
-
Is it possible to see the code of 90s computer games?
Doom might be the best one, they released their code i don't remember when. It's in github if you want to check it out: link
What are some alternatives?
NetHack - Official NetHack Git Repository
sil-q
crawl - Dungeon Crawl: Stone Soup official repository
FAangband - First Age Angband
open-watcom-v2 - Open Watcom V2.0 - Source code repository, Wiki, Latest Binary build, Archived builds including all installers for download.
project-based-tutorials-in-c - A curated list of project-based tutorials in C
how-to-mod-roguelikes - A walkthrough on creating your own variants of free and open-source roguelike games
Apollo-11 - Original Apollo 11 Guidance Computer (AGC) source code for the command and lunar modules.
doomgeneric - Easily portable doom
luxtorpeda - Steam Play compatibility tool to run games using native Linux engines
Cataclysm-DDA - Cataclysm - Dark Days Ahead. A turn-based survival game set in a post-apocalyptic world.
open-source-flash - Petition to open source Flash and Shockwave spec