Correct.
FWIW, I, like you, also thought autobrake was being removed in 1.33, but apparently not.
Just gotta keep yourself above 27 km/h
Don’t worry, I’ll update that to be 10km/h instead (when you are really stopping). I agree that 27km/h is just a random speed value that doesn’t make much sense.
I thought the old code you found was to be removed in 1.33?
There were 2 pieces of old code:
Lets just put this here:
2020 - Static bots introduced - Peak Zwift - 34,954
2021 - Static bots - Peak Zwift - 49,114
2022 - Mixed Static and dynamic bots - Peak Zwift - 42,199
2023 - Dynamic bots - Peak Zwift - 40,047
correlation is not causation
Just having some fun with silly numbers.
Firstly for an organic group ride, I LOVE the current pacer bots, it feels natural to climb on climbs and ease on the downhills - its good!
But like a few here (it seems) my main type of xl long rides are structured workout rides fed from my Garmin making me stick to say 3.2w for a couple of hours, this is where a ‘no brain needed’ static pacer bot for a bit of company would be amazing, no need to watch the road, we can have a chat, watch a video, fiddle with the phone etc (all the while knowing we will still all be stuck together), and still have a feel of a group ride with loads of riders around you.
At the moment, I just do circles of Tempest
This part I don’t understand you can do this in a free ride as well. Why do you need a big group around you when you don’t even pay attention to the group. Or is it about getting to 100km in 2.5hours as opposed to 3+ hours alone.
Set the trainer in ERG mode pick a route and go.
If you said you want to do steady pace for a few hours in a nice group chatting and interacting then I would say yes you will need a pacer or a steady group ride.
Sorry if what I said wasn’t clear- this is precisely what I would like. My punctuation wasn’t good. I mean 'no need to watch the road but have a chat with other riders, fiddle with the phone etc
That make sense. And I agree I like long rides over the weekend as well and I can’t do it with a current bot when the road are not flat, and I don’t like just riding tempus fugit.
At my weight I have to increase my power going up even with a static bot, with a dynamic bot it is even worse.
But I came to realize that I am in the minority and there is other ways to do steady state rides.
Disclaimer: I don’t have a horse in this race, but here goes…
I am curious as why there can’t be both static and dynamic bots? Why does it have to be either or? Is there some technical or resource driven reason why four static bots couldn’t be added to Watopia for those who want them?
Not everyone wants the same things and unless there’s a clear reason not to add them back along side dynamic ones, it’s hard for me to understand the level of pushback the idea seems to get. Every few weeks someone reopens the call for static bots so It would seem that there is some demand even if it’s not the majority. If it doesn’t create more work or system load, I have trouble understanding why the request for both is a non-starter from Zwift’s perspective.
There are quite a few things that the majority of Zwifters don’t use, but they are still provided; think racing, most hill climbs, long routes, lower end/ higher end pace bots, the toast button, etc. These things, though not popular, serve a need of some of the user base and provide a diversity of experience and utility.
I also am always a bit surprised when people mention ERG as an alternative to having static bots. ERG gives you the freedom not to have to think about your pace, but it doesn’t solve the problem of the tedium and the lack of socialization. It really isn’t an alternative for those people who want to do a longer steady state effort and have some companionship.
Great post Lebasi 
We currently have 16 extra bots taking off every half hour for the the Tour de Zwift makeup week… so clearly it isn’t a resource issue. Either there is a limitation that Zwift didn’t program the bots to be either dynamic or steady and you can only have one option at a time, or James just doesn’t want to.
Mainly down to how much you have to scroll already. It’s not a good experience and I’m not adding more to that without a significant UI update.
So, yes, James doesn’t want to.
I’ll second that, I hate the horizontal scrolling.
I second that. I don’t select anything if I have to scroll horizontally. 
We have a motion on the floor to remove horizontal scrolling, all in favor?
If they add the concept of favorites to everything (workouts, pacer bots, routes, race series etc…) you could have your favorite pacer bots be the ones that show up front and center, and have very little need to continually have to scroll so much.
One idea someone mentioned further up is for bots to only surge for a certain time period going up hills. Which would mean be dynamic as they are now for short punchy climbs and rolling terrain, BUT instead of keeping the increased higher dynamic difficulty perpetually on a long hill they could perhaps slowly drop back to their normal steady state w/kg. So then if the bots do end up on a bigger climb (such as epic KOM or the Alpe), it wouldn’t be 30+ mins of elevated w/kg for folks who happened to just join the pacer at the bottom. I thought it was an interesting idea because it would keep the bots feeling natural on rolling terrain, but allow the w/kg to not get too out of hand for too long essentially dropping people who were expecting a certain w/kg ride. They could keep the same behavior on the way down hills so people don’t get dropped going downhill (which apparently was a problem before), but for longer hills they would only surge for ‘x’ time.
Isn’t the UI suppose to orient your “favourites” to the beginning of the screen i.e., the left side. It doesn’t seem to want to do it for me but I thought it was suppose to.