Both Shaft Arena and Rocket Arena have 50% lifesteal, if you do 10 damage you receive 5hp, this effect is also present if you are the last person alive on a Wipeout team or if you grab the Siphonator powerup in modes with powerups. It's not present in Aim Arena

When we change a map we are supposed to bump the version of the game and force people to update after they finish their current game, otherwise the game server is going to see a different version of the map as if your version is outdated and you won't be able to start the game.

We updated Skybreak last night (morning?) and the client version failed to be bumped. Raven stayed around removing penalties manually for a while to people affected. (Hopefully your penalty for this would have been removed too, if it wasn't let me know). We'll make changes to the system today so this doesn't happen again.

There is still an edge case that we need to solve at a technical level, and it's to notify server instances running continuous games.

As an aside, most of these map versioning issues will be solved when we introduce the final content delivery system for map delivery that we are gonna use that allows the community to contribute maps, in this system everything will hav...

The version of the race physics which we want isn't working correctly so the Custom Game's more settings doesn't have a physics options dropdown at the moment, when it is working correctly that setting will be added.

Please try verifying the game by going to the Epic Games Library, then click the 3 dots button next to Diabotical and press verify, if that does not work, please try going to your game installation, likely C:\Program Files\Epic Games\Diabotical delete diabotical.exe and diabotical-launcher.exe and verify again. If this continues to fail please try restarting the Epic Games Launcher, if it still fails please try restarting your computer. If it continues to fail delete the C:\ProgramData\EQU8 folder, delete diabotical.exe and diabotical-launcher.exe and verify the game again.

Also how can I display the speed HUD showing me what direction I need to bhop in order to increase speed ? I can't find it :/

That HUD element was called G-Meter, it is not currently available since the HUD system has been changed to be rendered by the engine for the sake of improving performance, this required the HUD elements to be remade and that HUD element hasn't been remade yet. I believe it would be nice to have a tool like that, it has helped players learn how to strafejump and/or strafejump better than before but it is not an easy conversion so I'm not sure if/when the G-Meter or something like it will be available again.

There is a Speed HUD element which displays your current speed value, it can at least tell you if you are gaining some speed and how much, which may help you find out if your current actions are being successful or not when it comes to gaining speed.

From the information that we've gathered I think your issue and pogzis' are different issues. Pogzi's issue should have gotten better in 266, and hopefully be completely gone since 268. We are now focusing on your issue now that the other one is out of the way. Could you tell me if you have an AMD card?

We did some fixes last weekend for surround headsets that made it work for some people. Not sure what could be going on with yours or BBQuake's, could you send me your Log.txt file on Discord to see if it's correctly detecting your device as having 8 channels?

Please restart Diabotical and try the latest version 0.20.267 a tentative fix has been pushed

The format of commands in the Custom Game-More settings-Commands box is phy_double_jump: 1; (instead of /phy_double_jump 1) with each command on a separate line

Brawl 3v3v3 is intentionally starting you with a full loadout and high health and armor, there is a mode called FFA where you start with only the Machinegun, Melee and regular 125hp 0 armor
Some patch notes here: https://www.reddit.com/r/Diabotical/comments/i62h91/the_stress_test_3_is_starting_patch_notes/

We tried to repro this but we are not seeing the same on arena. If this is something that you can reproduce consistently, would you mind DM'ing me in our Discord and I'll send you something to try? UPDATE: Nvm, try 266 and see if that fixes your issue.

It was also mentioned, we aren't exactly sure the competitive playlist & queue rules for open beta.

From testing and feedback we are only sure on the quickplay setup

There are some bugs that we haven't gotten around to which we are aware of:

- Items not spawning on the round/start carrying over with you into the round

- Taking damage from your previous life including dying on respawn after dying if you fall off the map

- Doors not being openable by firing projectiles at them

- Grenades going through doors, going through walls, not bouncing, doing more than 100 damage

- Nvidia Shadowplay not recognizing Diabotical, you can try using desktop capture or adding Diabotical as a game

- Dodge getting stuck on repeat when you press it as you die, if this happens to you, press your Dodge key again

- Firing animation on some weapons remaining active even when not firing

- Respawning in the same location as another player

- Crossbow and Blaster shots going through enemies/bots close range without hitting them

- Chat box being opened when a match starts if it was open when the ...

Diabotical will be available until Monday morning 10 AM CEST <https://www.timeanddate.com/worldclock/fixedtime.html?msg=Diabotical+Stress+Test+3+End&iso=20200810T10&p1=239>

0.20.271

• Stability improvements - please report if you see any part of a map looking unusual relative to how it looked before

0.20.270

• Fixed some issues with the colors of some props and blocks not being correct (some props using "color2" and block materials that had accent colors attached)
• Potential multithreaded input fix

0.20.269

• Fixed the Steal progress bar in MacGuffin not showing up when a player is stealing the MacGuffin from a base
• Fixed the Alignment of the Rank name after finishing the placement matches and being awarded a rank for the first time

0.20.2...

Yes, there's something definitely wrong with multi-threaded input.

During the weekend we did a small survey of pros: 2 of them felt multi-threaded input was clearly better, 2 said it felt a bit better, 1 said it feels different but couldn't tell how, 1 said it felt the same. I think this probably means it's working as expected if conditions are right (all of these people have decent setups).

But there is obviously something about it that creates a requirement gate and in some systems it's causing high latency in the input thread. High latency in the input thread would feel really bad so I understand the feedback. I suspect it's going to be something very trivial causing some timer to accumulate excessively. We never caught this during development because we just needed to have the engine exposed to a larger variety of specs. Now we have to do some A/B testing with systems like this and it should be easy to make it work correctly.

So if you have a really not...

Sorry, we will likely use a better procedure at the end of the next stress test which will allow at least most people that are in a match at the end of the stress test to be able to finish them