alexander h. said: SkyCaptainXIII said: alexander h. said: I agree, it doesn't appear to be something most people want, so the best option would be to create a fork of the sheet and use that instead. I personally don't want it, and I really like how snappy this sheet is, compared to what it was in the old version. It's much faster, and it would be a shame to lose that for most users, so a few users can gain a feature they have already implemented on a customised version of the sheet. Again, even if I did fork the sheet... it WILL NOT show up in the drop down list and wouldn't serve the purpose of being able to use it in other DM's games without bothering them to change the character sheets they're already using to a custom one. There's already a crapload of other text fields on the sheet and adding a few more won't make a huge difference. That attitude is why so many programs have such terrible performance. "There's already a bunch of these calls, a few more won't hurt". A couple of extra text fields doesn't matter when you've only got a couple of sheets. But if you've got a lot of different monsters, those couple of extra text fields become a significant amount of extra text fields, and saving even a little becomes very important at that point. Plus, it sounds like each macro would have to have its own field, to give enough customisability. That means each item in each repeating section needs its own. A full caster like a cleric or wizard is definitely going to notice that. And you have to understand, from what you've said, you know of 3 DMs who are going to use this. 3 DMs getting something by default is not worth power users getting a slower sheet. And if it's something you personally can't do without, tell your DM and ask them to use the custom one. If you outline the benefits to using your custom sheet, if they're interested in the feature, they're probably going to use it. If they're not interested in that feature, why should they suffer reduced performance The bolded part is exactly why I don't want this. In my game, I already have a cleric where her PC struggles to open the sheet (very old laptop), and she's only Level 5, and she doesn't even have all her spells on there (I just delete and add spells for prepared so there is less lag). This sort of update would likely cripple her ability to play with the sheet, failing back on macros instead (and no, I won't kick someone from a game just because their PC can't handle a full sheet, especially as she's a RL friend). The problem with this whole issue, is that you are mainly thinking how this is best for you, not the playerbase at large. Just because it's an easy code change to make, doesn't mean it's the right one.