This is the second time this has happened to me. Baal simply does not cast the minion waves as he normally does. I can open portals and come back or even go elsewhere to kill monsters and come back. The game doesn't freeze, Baal casts decrepify and the light is whirling around him. After that it took what seemed to be another 5 minutes before the second wave spawned. I double and triple checked to make sure that there were no other monsters anywhere in the level and after being decreped by Baal multiple times I finally got the first wave to spawn after what seemed like 5 minutes. Last night I decided to do a Baal run on P/8 with my zealot and everything went fine till it was time for the minion waves and they didn't come. Please confirm if 60 fps mouse fix is allowed or not.Īlso I suggest updating the rules as they currently claim that Singling is allowed under rule section 2.1, but later in the Community and Links thread it links one approved version which doesn't have the 60 fps fix, so it's a bit confusing.

Impossible to know because their videos are never recorded in 60fps: Gripphon, Pb_Pal, Babyhell, D30D043, Pax1990 I've done it by pausing their YouTube videos and viewed them frame-by-frame to inspect the movement behavior of their mouse cursor.ĭefinite 25fps mouse: ffs, maxicek, Bewitch EDIT: I've scienced a little bit and found that not everyone run the game with default 25fps mouse. The approved Singling mod doesn't fix this issue. When you play through TCP/IP Host or your mouse moves freely at 60fps, but in Single Player it's locked to 25fps, feels very choppy. The /fps command shows you your FPS, it doesn't unlock the mouse FPS from 25 to 60. However inside the zip of the Ladder Runeword mod I found a different. I got the Runewords working finally! The forum link has a PDF that was confusing, expecting you to have another RedRuneMod that I wasn't interested in.

Diablo 2 no cd mod