You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When using any piece of software, especially for the first time, things can be confusing or hidden where you wouldn't think to use them. Also we are going to have times where putting all the relevant little tidbits of info on how to use certain interface features would break design principles, so only the most immediately useful ones will be visible. When released we're going to have people who have never used Foundry before as well as veterans who maybe haven't used the systems we've been inspired by trying to understand how to make the most out of the system. They are likely to get frustrated or just not be aware of some time-saving tips if left to their own devices.
Describe the solution you'd like
I'd like to use Foundry's built-in tutorial system to give users an opt-in method to have a guided explanation of our work from within the platform itself. This would allow us to give a basic overview of Foundry functionality (though also suggesting they go back and watch the core FVTT guides first) and also highlight specific settings that will be needed/why we picked certain defaults, and also how to use our custom sheets.
User guides I'd suggest:
Welcome / Intro (GM-only)
Enabling / Using premium Module content / Compendiums (GM-only)
Creating Scenes (GM-only, points to core guide then gives explanation of our settings)
Creating Items (GM-only)
this would include setting attack / damage settings
cover physical item types and actor features such as paths/talents/etc
should we have a tutorial per Item Type?
Creating Characters / Adversaries (All players)
specifically explain the relationship between an actor sheet and any embedded items dropped into it
Levelling up (All players)
(Advanced) Creating Active Effects on Items (GM-only?)
Macro support? / QoL suggestions (All players)
Describe alternatives you've considered
This could also be done through static journal pages that include screenshots. The tutorial method would probably need more effort but might be more approachable.
Though we could also have both? Use static journals as a sort of transcript for the tutorials, in which case, start with the static guides?
Version
< 1.0.0
Additional context
Open to other topic suggestions, or a revised list, this is just a suggestion off the top of my head.
Checklist:
I have searched the existing issues to ensure this feature has not already been requested.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When using any piece of software, especially for the first time, things can be confusing or hidden where you wouldn't think to use them. Also we are going to have times where putting all the relevant little tidbits of info on how to use certain interface features would break design principles, so only the most immediately useful ones will be visible. When released we're going to have people who have never used Foundry before as well as veterans who maybe haven't used the systems we've been inspired by trying to understand how to make the most out of the system. They are likely to get frustrated or just not be aware of some time-saving tips if left to their own devices.
Describe the solution you'd like
I'd like to use Foundry's built-in tutorial system to give users an opt-in method to have a guided explanation of our work from within the platform itself. This would allow us to give a basic overview of Foundry functionality (though also suggesting they go back and watch the core FVTT guides first) and also highlight specific settings that will be needed/why we picked certain defaults, and also how to use our custom sheets.
User guides I'd suggest:
Describe alternatives you've considered
This could also be done through static journal pages that include screenshots. The tutorial method would probably need more effort but might be more approachable.
Though we could also have both? Use static journals as a sort of transcript for the tutorials, in which case, start with the static guides?
Version
< 1.0.0
Additional context
Open to other topic suggestions, or a revised list, this is just a suggestion off the top of my head.
Checklist:
The text was updated successfully, but these errors were encountered: