Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Is there a fundamental reason...?

Is there a fundamental reason why sheets in a game must all be the same type / style? Say you have a player that prefers the Community sheet, and one that prefers the Official sheet (and you don't toss him out). Is there something in particular where it would be exceptionally difficult to allow both sheet types in a single game?
1591241270
Kraynic
Pro
Sheet Author
Well, at this point they would have to be somehow totally separated so that none of the css styling for one used the same class references as the other, which would do a number on display of the sheet.  If they each have built in roll templates, the various templates would all have to have different names so that the template calls wouldn't get confused on which one to call. Or all 700+ sheets on the Roll20 github would have to be altered to have totally unique classes and roll template names from each other. They would also need to use either totally different attribute names or absolutely the same attribute names to keep macro attribute calls from getting confused or failing.  But since different sheets can have different features, there will be sure to be some things set up differently on one than the otherl, or things that exist on one sheet that simply don't on another, which takes us back to being totally separated somehow, meaning there might be some sort of addition to the macro system that would allow you to point the macro to a specific sheet. The potential downside to this is that an addition to the fundamental macro system would potentially interfere with every existing macro anyone is using on Roll20. Pretty much every hurdle with macros also applies to api script interaction with character sheets as well. Aside from any potential technical issues, whoever is running a game will need to learn how each separate sheet works, and be able and willing to tailor any GM side macros to be able to interact with different sheets depending on which player is using what.  I know there is a suggestion in the suggestion forums desiring this to happen, and maybe it is possible and much easier than I think it will be.  I think it is probably much more difficult than what people in that thread are thinking it may be however.  I suppose time (maybe) will tell.
1591243368

Edited 1591243383
GiGs
Pro
Sheet Author
API Scripter
Yes, there is a fundamental reason we cant have more than one sheet in a campaign. It's because - in a sense-  there is only one sheet in the campaign. All the different characters in the campaign are using the same sheet. Not the same type of sheet - the exact same sheet. They are connected. When sheet designers set up their sheet, they have to follow certain rules that dont exist elsewhere on the web. There's a type of element html uses called an id. This can be used to layout sheets, and different parts of the page can have different ids. But no two elements can share an id, they must be unique. We cant use ids on roll20, because if one sheet has an id, they all have it, and thus it's not unique. A change to one id would affect every character in the campaign identically.  Imagine there is only one sheet, but the character displayed on it changes. Like the character sheet is a book, and each character is a page in that book, and you flip through it whenever you look at a different character. This is a simplification, it's not exactly how things work. But it's a good way to conceptualise it.  This is why you cant have different sheets in a campaign: its in the foundations of how roll20 handles character sheets, and it would take a massive rebuild to enable different sheets. It's easy to imagine a way to make such a feature work- have each sheet in its own sandbox, isolated from the others. But saying that and doing it are two vastly different things: the technical hurdles to achieve it will be immense.  There's no real incentive to the devs to work on such a feature, when it would be so costly (in devtime and resources) and when it is needed by a tiny fraction of the userbase.
1591243522

Edited 1591243538
GiGs
Pro
Sheet Author
API Scripter
Kraynic said: I know there is a suggestion in the suggestion forums desiring this to happen, and maybe it is possible and much easier than I think it will be.  I think it is probably much more difficult than what people in that thread are thinking it may be however.  I suppose time (maybe) will tell. It's much, much harder than anyone voting for the feature realises. If they realised how hard it would be, they wouldnt be voting for it, and would put their vote somewhere that has a better chance of being done (which is likely  anything else  in the suggestion forum).
1591249291

Edited 1591249491
Gold
Forum Champion
Hi Shade. Please vote for the related Suggestion thread and add your comments. <a href="https://app.roll20.net/forum/post/7926666/more-than-1-character-sheet-template" rel="nofollow">https://app.roll20.net/forum/post/7926666/more-than-1-character-sheet-template</a> It is very,&nbsp; very easy to add your +1 vote of support. Some things get accomplished even when others say it is nearly impossible.