SMG_Man

I'm sorry, but I'm going to drop out from this project. I've had a lot of neat ideas for building a Boom map, but work's been rather stressful lately and I just have not had the time to actually put any of them together into a coherent map. Sorry for the inconvenience, and best of luck.

The playable areas of most stock Doom II maps fit within a 4,096 x 4,096 bounding box, usually erring smaller than that. Map20 (Gotcha!) is a bit larger, at about 6,144 x 5,120, and Map24 (The Chasm) at about 5,120 x 5,120. The maximum size supported by the original engine would technically be within a 32,768 x 32,768 square, and Gez pointed out in 2012 that the safest range for vanilla maps would be in a roughly 18,800 x 18,800 square so as to avoid overflows. However, issues can still arise depending on the complexity of your map (visplane overflows, drawsegs overflows, blockmap limits, etc.) so you may end up with a smaller playable area than even that. Ultimately, the feeling of "how large" a map is also depends on what you do with the map space, and how taxing you make remembering locations/getting around on the player. I hope this all helps. Bonus: TNT's Map20 (Central Processing) fits in a 14,336 x 9,216 box, Map21 (Administration Center) fits in a 16,384 x 8,192 box, Map22 (Habitat) fits in a 10,240 x 6,144 box, and Map27 (Mount Pain) fits in a 15,360 x 11,264 box

You can have the script clear the action of the other line trigger, or simply remove the other line's trigger condition(s) so that the script doesn't run again. Alternatively, both lines can run the exact same script with the exact same arguments, but have the script terminate if it checks and sees that it's already been run before. There are multiple ways you can go about it. Personally, I would go about it by using SetLineActivation at the start of the script to disable the other line's trigger condition(s), and you could define arguments for the script so that you don't need to have two separate scripts ultimately doing the same thing.

I guess technically the Master Levels and a smattering of the Maximum levels were my first exposure to custom WADs. Besides that though, the list of PWADs I've played is very short - Eviltech, Plutonia 2, Knee Deep in ZDoom, Mock 2, and a small bit of Psychophobia were pretty much all I'd touched before I joined Doomworld, and honestly since then the list hasn't really grown.

I distinctly remember having trouble with this, but in trying again you're 100% correct and it's working perfectly. What the fuck was I doing in the past???

if the issue is that cacodemons are bunching up UNDERNEATH a platform, then simply using a "Cacodemon-only" teleport line will have the unintended effect of teleporting them even if they're ABOVE the platform. My suggestion, if it's feasible - have your script check the actor's Z-value when determining whether to trigger the teleport or not. For example, I made a script to keep track of where the player was in a map and have it displayed in the automap (like how Doom 3 keeps track of where you are in a level). The problem I was running into was in a level with multi-story buildings built with 3D floors; the regular line trigger would activate regardless of which floor the player was on, and I couldn't substitute in "actor touches floor" thing triggers since those don't work with 3D floors. My solution was to implement a check via "GetActorZ" to look at the player's height when crossing the line - if their height was above the 3D floor's floor height, then it would give their location as the upper room, and if not, then it would give it as the lower room. I hope this helps!

@Doomy__Doom hope I'm not bugging you in asking this, but do you have a visual theme in mind for your map (32)? Based on the texture pack we have and the project specifications, it would be pretty easy to do either an Egypt or snow-themed map for the secret level slots without importing more resources, so I figured I might do one of those for mine (31).

Your best bet would be either 1. Use Portals instead of 3D Floors to make the structure 2. Use specially-constructed Polyobjects that have limited height Both approaches have their merits and are definitely possible, but I can't really remember the method for no. 2 off the top of my head. Conventional Doom-style raising doors just don't work well with 3D floors unfortunately, so you'll probably have to learn something new to get this going.

When playing the original games, I can pretty much go level to level with a single save at a time. Playing my own maps, I'll usually save wherever I know a hard part is. Playing someone else's maps, I'll rotate three or more save slots to help offset going in blind.

This is prob the largest dimension of it that I can think of. Things like arbitrarily reducing the damage the player deals or increasing the damage that enemies deal are easy examples across all genres of games.

Gonna be honest, this is exactly how I playtest my own maps lol.

This sounds like an older version of the game. There are minor differences in some levels between v1.666 (first commercial release of Doom 2) and v1.9 (the last official release).

I played your map on HMP via GZDoom (no freelook/jump/crouch). It's definitely on the harder side in my appraisal (though for full disclosure, I don't generally play custom levels, so I have no idea what the difficulty landscape is like beyond "harder than Doom 1/Doom 2"). Your architecture and atmosphere are pretty solid, and I dig the choice of midi. A few concrete thoughts: Nice map!

I'll have some time to get started on my map here in the next week or so. Before I get started putting pen to paper though, I have a question - In the main post you said re: the secret level slots "The only guideline here is to not make a map that you would see ending up in any of the six episodes listed." Is this only in terms of the aesthetic, or would this include gameplay design as well?

Here are some thoughts I've had about weapons in the past Fist - After re-playing some Metroid games, the idea of adding more "permanent" upgrades to Doom wouldn't leave me alone, and I figured a sort of cumulative Berserk effect could be interesting. Each berserk pack picked up throughout an episode would slightly increase the damage the fist deals, and once a certain threshold is crossed the fist's DPS would solidly outpace the Chainsaw's (though the Chainsaw could still have some utility in stunlocking certain enemies for example). I don't like the idea of taking the Chainsaw away from the player, since it offers an interesting dimension for a melee weapon that an axe/wrench/etc. kind of "slower but stronger" melee weapon doesn't. Pistol - doubling the damage and increasing its accuracy is probably fine enough, though I did try going further in a mod I was working on and made it where firing the pistol click-by-click gave it a much higher rate of fire than simply holding down the mouse button. Don't really have enough data/feedback whether this was a good change or not, but it's an idea. Shotgun - This one's difficult to me. The idea I've settled on liking the most is rather boring: simply increase the base shotgun's pellet count from 7 to 9, narrowing the ammo efficiency gap a bit, and maybe make it slightly more accurate/the SSG slightly less accurate. Chaingun and Machinegun split - I like how Quake II's chaingun functions: a slight windup, then just fucking BULLETS raining everywhere chewing through your ammo like no tomorrow. Then have the Machinegun function as Doom's original Chaingun does, with maybe a 5 tic delay between shots instead of 4 tics. Plasma Gun - I actually never really thought about this one too much until I saw a recent thread regarding the disparity in damage-to-ammo the Plasma Gun faces compared to the BFG, and I still don't have a good answer. Again, the boring option screams at me - maybe add in another cell-using weapon to complement the Plasma Gun (a Rail gun, or a pseudo flamethrower, or something) and have the BFG9000 use a new type of ammunition and then add in the Unmaker and Quake III Arena BFG10K and have them share that ammo type.