Character Vault
Any Concept / Any System
Compendium
Your System Come To Life
Roll20 for Android
Streamlined for your Tablet
Roll20 for iPad
Streamlined for your Tablet

Personal tools

Difference between revisions of "Storage Allocation"

From Roll20 Wiki

Jump to: navigation, search
m (added "See Also"-section and missing category tag)
 
(10 intermediate revisions by one user not shown)
Line 1: Line 1:
Storage and Management
+
To help users manage assets and account storage limitations as well as control game size and performance, here is a guide to how things you upload, purchase, or create are stored and managed on Roll20. For more information on managing your assets and games, see the wiki pages for [[Best_Practices_for_Files_on_Roll20|best practices on handling files]] or [[Optimizing_Roll20_Performance|improving game performance]].
  
To help users manage assets and account storage limitations as well as control game size, here is a table of how things you upload, purchase or create are stored and managed on Roll20
 
 
{| class="wikitable" style="text-align:center"
 
{| class="wikitable" style="text-align:center"
 
|-
 
|-
! Item !! Calculated in User's Account Storage !! Loaded with Game
+
! Item !! Calculated in User's Account Storage !! Loaded with Game†
 
|-
 
|-
 
| Art || Y || Y
 
| Art || Y || Y
Line 12: Line 11:
 
| Music Linked to || N || N
 
| Music Linked to || N || N
 
|-
 
|-
| Character Sheets || U || Y
+
| Character Sheets || N || Y
 
|-
 
|-
| Handouts || U || Y
+
| Pages (Map Pages) || N || Y
 
|-
 
|-
| Macros || U || Y
+
| Handouts || N || Y
 
|-
 
|-
| Card Decks || U || Y
+
| Macros || N || Y
 
|-
 
|-
| Tables || U || Y
+
| Card Decks || N || Y
 
|-
 
|-
| API Scripts || U || Y
+
| Tables || N || Y
 +
|-
 +
| API Scripts || N || Y
 
|-
 
|-
 
| Marketplace Modules || N || Y
 
| Marketplace Modules || N || Y
Line 39: Line 40:
 
N = No, this item does not count in this category
 
N = No, this item does not count in this category
  
U = Unclear, need an answer on this.
+
† For an item to count as being loaded at runtime, it must be deployed within the game. An image in your Art Library does not get loaded at run time unless it has been placed onto the tabletop.
 +
 
 +
''Keep in mind that any item that uses another item, (for example, a handout containing art from the user library) will count the art as being "in the game". A card deck takes up minimal memory, but all of the images are counted in the Art library.''
 +
 
 +
== How Each Type of Item is Handled ==
 +
 
 +
Here is more detail explaining how Roll20 treats each part of your games.
 +
 
 +
===Art===
 +
 
 +
Art you upload from your own computer goes into your Art Library. This is counted as part of your Account Storage quota. However, unless a piece of art is actually on the tabletop, it does not count as part of your game size—it is not loaded into your browser memory at game launch. The number and size of art assets can greatly impact the performance of your game. It is a good idea to be familiar with the [[Best_Practices_for_Files_on_Roll20#Images_and_Animations|Best Practices for Art and Animations on Roll20]].
 +
 
 +
===Audio Uploaded===
 +
 
 +
Audio you upload from your own computer goes into your My Audio section of the Jukebox. This is counted as part of your storage quota. However, Audio is streamed directly from storage, and does not count as part of your game size—it is not loaded into your browser memory at game launch. It is a good idea to be familiar with the [[Best_Practices_for_Files_on_Roll20#Audio_Files|Best Practices for Audio Files on Roll20]].
 +
 
 +
===Music Linked to===
 +
Music that you link to from one of Roll20's partners does not count as part of your storage quota. It is merely a pointer to a streaming source. Neither is it loaded in to your browser memory at game launch.
 +
 
 +
===Character Sheets===
 +
Character sheets do not count as part of your storage quota. However, they are loaded into your browser memory at game launch. Large numbers of complex character sheets can greatly impact your game performance, and lead to slow load times.For more information, see [[Optimizing_Roll20_Performance|Optimizing Roll20 Performance]].
 +
 
 +
===Pages (Map Pages)===
 +
Map pages themselves do not count as part of your storage quota. However, they are loaded into your browser memory at game launch. The graphics on them are counted as part of your Art Library, but the pages themselves do not take up any Account Storage. Because pages usually contain very large images that are placed onto the table top, and because they may contain Dynamic Lighting Features, or records of what players have seen with Advanced Fog of War, they may become large enough to impact performance. As with character sheets, Roll20 recommends keeping the number of map pages small and manageable. Too many map pages can lead to slow load times.
 +
 
 +
===Handouts===
 +
 
 +
The text of a Handout is loaded into your game at runtime. The image is not, unless it is displayed. Handouts have minimal impact on the size of your game, and because the images are in your Art Library, handouts themselves do not take up any Account Storage
 +
 
 +
===Macros===
 +
 
 +
The text of Macros is loaded into your game at runtime. However, unless you have thousands of extremely complex macros, this is not likely to affect performance in any measurable way.
 +
 
 +
===Rollable Tokens and Card Decks===
 +
 
 +
Rollable Tokens and Card Decks are quite small in space they take up. Images are not "double-dipped" from your Art Library storage. These items will only impact your game size if the assets are actually deployed onto a page. A rollable token that has a hundred faces, but with only ten of them showing on a given page will only count the images that are showing when considering game size. They will not affect your Account Storage because the images are already accounted for in your Art Library.
 +
 
 +
===Tables===
 +
 
 +
The text of Rollable Tables is loaded into your game at runtime. Unless your tables are extremely numerous and complex (dozens of tables with hundreds of items each) they should not affect performance in any measurable way. Images in Rollable Tables will not affect your Account Storage because the images are already accounted for in your Art Library.
 +
 
 +
===API Scripts===
 +
 
 +
The text of API Scrips (Pro feature) is loaded into your game at runtime. Unless a script is inefficiently written or conflicts with other scripts, they should not affect performance in any measurable way.
 +
 
 +
===Marketplace Art===
 +
 
 +
Artwork purchased from the Marketplace (tokens, tiles, maps animation and similar items) do not count as part of your storage quota. However, they are loaded into your browser memory at game launch. Unless a piece of Marketplace art is actually on the tabletop, it does not count as part of your game size—it is not loaded into your browser memory at game launch. Marketplace Art that you download and re-upload, or have added to your library with the Add to My Library button, ''does'' count as part of your storage quota. The number and size of art assets can greatly impact the performance of your game. It is a good idea to be familiar with the [[Best_Practices_for_Files_on_Roll20#Images_and_Animations|Best Practices for Art and Animations on Roll20]]
 +
 
 +
===Marketplace Modules===
 +
 
 +
Modules purchased from the Marketplace do not count as part of your storage quota. However, they are loaded into your browser memory at game launch. Some modules were originally created as print products and not designed for a Virtual Tabletop. As such, they may contain significant numbers of very large maps and many characters. Roll20 has done everything within their power to make these modules run and load smoothly. However, users should be aware of the realities of storage and management before making any significant changes or additions.
 +
 
 +
===Marketplace Addons===
  
For an item to count as being loaded at runtime, it must be deployed within the game. An image in your library does not get loaded at run time unless it has been placed onto the tabletop.
+
Addons are very similar to modules in how they are treated for the purposes of storage and game management. Large Addons (usually small adventures) can add significant numbers of deployed assets. Users should be aware of the realities of storage and management before including Addons to games that are already very large or complex. Fortunately, assets placed into a game by Addons can be deleted and replaced as needed.
  
''Keep in mind that any item that uses another item. I.e. a handout containing art from the user library) will count the art as being "in the game". A card deck takes up minimal memory, but all of the images are counted in the Art library.''
+
==See Also==
 +
* [[Best Practices for Files on Roll20|Best Practices for Files on Roll20]]
 +
* [[Optimizing Roll20 Performance]]
 +
<br />
 +
[[Category:Tips]]

Latest revision as of 18:41, 17 May 2019

To help users manage assets and account storage limitations as well as control game size and performance, here is a guide to how things you upload, purchase, or create are stored and managed on Roll20. For more information on managing your assets and games, see the wiki pages for best practices on handling files or improving game performance.

Item Calculated in User's Account Storage Loaded with Game†
Art Y Y
Music Uploaded Y N
Music Linked to N N
Character Sheets N Y
Pages (Map Pages) N Y
Handouts N Y
Macros N Y
Card Decks N Y
Tables N Y
API Scripts N Y
Marketplace Modules N Y
Marketplace Art (token images and map items) N Y
Marketplace Modules N Y
Marketplace Addons N Y
Marketplace Decks N Y

Y = Yes this item counts in this category

N = No, this item does not count in this category

† For an item to count as being loaded at runtime, it must be deployed within the game. An image in your Art Library does not get loaded at run time unless it has been placed onto the tabletop.

Keep in mind that any item that uses another item, (for example, a handout containing art from the user library) will count the art as being "in the game". A card deck takes up minimal memory, but all of the images are counted in the Art library.

Contents

[edit] How Each Type of Item is Handled

Here is more detail explaining how Roll20 treats each part of your games.

[edit] Art

Art you upload from your own computer goes into your Art Library. This is counted as part of your Account Storage quota. However, unless a piece of art is actually on the tabletop, it does not count as part of your game size—it is not loaded into your browser memory at game launch. The number and size of art assets can greatly impact the performance of your game. It is a good idea to be familiar with the Best Practices for Art and Animations on Roll20.

[edit] Audio Uploaded

Audio you upload from your own computer goes into your My Audio section of the Jukebox. This is counted as part of your storage quota. However, Audio is streamed directly from storage, and does not count as part of your game size—it is not loaded into your browser memory at game launch. It is a good idea to be familiar with the Best Practices for Audio Files on Roll20.

[edit] Music Linked to

Music that you link to from one of Roll20's partners does not count as part of your storage quota. It is merely a pointer to a streaming source. Neither is it loaded in to your browser memory at game launch.

[edit] Character Sheets

Character sheets do not count as part of your storage quota. However, they are loaded into your browser memory at game launch. Large numbers of complex character sheets can greatly impact your game performance, and lead to slow load times.For more information, see Optimizing Roll20 Performance.

[edit] Pages (Map Pages)

Map pages themselves do not count as part of your storage quota. However, they are loaded into your browser memory at game launch. The graphics on them are counted as part of your Art Library, but the pages themselves do not take up any Account Storage. Because pages usually contain very large images that are placed onto the table top, and because they may contain Dynamic Lighting Features, or records of what players have seen with Advanced Fog of War, they may become large enough to impact performance. As with character sheets, Roll20 recommends keeping the number of map pages small and manageable. Too many map pages can lead to slow load times.

[edit] Handouts

The text of a Handout is loaded into your game at runtime. The image is not, unless it is displayed. Handouts have minimal impact on the size of your game, and because the images are in your Art Library, handouts themselves do not take up any Account Storage

[edit] Macros

The text of Macros is loaded into your game at runtime. However, unless you have thousands of extremely complex macros, this is not likely to affect performance in any measurable way.

[edit] Rollable Tokens and Card Decks

Rollable Tokens and Card Decks are quite small in space they take up. Images are not "double-dipped" from your Art Library storage. These items will only impact your game size if the assets are actually deployed onto a page. A rollable token that has a hundred faces, but with only ten of them showing on a given page will only count the images that are showing when considering game size. They will not affect your Account Storage because the images are already accounted for in your Art Library.

[edit] Tables

The text of Rollable Tables is loaded into your game at runtime. Unless your tables are extremely numerous and complex (dozens of tables with hundreds of items each) they should not affect performance in any measurable way. Images in Rollable Tables will not affect your Account Storage because the images are already accounted for in your Art Library.

[edit] API Scripts

The text of API Scrips (Pro feature) is loaded into your game at runtime. Unless a script is inefficiently written or conflicts with other scripts, they should not affect performance in any measurable way.

[edit] Marketplace Art

Artwork purchased from the Marketplace (tokens, tiles, maps animation and similar items) do not count as part of your storage quota. However, they are loaded into your browser memory at game launch. Unless a piece of Marketplace art is actually on the tabletop, it does not count as part of your game size—it is not loaded into your browser memory at game launch. Marketplace Art that you download and re-upload, or have added to your library with the Add to My Library button, does count as part of your storage quota. The number and size of art assets can greatly impact the performance of your game. It is a good idea to be familiar with the Best Practices for Art and Animations on Roll20

[edit] Marketplace Modules

Modules purchased from the Marketplace do not count as part of your storage quota. However, they are loaded into your browser memory at game launch. Some modules were originally created as print products and not designed for a Virtual Tabletop. As such, they may contain significant numbers of very large maps and many characters. Roll20 has done everything within their power to make these modules run and load smoothly. However, users should be aware of the realities of storage and management before making any significant changes or additions.

[edit] Marketplace Addons

Addons are very similar to modules in how they are treated for the purposes of storage and game management. Large Addons (usually small adventures) can add significant numbers of deployed assets. Users should be aware of the realities of storage and management before including Addons to games that are already very large or complex. Fortunately, assets placed into a game by Addons can be deleted and replaced as needed.

[edit] See Also