Two or more people cannot proceed to E4M2b in co-op
Issue #132
resolved
In E4M2a, two exit triggers to E4M2b (the underwater one and the one past the Attack powerup near the start) are too small for two or more players to fit in. This makes it impossible for a co-op team to get past E4M2 without noclipping because co-op requries all players to be at the exit, but there's no way to get two or more players on the exit triggers. Going thorugh E4M2b is also required to proceed, so the team is stuck unless they noclip to the exit that leads to E4M3a.
The exit at the top of the map near the harbor (the one that has an elevator connecting to it and has a cave in it) works for two or more players, but it isn't a solution because the player has to go through E4M2b in order to get to that part of E4M2a in the first place.
This isn't a problem in SP, as the game will let the player proceed to E4M2b without Superfly and Mikiko via both exits.
Comments (6)
-
-
That sounds good. We ran into this issue during coop and there really wasn't any obvious way to continue the game after that other than noclip to get the door open.
-
reporter
Wouldn't it be easier to move the exit trigger for the water entrance to E4M2b so that the team can gather the large area right before the normal exit? Moving that trigger shouldn't be too hard compared to merging E4M2a and E4M2b.
The Attack Powerup entrance might be a bit tricky, but it might be possible to do the same there.
-
- changed status to closed
Merged e4m2a and e4m2b made by Knightmare and was tested in SP and coop. Works properly. Will be available in the next public build.
-
- changed status to resolved
I've already got the map merge completed, and testing hasn't turned up any bugs. It will be in the next update of the maps pak.
-
the fix is now available on the Downloads page
- Log in to comment
I don't want to mess with the geometry around those areas, so I'll try merging these two maps together. As they were originally a single map in the 1998 E3 demo, there shouldn't be any problems with running into the BSP format limits. E4M2b also lacks complex linked entities with generated targetnames, so there shouldn't be any bugginess caused by merging.