Yeah helion would better be a tune up of some regular source port, written in C of course. Cuz i at least understand code like that. Cpp has many dumb words. C sharp is like pretending I'm a priest and i don't know holy books and yet I have to understand something.

Hypothetically it's a fillable niche. I'm gonna be looking into that. Maybe

Like recently I've been trying to vibecode a zdoom texture editor so that i don't have to deal with garbage like slade 3. Result is okay, but without llms being able to SEE what's wrong, it's a very hard task to tell them what to fix. I know i can just deal with each part of the plan myself and that's fool proof, but I'm lazy to and want shit that i think is easy, to get it fast. Maybe i should be looking at debloating slade 3 and downporting.

However the unhealthy state of doom community makes me think it's all not worth the trouble, I'd better go vibe code some mods for Minecraft. It's also a cesspool i guess, but userbase is at least liquid and more in count at least ten times

Sort of. The requirement for a global, fixed, precomputed bsp tree means looking from the top-down, the map geometry must be static.

But you can certainly have bsp-based renderers that support moving geometry. You just need to split static and dynamic geometry apart (this is what Quake did, which is still also bsp-based).

Played d64 for the first time couple of years ago and I thought the level design was amazing, way better than classic dooms. The game's atmosphere and music were strangely enchanting. Didn't realize I had to collect some secret keys though but luckily the final boss was still beatable without them.

Wasn't bsp also the reason why doom's geometry is static? That sucks if so. As for me 35fps is preferable to play doom. Higher fps looks weird when you have sprite monsters imho.
Too bad helion is based on .net. I'd rather install a random doom port from randocoder than microsoft's malware.

the first time i played it i thought it's pretty short and simple, and it just had a large portion of optional areas, which gives me diafragmal orgasm

I just replayed Habitat today by loading a random map and I completely forgot the blue key was behind a fake wall. I guess all the times I've played it, I ran through the wall by accident and found the key anyway. I was stuck on this map for almost 30 minutes before I found it.

I've changed my mind, Habitat sucks.

Doortrak is boring.

Doortrak not used in all those maps? (E2M9, E3M2, E3M6, E4M1, E4M2, E4M6, E4M8) ...   That's gotta be some Mandela effect shit! DAMN THOSE MADMEN AT CERN!

That's one way to look at it, and that is why I said SilverMiner and thundercunt were incorrect.
But there does exist a context in which it is correct. I'm surprised it's turning to be so difficult.

There are many mistakes in the map progression.
MAP31 is accessible from MAP18. MAP33 is unreachable via any map, as it is the title map. MAP38, 34 35 are not accessible via the main campaign's maps.
The only correct vertical link is the one between MAP01 and 32.

No, not the 2020 release, but you are thinking in the correct direction.
It's been long enough - everyone can re-answer, including joe-ilya.

Thanks for the demo!
I spent some time working on the combat. The extra arch-viles I think added a nice 'surprise' to the encounters.
Put some barrels around the lower-tier enemies at the start but the difficulty kinda spikes after the blue pipe. I added in some Hell knights and more spiders too.
Other changes:
-Changed the megasphere to green armor.
-Smelly signs and armor bonuses near drop
-Added support tex to fix misalignment.

Down With Brown V2

DOWNLOAD PDF: Google Drive


▌ DESCRIPTION

I made myself a cheat sheet to speed up writing MIDI that sounds roughly the same across different soundfonts. I figured it might come in handy for someone else, so I decided to share it.

I work in Ableton, so I put together two versions for convenience.


- Attached a PDF so you can print it out and have everything right in front of you while working.
- If there's any bullshit in there, please correct me — I used AI to help lay it all out.


▌ WHAT'S INSIDE


- Colors show which instruments sound more or less the same across different soundfonts.

- Below each instrument you'll find the MIDI controllers that work best with that particular instrument.

- The recommended velocity range is indicated, as well as the note register where the instruments will sound decent.

- If some instrument is fucking with your head, try swapping it for a similar one with better compatibility.

It's rumored that compifont should exist as 2019 updated version

Stats is interesting

Level progression of the 2020 release?

www.doomworld.com/forum/topic/159435-oldakounts-story-is-strange/

A failed attenpt to a spooky ARG and...

www.doomworld.com/forum/topic/159389-iwad-texture-stats-and-other-silly-metrics-doomwad-doom2wad/

A really interesting thread about textures usage in OG Doom and Doom 2.

Just finished this. It was great! Nice and easy difficulty, great progression, fair ammo availability. Very nostalgic and enjoyable. Captures the "spirit" of E3 nicely, I thought.

I have uvmaxed and enjoyed the whole series.

same

Yeah, I think it would have to start out as a custom source port, I feel. You could post-process demos but that's tricky and requires, well, demos. User freedom to play how they want is probably a big part of the fun. One might argue a source port restriction is even more restrictive but if the scoring spec is explicit it could be applied to many ports over time.

I did see there is a port of Doom to webasm which opens the possibility to playing in a browser window. Such solutions have the potential to solve many of the issues around scoring, number of attempts, etc. But it is also a lot of work of course.

Better would probably to get it off the ground first and then figure out how to improve it over time.