TheBreadMan
New Member
- Joined
- Jun 20, 2024
- Messages
- 2
EDIT: An attached video isn't showing up. Uploaded it unlisted on YouTube so you could watch that way. Link here.
This ended up being a lot longer than intended as I needed to report more strange behaviors.
Out of the 4 TD servers hosted by blw.tf, one of them is not working as intended at all. This is the LA server, and this problem applies to all 4 of the TD maps (td_firstone, td_rampant, td_swampy, and td_cavern). Whenever I load into the server, it always brings me to td_firstone (which by itself isn't really an issue) so that's why I recorded the initial video on this map. This was recorded on the 19th of June, 3 days ago, but has apparently been going on before then. Someone within the blw.tf Discord server said this issue has been reported already, and even fixed at some point, but given this recording, it's seemingly a repeating bug. I was told to post my video here so it could be forwarded to devs.
To start, all of the buttons (with the exception of the two server start buttons that you see when you spawn into a map) are non-functional, including the button that starts the actual waves. You are also able to switch both class and team, as well as use any weapons, when you're supposed to be restricted to only playing Engineer on BLU with his stock weapons. When joining the server, you spawn in with a bot on your team that does nothing but stands in one place (and is given one of the many default bot names in TF2's training mode). In the video, there are two bots that spawn on RED, and one that spawns on BLU. Bots that spawn on RED seem to follow your movements (you can see in the video that they tilt a bit as I move), but do nothing else. You are able to damage the bots inside the cubby if there's space for projectiles to go through (only possible on td_firstone) or if you're playing Pyro and do the "aiming at the bottom of the door and forcing flame particles to pass through a nearly invisible crack" thing (also only possible on td_firstone), but that requires the RED bots are close enough for the flames to hit. If you try and change to RED Team, you will spawn into the small cubby where the bots are meant to come from, but you can't move much and can't exit unless you switch back to BLU.
I initially would've ended things here. However, as I was typing this, I checked the server again to double-check some things, and I happened to spawn in with 3 bots on BLU and 4 on RED (happened on td_firstone, and continued into the rest of the maps when I used !rtv, however I stayed on td_swampy for a while to inspect the following behavior). The BLU bots don't do anything different than previously stated/shown in the video, but in this scenario, the bots on RED do interact with one another. Shown in one of the attached screenshots, a RED Medic bot is overhealing a RED Soldier bot. Changing to RED, the Medic ignores you and won't heal you, even if you're in the Soldier's way. The Medic bot seems to change direction to face the player, much like other bots, but will never interact. BLU and RED Medic bots sometimes heal and sometimes don't. On td_swampy, both RED and BLU ignored me.
I eventually used !rtv again to switch to td_rampant. 3 bots spawned on BLU once more, and 4 on RED. This time, the BLU Medic bot would heal me, as well as the other two BLU bots periodically (in all of my investigation, I never saw Uber being activated). Using !rtv again in order to go to the last of the 4 maps, td_cavern, the BLU Medic bot repeated the same behavior of healing each BLU member (including the player) for about 1 second at a time. Switching to RED, I managed to get their Medic bot to heal me, but only when I was standing directly in front of it. The RED bot's cubby on td_cavern, for some reason, doesn't restrict your movement much with any invisible walls like td_firstone and td_rampant do (td_swampy is sorta a mix; it has an invisible wall, but it only restricts you to roughly the back half of the given area). You still can't exit without changing teams, but you can walk around a lot more freely.
Another human player ended up joining when I made a return to td_firstone, but it didn't seem to change anything other than removing one of BLU's bots (RED's stayed).
I was going to record another video to display the things I didn't record the first time, but the server suddenly blocked me due to the VAC system. Unsure why; is it because I opened OBS suddenly? I didn't do anything other than that. It's fixed now but this post is long enough as is. If anyone wants more recordings though, I'm up for it.
Other quick finishing notes:
- You are still able to build and upgrade sentries, dispensers, and teleporters normally (though you shouldn't be able to build dispensers unless you buy certain upgrades)
- All buildings still function (however the sentry is an assumption; there's no way for it to reach the opposing team from what I know, but given that the others work, I don't see why the sentry wouldn't)
- Text commands still worked
- You probably noticed, but all bots use the normal human merc models when you're supposed to be defending against RED MvM bots
Hopefully there's nothing I missed. Apologies for this being so long, there's just a lot to say about how this server is bugging out, and I didn't want to be vague by just saying "it's broken" and nothing else. Hope a dev can figure out what's happening!
This ended up being a lot longer than intended as I needed to report more strange behaviors.
Out of the 4 TD servers hosted by blw.tf, one of them is not working as intended at all. This is the LA server, and this problem applies to all 4 of the TD maps (td_firstone, td_rampant, td_swampy, and td_cavern). Whenever I load into the server, it always brings me to td_firstone (which by itself isn't really an issue) so that's why I recorded the initial video on this map. This was recorded on the 19th of June, 3 days ago, but has apparently been going on before then. Someone within the blw.tf Discord server said this issue has been reported already, and even fixed at some point, but given this recording, it's seemingly a repeating bug. I was told to post my video here so it could be forwarded to devs.
To start, all of the buttons (with the exception of the two server start buttons that you see when you spawn into a map) are non-functional, including the button that starts the actual waves. You are also able to switch both class and team, as well as use any weapons, when you're supposed to be restricted to only playing Engineer on BLU with his stock weapons. When joining the server, you spawn in with a bot on your team that does nothing but stands in one place (and is given one of the many default bot names in TF2's training mode). In the video, there are two bots that spawn on RED, and one that spawns on BLU. Bots that spawn on RED seem to follow your movements (you can see in the video that they tilt a bit as I move), but do nothing else. You are able to damage the bots inside the cubby if there's space for projectiles to go through (only possible on td_firstone) or if you're playing Pyro and do the "aiming at the bottom of the door and forcing flame particles to pass through a nearly invisible crack" thing (also only possible on td_firstone), but that requires the RED bots are close enough for the flames to hit. If you try and change to RED Team, you will spawn into the small cubby where the bots are meant to come from, but you can't move much and can't exit unless you switch back to BLU.
I initially would've ended things here. However, as I was typing this, I checked the server again to double-check some things, and I happened to spawn in with 3 bots on BLU and 4 on RED (happened on td_firstone, and continued into the rest of the maps when I used !rtv, however I stayed on td_swampy for a while to inspect the following behavior). The BLU bots don't do anything different than previously stated/shown in the video, but in this scenario, the bots on RED do interact with one another. Shown in one of the attached screenshots, a RED Medic bot is overhealing a RED Soldier bot. Changing to RED, the Medic ignores you and won't heal you, even if you're in the Soldier's way. The Medic bot seems to change direction to face the player, much like other bots, but will never interact. BLU and RED Medic bots sometimes heal and sometimes don't. On td_swampy, both RED and BLU ignored me.
I eventually used !rtv again to switch to td_rampant. 3 bots spawned on BLU once more, and 4 on RED. This time, the BLU Medic bot would heal me, as well as the other two BLU bots periodically (in all of my investigation, I never saw Uber being activated). Using !rtv again in order to go to the last of the 4 maps, td_cavern, the BLU Medic bot repeated the same behavior of healing each BLU member (including the player) for about 1 second at a time. Switching to RED, I managed to get their Medic bot to heal me, but only when I was standing directly in front of it. The RED bot's cubby on td_cavern, for some reason, doesn't restrict your movement much with any invisible walls like td_firstone and td_rampant do (td_swampy is sorta a mix; it has an invisible wall, but it only restricts you to roughly the back half of the given area). You still can't exit without changing teams, but you can walk around a lot more freely.
Another human player ended up joining when I made a return to td_firstone, but it didn't seem to change anything other than removing one of BLU's bots (RED's stayed).
I was going to record another video to display the things I didn't record the first time, but the server suddenly blocked me due to the VAC system. Unsure why; is it because I opened OBS suddenly? I didn't do anything other than that. It's fixed now but this post is long enough as is. If anyone wants more recordings though, I'm up for it.
Other quick finishing notes:
- You are still able to build and upgrade sentries, dispensers, and teleporters normally (though you shouldn't be able to build dispensers unless you buy certain upgrades)
- All buildings still function (however the sentry is an assumption; there's no way for it to reach the opposing team from what I know, but given that the others work, I don't see why the sentry wouldn't)
- Text commands still worked
- You probably noticed, but all bots use the normal human merc models when you're supposed to be defending against RED MvM bots
Hopefully there's nothing I missed. Apologies for this being so long, there's just a lot to say about how this server is bugging out, and I didn't want to be vague by just saying "it's broken" and nothing else. Hope a dev can figure out what's happening!
Last edited:
