Throwing more devs on multiplayer would definitely solve those problems.
-
If you are reporting a bug, please head over to our Technical Support section for Bannerlord.
Hear the Casul Roar: We are sad!
- Thread starter Moth_Queen
- Start date
-
- Tags
- #balance #casuals #playerbase
Users who are viewing this thread
Zoonanay
Knight
I agree you should've had a better explanation by now, Armagan has said they're on the way recently but you should be told what's causing the delay so it's not some abstract problem.
Mexxico, NIN3 and other devs have made great contributions as well, but I don't see what else in OPs post AVRC could specifically respond to? He hasn't got the authority to say TW's now going to focus on large-scale battles instead of Skirmish. Nor can he individually solve the lack of player count. The only other thing I see is captain balancing, which he has talked about in other threads.
Just recently he posted about trying to get competitive data of matches without class restrictions to help balance Skirmish, I'm fairly sure that's also being done in his free time. It seems pretty uncalled for to personally assail him, but to each their own I guess.
This is why a Community Liaison is sorely needed, it's someone who can be expected to get these answers, instead we expect more from people whose primary job isn't even to communicate with the community.
You'd be surprised.
The more staff, the more co-ordination is required, the more infrastructure within the company needs to be made. Not to mention you've got to assign someone to teach the new guys internal tools etc. It can often end up slowing projects down even more.
Especially considering Ankara is hardly a Tech Capital and Turkey isn't exactly in abundance of experienced programmers.
Ah yes, more devs means development will slow down on an already barely staffed section of the game. A common thing in the industry.
Zoonanay
Knight
Unfortunately, someone would have to mentor them, and that'd be existing MP staff as they're most familiar with the work they'll be doing.
Plus with that long refactor earlier, it suggests it wasn't designed for easy alteration or patching once legacy code. Other things like not enforcing a standard style or format can make working on other people's previous work a pain in the ass, especially if you're unfamiliar with the code in general.
You make it sound like most developers in their studio are not familiar with the codebase they wrote, unless you implying they get changed a lot.
Aside from that, we don't know. And like any normal development studio which we should consider TW to be, the more people, the more **** gets done.
But, back on topic, all MP needs is proper spawns on TDM or have single life battles. In skirmish or captain mode one incompetent player can very much affect the battle outcome, and in TDM casuals don't live long enough to figure out the game.
And nobody likes siege.
Give the casuls a safe place to spawn, and let them join a large mass where individual dueling aren't as important.
How hard is it to set team spawn points? And if some maps give a slight advantage to one side, who cares? It's TDM! And its better to lose that way rather than getting couched in the back or spawning into the middle of 5 enemies.
And nobody likes siege.
Give the casuls a safe place to spawn, and let them join a large mass where individual dueling aren't as important.
How hard is it to set team spawn points? And if some maps give a slight advantage to one side, who cares? It's TDM! And its better to lose that way rather than getting couched in the back or spawning into the middle of 5 enemies.
Zoonanay
Knight
More that new employee's may not be familiar with the code base, so often work on older code to familiarize. Scripts worked on by a single individual may be rather untidy/stringent, especially if it wasn't regularly expected to be altered later or worked on by a bigger/newer team. So you might end up re-doing the new employee's work in audit, or worse miss an alteration in audit that causes bigger problems down the line. I've known limited pool of hireable employee's and low employee count to lead to these issues.
But regardless, community staff aren't potentially effected by this, that was the original point. Hiring more dedicated community staff seems a no-brainer to improve community feedback, and can directly ask the people who can answer the questions we've all been asking.
I hink it doesn't even need team spawns. Just check which players are near which spawnpoint and make sure people don't spawn to close to their enemies. I think that was how it worked in Warband and I never had trouble with spawning surrounded by enemies.
Ice cold take. Siege was the most popular gamemode in Warband and was the most popular in Bannerlord when multiplayer actually had players. It was so unstable at launch that many people were driven away, and now the community isnt even big enough to fill a single server, so even though siege is now stable, the few players left just stay on TDM like a group of hobos huddled around a trashcan bonfire.
Last edited:
Have people spawn like in the BGs in World of Warcraft. Every 30 secs everybody that is dead respawn all together in a random spot. Instead of having your personal Rez timer, the rez timer is shared for all. Sometimes you die and wait 25 secs, sometimes you die you wait 2 secs depending on how much time left was on the global rez.
Having people spawn left and right at different times and places, no matter how good the spawn, will keep the same issues in TDM.
Siege was and is popular in Warband, but I think it was only popular in Bannerlord because it was the only choice for large battles. We all flocked to it (thinking it would be similar to Warband), but the frustration of having cav running everywhere and the confusion over flags being lost or attacked just made it feel like a chaotic TDM. Myself and my friends could deal with the crashes (we expect that in early release), we just didn't like the part in between the crashes.
The flags seemed like a good idea, but unfortunately it didn't work out.
In 1.5.8 they want to reduce the defender morale loss depending on the number of flags they still hold. Could do a little bit against backcapping but I think it needs at least some testing whether it works.
I think the most important flaw of the flags is that they ofen move the focus away from natural defense/attack points. It forces people to stand around like sitting ducks while it would actually be more sensible to push beyond any given flag to the next bottleneck.
I think the most important flaw of the flags is that they ofen move the focus away from natural defense/attack points. It forces people to stand around like sitting ducks while it would actually be more sensible to push beyond any given flag to the next bottleneck.
