Page 1 of 1

SNS (Rebranded) #1: Death & Decay with Mayhem 2016

Posted: Sat Jun 03, 2017 10:56 pm
by ARGENTVM
So after lots of bitching (mainly from the same three people), I decided to reformat how the threads for SNS are. Hopefully, no more cop-out threads will be made as actual events take place.
With that out of the way, tonight's session will feature Ivan's Death & Decay on the recently released (after around a year of development hell) Mayhem 1600.
Image WADs: Death & Decay Version 2.3c, Death & Decay Monsters Version 0.7b, Death & Decay Ammo Spawner Version 2.4, Mayhem 1600

When: June 3rd, 2017 - 00:00 UTC
Pacific Time: 17:00 (5 PM)
Mountain Time: 18:00 (6 PM)
Central Time (US): 19:00 (7 PM)
Eastern Time: 20:00 (8 PM)

Where: TSPG-Painkiller
Spoiler: Customized Settings (Open)
Player/Client limit: 32/64
Maplist: MAP01-MAP20, MAP31
Skill = 3

Re: SNS (Rebranded) #1: Death & Decay with Mayhem 2016

Posted: Sat Jun 03, 2017 11:06 pm
by doomjoshuaboy
good choice making bob proud.

Re: SNS (Rebranded) #1: Death & Decay with Mayhem 2016

Posted: Sun Jun 04, 2017 2:31 am
by Combinebobnt
good sns only crashed within the first 5 seconds farthest i ever got in dnd

Re: SNS (Rebranded) #1: Death & Decay with Mayhem 2016

Posted: Sun Jun 04, 2017 3:06 am
by Ivan
Combinebobnt wrote:good sns only crashed within the first 5 seconds farthest i ever got in dnd
You tried but only got so far... Dark Cardinal ruined your day :) (Hi to asshole mapper)

Re: SNS (Rebranded) #1: Death & Decay with Mayhem 2016

Posted: Sun Jun 04, 2017 4:22 am
by Combinebobnt
crashed again on map13 corrupt zlib stream great modding ivan

map13 was ass tho wtf is that map rofl good one alter rip sns there

Re: SNS (Rebranded) #1: Death & Decay with Mayhem 2016

Posted: Sun Jun 04, 2017 8:21 am
by Ivan
Combinebobnt wrote:crashed again on map13 corrupt zlib stream great modding ivan

map13 was ass tho wtf is that map rofl good one alter rip sns there
Only for you or others?

It'd also really help if there was some sort of a stackdump or some other kind of report as to what caused this crash. It's just putting "Corrupt ZLib Stream" and that's it. You don't know what data access caused it and it's really difficult to trace.