Good work as usual Siv

Bless you for timestamping all of these so I can zip around the ones I wanna see.

Great work frendo

Thank you for making this! It's great when you put in timestamps so I can go right into my favorite moments of the LP.

Insane amount of work, thank you friend

Obnoxious indeed. Let's put that one back on the shelf and behind a glass case for emergencys

@@jonaswest6993 probably gonna come out on Christmas

@@slyfox1223 Does Reggie has some alternate family name we don't know about? Reggington?

wish granted

@@fearlesstp Yoooooooooooooooooooooo Also this is how I found about this, I better keep comment spamming the next VoDs to stay updated for DS2.

You Did It

perfect

Drop your tears for the legend. Never forgotten

Woolie squats next to the woolie hole and tells you there's a treasure inside.

I knew it from "press that any button".

Thanks! I try to put some narrative stuff in there(not all, though). It makes the videos a bit long, but caters to the viewers who treat it as a shorter version of the LP.

Dang idk Even I dont want to subject Reggie to the special kind of torture that is ds2 hitboxes and fall damage

I don't know if I can handle another snailborne.

Dark Souls 2 in general is a special kind of bullshit that leaves even veterans in tears when returning.

That will be a LONG time away. Prob dark souls trilogy first

We did get a "Drop your firebombs" which cracked me up.

You know what I mean?

Nah, drop your shield.

Did your buddy turn into an item yet?

Me, too!

Reggie already know the difference between left and right

@@silentassason and he seems capable of reading

Talking mad shit for someone in invader range.

Do explain, please?

@@tylerdenham3880 basically if you left your console on or left the game running for a really long time it would mess with the boss AIs and cause them to not use their full moveset and act a lot more predictably

@@dumbsterdives Oh wow, that's really strange. I wonder what exactly is the cause of that and how someone discovered such.

@@tylerdenham3880 Late answer but generally memory leak bugs are caused by memory being reserved by the program for certain data and then failing to un-reserve or release it. It marks that data space so that the program knows not to try and put any data there because it needs the stuff that's there. Then when it's done the program releases the marker on those memory addresses so it can be used for new data. When the program fails to release all memory addresses it reserved you get memory leaks, less and less of your RAM is now usable. The longer the program runs and the more this happens the more you end up with big chunks of RAM addresses being unusable because they're considered 'reserved' for data that the program doesn't actually need anymore. With bloodborne the prevailing theory was that lots of different things were causing memory leaks. Fast travelling and loading into different areas, fighting bosses, checking enemies in an area, loading textures, sound effects etc. Especially when you consider that you could cause this to happen by just leaving your character standing in place and doing nothing for a few hours. So it was likely an issue with how memory was being handled by the engine rather than any specific game function causing the issue. For example whenever you fight a boss, memory in RAM is likely reserved so that the data most relevant to the boss is in RAM so you can access it quickly, because reading that data from storage (of any kind) is very slow compared to RAM and you don't need the boss data all the time. Then when you're done fighting the boss the memory is released so RAM can be used for other stuff, but not all of it gets released for (most often) a programmatic/engine error. This process is applied to lots of things in game because of how slow reading from storage is, you load what you need into RAM, use it until you don't need it then release the memory associated with it so you can load something else in. So if you played for a couple of hours you'd start to notice that bosses lose portions of their moveset because space in RAM is reserved and the bosses entire dataset can't be loaded to where the program wants it to be, so it just partially loads it. Leading to the bosses sometimes standing around doing nothing because the thing they would do in that situation just isn't in RAM. As for how people discovered it I think it was specifically loading times? Loading times got worse and worse as the memory leak gets bigger but you can force the memory to be released by closing the game and restarting the console. Enough people were getting sick of long load times between boss attempts and noticed that after doing this that bosses and enemies were suddenly more aggressive and proactive then they were during preious boss attempts. The fact that the entire memory leak issue was fixed in one patch means likely there was an issue with how the engine was loading and releasing things in RAM, if it was unique issues for different assets it would have taken a long time to find every way that memory was being leaked.