first and foremost awesome application. but perhaps it's an idea to add an undo button to it. it happens some times that they try to take a long rest and during the last watch something happens and they are in an encounter. the cries off "oh crap I already hit long rest" happen often. though this is the fault off the players because I haven't said they received a long rest. it might be handy to have a reset button to restore the last changes.
I fully agree that they need to wait until the DM says "you have a long rest". but what if they accidentally press it because #reasons. Do you want to take half an hour to restore their spell slots and discuss how much HP they had or to you want to tell them "well then push the reset button"????
It even happened on critical role. so yes it's perfectly possible to accidentally take a long rest. even the best players are sometimes enthusiastic and do this.
I think you're misunderstanding the post. NOT POSTING FOR A SYSTEM ISSUE. only posting for an interesting addition to the application.
if I thought this was a system issue I would have posted in bugs and support or something. I POSTED IN DND BEYOND FEEDBACK.
I fully agree that the Players should not apply a full rest until the DM states it's ok. however things happen WITH ON THE BEST TABLES. as seen on CRITICAL ROLE at the end of Season 2 episode 120.
so MY FEEDBACK to the developers is to perhaps add the undo button in case this happens. I'M NOT SAYING THAT IT'S A SYSTEM ERROR IN ANY WAY OR FORM. JUST THAT IT MIGHT HELP IF ERROR'S OCCUR BY EITHER THE PLAYERS OR THE DM.
Oh - I think YOU misunderstand we all get YOUR point but frankly it is not something WE believe the system should do. End of it.
if YOUR PCs are hitting long rest before the end of the rest than that is a problem at YOUR table. Sure critical role, a popular online game had this issue ad guess what I watch the show. Liam also over used spell slots all the time because he forgot to mark them. Should DDB make a feature that says "This is a pop up reminder to ask if you have correctly marked off spells in the past 30 mins."
PCs hitting long rest before the DM tells them is a failure of that player and in the opinion of those that have commented against you, NOT something that DDB should put design effort into. If they make an undo for Long rests (which lets not even get into the infeasibility of it since the server caching error we deal with now would only get worse if DDB had to recall the previous save state of everyone's character sheet) why not make an undo button for everything? Again PCs making mistakes and doing things they shouldn't be doing is NOT what this system is for. The character sheet is there to aid in the game, not play it for the players.
If there was an “undo” button it wouldn’t be the worst thing, but there are other priorities I’d rather they focus on first. And besides, sometimes it’s gotta sting if we’re to learn. There isn’t always an “undo” button, and sometimes we as people just need to accept that and learn to be more careful. Inter having to undo it all manually once or twice, I’ll bet people stop making that mistake.
Entering XP is an undo thing that if you click the wrong thing (newbs) it can completely upend weeks/months of character work and updates. An undo button/backtrack would be key. Sure, in a Long Rest situation, fine. But in general, an undo button would be a good idea for ppl who hit the wrong button and don't realize it because it's their first campaign and they don't know any better.
Entering XP is an undo thing that if you click the wrong thing (newbs) it can completely upend weeks/months of character work and updates. An undo button/backtrack would be key. Sure, in a Long Rest situation, fine. But in general, an undo button would be a good idea for ppl who hit the wrong button and don't realize it because it's their first campaign and they don't know any better.
I am not disagreeing with you, I want to be clear about that. I do however have two questions to ask:
If the player makes a mistake and doesn’t realize it, how would they know to hit the undo button?
If one accidentally hits the wrong thing when managing XP, how would that completely upend anything? Could you please give an example of whatever it is I am not thinking of? Because I cannot think of a situation where it should be enough to ruin weeks or months of work.
If one adds too much they can remove the excess, if someone removes XP accidentally it can be added back. If someone accidentally sets their XP or level incorrectly, they could be reset to the correct number. I suppose it’s possible to not know or remember the correct numbers, but it is unlikely to not be able to get it at least pretty close to correct again. I know XP is neither horseshoes nor hand grenades, but it also doesn’t need to be tight enough to prevent atmosphere from leaking into space or water leaking into a submarine either. It could definitely be upsetting at first, especially for the unfamiliar, but it shouldn’t be something to "completely upend” anything, least not weeks or months of work. Considering that the concern is for newer players, the XP benchmarks are fairly low and close together at lower levels of play, 300 for 2nd level, 900 for 3rd, and then 2,700 for 4th level. By the time someone hits 4th level I would figure that player to have entered XP at least 5 or 6 times if not more, so I personally wouldn’t call them “new.” If for example a 2nd level PC has 427 XP, and next session their player accidentally adds 552 XP instead of 332, it shouldn’t be that bad. Even if they can’t remember what they had or what they accidentally entered, and can’t figure out it should be a total of 759 instead of 979, the only real immediate issue would be the fact that they prematurely broke 3rd level by accident. But that won’t actually add a class level or anything since the system doesn’t know if they want to multiclass or not. So the new player goes “woohoo, 3rd level!” Everyone else would look at them and ask how since they’re still around 200 XP short, give or take. Okay, now the table is aware a mistake has been made. So the DM says, “that must be a mistake, do you know what it’s sposta be?” Even if they say “no,” at least the more experienced players know it’s somewhere around 200 XP over. So if 200 CP gets removed and they end up with 779 XP instead of 759, it isn’t that big of a miscalculation. The rest of the party should all still break 900 on the same session, and then it’s 1,600 more to go before 4th level. That 20 XP discrepancy will likely be forgotten by next session, and should become irrelevant the next time they get XP if it already isn’t.
What is it I am apparently missing? And again, I am by no means disagreeing with you about an [UNDO] button. That’s not the point, I’m genuinely just unable to see why it should be so disastrous.
Undo is notoriously hard or expensive, sometimes both, in computer science (and impossible almost everywhere else). Just learn to use the application more carefully.
I would like an Undo function, too. Sometimes these things happen. Also with healing, damage, etc: sometimes the player or DM realizes a mistake was made, but we don't remember what the exact number was.
Being able to call-up a Historyof all values changed would be nice. (even if the page was refreshed.) The digital sheet doesn't have pencil marks.
Oftentimes, people are too eager to blame the person to excuse anything lacking from the system. This is a rookie error.
The undo button is one such thing; "Don't make a mistake" doesn't help here. People make mistakes, any competent designer knows that.
Thank you OP for commenting this due to experiencing a problem that Developers would want to be aware of, holding firm to your sensible point despite being told it's your problem, and not being cowed by implications of majority disagreement or illogical rantings which use the slippery slope fallacy.
Rest assured that, while people may imply to represent me or others through broader language such as "we", they do not actually represent me nor the broader base of D&DBeyond users.
I will always be a proponent to basic user-friendly design concepts. It's common sense.
Save points might be reasonable for trying out things but a complete history enabling real rolling forwards and backwards is either extremely expensive in memory terms if done naively or extremely difficult (and will result in lots of bugs) if trying to do it by bidirectional functions. Don't do it.
Oh - I think YOU misunderstand we all get YOUR point but frankly it is not something WE believe the system should do. End of it.
if YOUR PCs are hitting long rest before the end of the rest than that is a problem at YOUR table. Sure critical role, a popular online game had this issue ad guess what I watch the show. Liam also over used spell slots all the time because he forgot to mark them. Should DDB make a feature that says "This is a pop up reminder to ask if you have correctly marked off spells in the past 30 mins."
PCs hitting long rest before the DM tells them is a failure of that player and in the opinion of those that have commented against you, NOT something that DDB should put design effort into. If they make an undo for Long rests (which lets not even get into the infeasibility of it since the server caching error we deal with now would only get worse if DDB had to recall the previous save state of everyone's character sheet) why not make an undo button for everything? Again PCs making mistakes and doing things they shouldn't be doing is NOT what this system is for. The character sheet is there to aid in the game, not play it for the players.
Thank goodness most developers don't have your kind of mindset.
Oh - I think YOU misunderstand we all get YOUR point but frankly it is not something WE believe the system should do. End of it.
if YOUR PCs are hitting long rest before the end of the rest than that is a problem at YOUR table. Sure critical role, a popular online game had this issue ad guess what I watch the show. Liam also over used spell slots all the time because he forgot to mark them. Should DDB make a feature that says "This is a pop up reminder to ask if you have correctly marked off spells in the past 30 mins."
PCs hitting long rest before the DM tells them is a failure of that player and in the opinion of those that have commented against you, NOT something that DDB should put design effort into. If they make an undo for Long rests (which lets not even get into the infeasibility of it since the server caching error we deal with now would only get worse if DDB had to recall the previous save state of everyone's character sheet) why not make an undo button for everything? Again PCs making mistakes and doing things they shouldn't be doing is NOT what this system is for. The character sheet is there to aid in the game, not play it for the players.
Lmao, this guy is an absolute condescending clown and does not speak for the entire community here.
OP, you're on the money here, an undo button would be a very welcome addition. I don't think it should be the next bit of functionality they build, but eventually it would be nice touch.
Bit late to the party, but I'm completely new to this and started building a character with some friends today. Wanted to check what point buy was for ability scores, found out it's not what I wanted and returned to standard array. Whole table was cleared and I have to dive into it again. I expected at least a warning before these kind of changes, undo button would have been great.
I'll probably just write my stuff down now and not use the builder at all
Hey DND beyond team
first and foremost awesome application. but perhaps it's an idea to add an undo button to it. it happens some times that they try to take a long rest and during the last watch something happens and they are in an encounter. the cries off "oh crap I already hit long rest" happen often. though this is the fault off the players because I haven't said they received a long rest. it might be handy to have a reset button to restore the last changes.
thx
I mean you can't just "accidentally" take a long rest. The button itself literally requires you to click, then click confirm.
This is not a software issue - this is a table issue.
The players should wait until the DM confirms the Long Rest was successful before hitting that button.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
I fully agree that they need to wait until the DM says "you have a long rest". but what if they accidentally press it because #reasons. Do you want to take half an hour to restore their spell slots and discuss how much HP they had or to you want to tell them "well then push the reset button"????
It even happened on critical role. so yes it's perfectly possible to accidentally take a long rest. even the best players are sometimes enthusiastic and do this.
And again this is a PLAYER issue.
Not a system issue.
I think you're misunderstanding the post. NOT POSTING FOR A SYSTEM ISSUE. only posting for an interesting addition to the application.
if I thought this was a system issue I would have posted in bugs and support or something. I POSTED IN DND BEYOND FEEDBACK.
I fully agree that the Players should not apply a full rest until the DM states it's ok. however things happen WITH ON THE BEST TABLES. as seen on CRITICAL ROLE at the end of Season 2 episode 120.
so MY FEEDBACK to the developers is to perhaps add the undo button in case this happens. I'M NOT SAYING THAT IT'S A SYSTEM ERROR IN ANY WAY OR FORM. JUST THAT IT MIGHT HELP IF ERROR'S OCCUR BY EITHER THE PLAYERS OR THE DM.
Oh - I think YOU misunderstand we all get YOUR point but frankly it is not something WE believe the system should do. End of it.
if YOUR PCs are hitting long rest before the end of the rest than that is a problem at YOUR table. Sure critical role, a popular online game had this issue ad guess what I watch the show. Liam also over used spell slots all the time because he forgot to mark them. Should DDB make a feature that says "This is a pop up reminder to ask if you have correctly marked off spells in the past 30 mins."
PCs hitting long rest before the DM tells them is a failure of that player and in the opinion of those that have commented against you, NOT something that DDB should put design effort into. If they make an undo for Long rests (which lets not even get into the infeasibility of it since the server caching error we deal with now would only get worse if DDB had to recall the previous save state of everyone's character sheet) why not make an undo button for everything? Again PCs making mistakes and doing things they shouldn't be doing is NOT what this system is for. The character sheet is there to aid in the game, not play it for the players.
If there was an “undo” button it wouldn’t be the worst thing, but there are other priorities I’d rather they focus on first. And besides, sometimes it’s gotta sting if we’re to learn. There isn’t always an “undo” button, and sometimes we as people just need to accept that and learn to be more careful. Inter having to undo it all manually once or twice, I’ll bet people stop making that mistake.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Entering XP is an undo thing that if you click the wrong thing (newbs) it can completely upend weeks/months of character work and updates. An undo button/backtrack would be key. Sure, in a Long Rest situation, fine. But in general, an undo button would be a good idea for ppl who hit the wrong button and don't realize it because it's their first campaign and they don't know any better.
I am not disagreeing with you, I want to be clear about that. I do however have two questions to ask:
If the player makes a mistake and doesn’t realize it, how would they know to hit the undo button?
If one accidentally hits the wrong thing when managing XP, how would that completely upend anything? Could you please give an example of whatever it is I am not thinking of? Because I cannot think of a situation where it should be enough to ruin weeks or months of work.
If one adds too much they can remove the excess, if someone removes XP accidentally it can be added back. If someone accidentally sets their XP or level incorrectly, they could be reset to the correct number. I suppose it’s possible to not know or remember the correct numbers, but it is unlikely to not be able to get it at least pretty close to correct again. I know XP is neither horseshoes nor hand grenades, but it also doesn’t need to be tight enough to prevent atmosphere from leaking into space or water leaking into a submarine either.
It could definitely be upsetting at first, especially for the unfamiliar, but it shouldn’t be something to "completely upend” anything, least not weeks or months of work. Considering that the concern is for newer players, the XP benchmarks are fairly low and close together at lower levels of play, 300 for 2nd level, 900 for 3rd, and then 2,700 for 4th level. By the time someone hits 4th level I would figure that player to have entered XP at least 5 or 6 times if not more, so I personally wouldn’t call them “new.”
If for example a 2nd level PC has 427 XP, and next session their player accidentally adds 552 XP instead of 332, it shouldn’t be that bad. Even if they can’t remember what they had or what they accidentally entered, and can’t figure out it should be a total of 759 instead of 979, the only real immediate issue would be the fact that they prematurely broke 3rd level by accident. But that won’t actually add a class level or anything since the system doesn’t know if they want to multiclass or not. So the new player goes “woohoo, 3rd level!” Everyone else would look at them and ask how since they’re still around 200 XP short, give or take.
Okay, now the table is aware a mistake has been made. So the DM says, “that must be a mistake, do you know what it’s sposta be?” Even if they say “no,” at least the more experienced players know it’s somewhere around 200 XP over. So if 200 CP gets removed and they end up with 779 XP instead of 759, it isn’t that big of a miscalculation. The rest of the party should all still break 900 on the same session, and then it’s 1,600 more to go before 4th level. That 20 XP discrepancy will likely be forgotten by next session, and should become irrelevant the next time they get XP if it already isn’t.
What is it I am apparently missing? And again, I am by no means disagreeing with you about an [UNDO] button. That’s not the point, I’m genuinely just unable to see why it should be so disastrous.
Thanks in advance for helping me understand.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Undo is notoriously hard or expensive, sometimes both, in computer science (and impossible almost everywhere else). Just learn to use the application more carefully.
I would like an Undo function, too. Sometimes these things happen. Also with healing, damage, etc: sometimes the player or DM realizes a mistake was made, but we don't remember what the exact number was.
Being able to call-up a History of all values changed would be nice. (even if the page was refreshed.) The digital sheet doesn't have pencil marks.
Oftentimes, people are too eager to blame the person to excuse anything lacking from the system. This is a rookie error.
The undo button is one such thing; "Don't make a mistake" doesn't help here. People make mistakes, any competent designer knows that.
Thank you OP for commenting this due to experiencing a problem that Developers would want to be aware of, holding firm to your sensible point despite being told it's your problem, and not being cowed by implications of majority disagreement or illogical rantings which use the slippery slope fallacy.
Rest assured that, while people may imply to represent me or others through broader language such as "we", they do not actually represent me nor the broader base of D&DBeyond users.
I will always be a proponent to basic user-friendly design concepts. It's common sense.
Save points might be reasonable for trying out things but a complete history enabling real rolling forwards and backwards is either extremely expensive in memory terms if done naively or extremely difficult (and will result in lots of bugs) if trying to do it by bidirectional functions. Don't do it.
What an interesting thread!
I just made a mistake and have been using dndbeyond for years.
Mistakes happen. An undo button (or history of character changes) would be handy.
Thank goodness most developers don't have your kind of mindset.
Lmao, this guy is an absolute condescending clown and does not speak for the entire community here.
OP, you're on the money here, an undo button would be a very welcome addition. I don't think it should be the next bit of functionality they build, but eventually it would be nice touch.
Bit late to the party, but I'm completely new to this and started building a character with some friends today.
Wanted to check what point buy was for ability scores, found out it's not what I wanted and returned to standard array.
Whole table was cleared and I have to dive into it again. I expected at least a warning before these kind of changes, undo button would have been great.
I'll probably just write my stuff down now and not use the builder at all
You’re ditching because you have to assign the same six numbers to the same six abilities a second time?
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting