5ET-1361 Consistent handling of statblocks based on adjustments if the base statblock got reprinted #1378
Description
Information
Some Statblocks on 5e.tools aren't part of the books inherently but a result of convenience for potential users, e.g. the Moonshark from CRCotN is, by the book, a giant shark with a few adjustments.
With the Monster Manual 2025, the giant shark itself got reprinted and changed (more movement speed, less HP), so by that logic there should be a Moonshark based on the new version of a giant shark as well for anyone that wants to run CRCotN with 2024/5 rules.
Who would use it?
A specific usecase would be the ones running "older" adventures based on the 2024 ruleset, however it could arguably also be used backwards (new adventures run in the old ruleset) and would ideally be a futureproof system that could be used/reused whenever a similar situation arises
How would it work?
I'm not really sure how the best solution looks like. Maybe it is a flag for "convenience statblocks" that aren't inherently part of the book but created for, as mentioned, convenience reasons, that can then be additionally tagged with the old or new version. Maybe it is simply a Moonshark (2025). Maybe something else.
Why should this be added?
Essentially, if there is a Moonshark based on the 2014 MM, there is no reason for there to not be one based on the 2025 MM
This would make it easier for DMs to run adventures without needing to double-check every statblock and if it is up-to-date
- shirox_ (Shirox)
Indifferent - spap (Spappz)
Indifferent - f0rgetful (absentminded)
Upvote - hareblix (Hare Blix)
Downvote - rad0n222 (Radon)
Upvote - josephhan0826 (Josie2000)
Upvote - dito1917 (É)
Indifferent - meifl (Luis)
Upvote - _kimura (Kimura)
Upvote - earlofham (EarlOfHam)
Upvote - sirleonelle (Leo)
Votes: +6 / -1 / ±3