Instead of giving us different dice and character sheet backdrops, you worked on the Encounter feature. You know, the one that’s been in alpha/beta for years now?
It should be noted that D&D Beyond is divided into different teams that deal with different things. The team that does content entry for example is an entirely different team from the one working on the encounter builder to the one working on the character sheet.
Dice and backdrops are handled by a team separate from the encounter builder, meaning that the bandwidth dedicated to those features does not pull any bandwidth from other parts of the sites development. However, due to how varied software development skills can be, from graphics to 3d modelling, to site coding, to backend coding, those people on the team that does dice and backdrops can't just be moved over to the team working on the encounter builder. Also there's the principle of diminishing returns on team size, you know the expression about how you can't make a baby in a month with nine women?
The encounter tool represents a lot of cool and complex features, hence why it's been in development for as long as it has. But this means there's still gonna be cool stuff still to come
There are different teams but I understand the frustration. I've wanted the ability to drag and drop creatures into an encounter since alpha. Most encounters will remain awkward to run until then.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Instead of giving us different dice and character sheet backdrops, you worked on the Encounter feature. You know, the one that’s been in alpha/beta for years now?
Just an idea.
It should be noted that D&D Beyond is divided into different teams that deal with different things. The team that does content entry for example is an entirely different team from the one working on the encounter builder to the one working on the character sheet.
Dice and backdrops are handled by a team separate from the encounter builder, meaning that the bandwidth dedicated to those features does not pull any bandwidth from other parts of the sites development. However, due to how varied software development skills can be, from graphics to 3d modelling, to site coding, to backend coding, those people on the team that does dice and backdrops can't just be moved over to the team working on the encounter builder. Also there's the principle of diminishing returns on team size, you know the expression about how you can't make a baby in a month with nine women?
The encounter tool represents a lot of cool and complex features, hence why it's been in development for as long as it has. But this means there's still gonna be cool stuff still to come
Find my D&D Beyond articles here
There are different teams but I understand the frustration. I've wanted the ability to drag and drop creatures into an encounter since alpha. Most encounters will remain awkward to run until then.