KNOWN ISSUE: Bots staying after a player joins, causing matches to have more than 4 'players'

Issue Description:
3 players plus 2 AI players in one mission instance.

Steps to Reproduce:
Unknown steps to reproduce, additional detail:

  • one player did not show in the UI element on the left of the screen, but was otherwise fully interacting with the environment and enemies (Ogryn player)
  • Player that did not show on (my) ui seemed to be the mission’s original player
  • When new player (me, second player, veteran) joined, instance failed to kick a bot, spawned joining player at start spawn.
  • Mission was on malice difficulty
  • Mission had recently started as player/bots were located on the bridge section
  • Mission seemed to attempt to adjust difficulty, with more hordes, swarms, elites than normal, as well as a Demonhost and Beast Of Nurgle (Beast Of Nurgle wiped the party, partly due to lack of ammo, partly due to the intense continuing pressure).

Mission Name (If Applicable):
I think it was Vigil Station Oblivium

Platform:
Gamepass

Player ID:
Crunchi / Crunchi#1410 / Callista

Approx. Time of Issue & Timezone:
[12/17/2022, 01:00PM] [GMT+4] Aprox.

Reproduction Rate:
Once

Upload Supporting Evidence:


Image was taken upon initial joining. Later another player joined.
I also have a minute of footage of when the party wiped but its too large to upload here.

Upload Console Log:
Unable to as it says “contains system files”
Also my directory looks different from listed

Upload darktide_launcher.log:
My directory looks different from listed so unsure how to proceed.

PLEASE POST CRASHES AND ERRORS IN THE ‘TECHNICAL SUPPORT’ CATEGORY INSTEAD

We kindly ask that you complete the questions below. With this information, we can add it to our database for investigation.


Issue Description:

Steps to Reproduce:

  1. Joined a match with two players already in it.
  2. Realized there 5 rejects. Two of them were bots.
  3. Match was easier than usual. lol

Mission Name (If Applicable):

Platform:
Microsoft Store

Player ID:
Queasy1

Approx. Time of Issue & Timezone:
12/20/2022, 08:20PM ET

Reproduction Rate:
Once - Rare (<10%) - Unusual (<25%) - Common (<50%) - Often (<75%) - Constant (100%)

Upload Supporting Evidence:

Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]

N/A

Mission Name (If Applicable):
Any/Random

Platform:
Steam

Player ID: acquireTigris

Approx. Time of Issue & Timezone:
00:47 24/12/2022 +8

Reproduction Rate:
Unusual

Upload Supporting Evidence:
Attached

console-2022-11-18-03.07.44-2f7ef76c-c8a0-4fc6-90d3-2d35f2f9c7ab.log (632.7 KB)
darktide_launcher.log (248.0 KB)

3 players, 2 bots.
joined quickplay, there were 2 players + me and 2 bots.
Then another player joined replacing 1 bot, so we were 4 players and 1 bot.
Then 1 player left - 3 players and 1 bot, and reconnected replacing remaining bot, so at end we were 4 players 0 bots.

(Before that tried to begin mission and got server error like 1001 or something like that)

log (last mission)
console-2022-12-23-19.41.32-bec96bb7-21d5-46fc-b5cb-340bc832c147.log (299.8 KB)

I joined a game and got in mid-match to notice that something was off. We were playing 4 players plus a bot, see video clip:

1 Like

Issue Description:
I recently completed a mission but somehow the first slot was not overtaken by a player this is the first i seen it happen

Steps to Reproduce:

  1. manually select a mission for public
  2. ready up in a lobby by yourself
  3. someone joins but don’t take up a bot slot
  4. two other people joins and takes up two bot slots and ended up with 4 players and one bot

Platform:
[Steam]

Player ID:
Jonathanlh

Approx. Time of Issue & Timezone:
[12/31/2022, 05:25PM] [GMT]

Reproduction Rate:
Once - Rare (<10%) -

Upload Supporting Evidence:

Issue Description:
Not sure if this bug fixed or not. Patch 1.0.23 has it. After new player joined the bot was not disconnected.

Steps to Reproduce:
No specific steps

Platform:
Steam

Player ID:
(Steam Community :: minotaur)

Approx. Time of Issue & Timezone:
01/29/23 12:00 UTC +3

Reproduction Rate:
Once

Upload Supporting Evidence:

Upload Console Log:
console-2023-01-29-07.59.31-34336472-eb93-482c-851d-9133af8fab5e.log (539.8 KB)

Upload darktide_launcher.log:
darktide_launcher.log (184.8 KB)