illandril / FoundryVTT-sheet5e-lockdown

MIT License
2 stars 0 forks source link

Update as needed for dnd5e 3.0 #90

Open illandril opened 7 months ago

illandril commented 7 months ago

Note: Supporting the new Default 5e Character Sheets is non-trivial, so it may take a while for full 3.0.0 support to be implemented.

If you use this module, and want to use the new 3.0.0 Default 5e Character Sheets, please let me know what settings you use so I can prioritize what people actually want.

FargoAckel commented 3 months ago

Note: Supporting the new Default 5e Character Sheets is non-trivial, so it may take a while for full 3.0.0 support to be implemented.

If you use this module, and want to use the new 3.0.0 Default 5e Character Sheets, please let me know what settings you use so I can prioritize what people actually want.

I've no idea how this is working - I just made an account for this module ;)

I love the new Sheets, but I also love your module. I regularly play DnD and my players are not really digital natives so I try to keep it as simple as possible for them. The first feature I'd really love to have again is to hide the tabs (bio, effects, empty spells, ...) and secondly I'd love to hide the edit-button at the top left and special-traits-button near the level.

illandril commented 2 months ago

@FargoAckel I think everything you asked for (as well as locking Short and Long Rests, and Inspiration) is included in the changes in 4.3.1.

I've got more I plan to add later, but not sure when that will be just yet.

VirusNik21 commented 2 months ago

Hi. All the options you marked as "Legacy, for now" are needed to prevent players from cheating during the game (my chaotic players may consider this an example of their "chaotic alig.":)). I also prefer to actually lock money, number of items, etc. It would also be nice to add an option to block experience changes - since the new DnD revision has a great "Award" tool for that.

illandril commented 2 months ago

@VirusNik21

Note that this is not a secure lockdown and players could get around the restrictions, so this is not a sufficient answer if your players are malicious. This is intended for games where the players are inexperienced (with D&D and/or with using computers) to prevent them from making mistakes (ex. accidentally adding/removing saving throw proficiency).

If you're concerned about cheating, this module isn't the solution. It will act as a superficial barrier to cheating, but that barrier can be easily bypassed (the easiest way is to just block the request that fetches the module). No module can reliably prevent a user who wants to cheat from cheating.

Consider...