Fantasy class
Carnival · 2 ships · all charted
9 rules hold across all 2 hulls, and 2 things do not. The exceptions are the reason not to quote a sister ship from memory.
None of this is written down anywhere. It is computed by comparing the 2 ship records field by field, so a class rule cannot drift from the hulls that carry it — add an exception to a ship and it appears here on the next build.
Where the hulls differ
The part that does not transfer. Everything here is one ship's, not the class's.
One hull only
Carnival Elation1 of its own
- Ship-specific trapsElation's mini-golf was relocated in refit and gained a bocce court, so older deck plans put it in the wrong place.
Carnival Paradise1 of its own
- Ship-specific trapsMini-golf is aboard. I couldn't confirm whether this ship's was relocated the way Elation's was, so check the current plan rather than assuming they match.
Class geometry
A deck stack counts as the class's only when every hull carries the same one. A single ship differing makes it that ship's data, not the class's.
No deck stack has been transcribed for this class. The placement rule above is the operator's own and stands on its own; there is no table here to check it against.
That is a gap in what we have looked at, not a clean bill of health. Check this part of the booking the way you would without CruiseRead.
The ships
Every hull in the class, with what has been signed off on each.
- Carnival Elation
- Cabinverified
- Moneyverified
- Trapsverified
- Carnival Paradise
- Cabinverified
- Moneyverified
- Trapsverified
Each ship page carries its own exceptions in context, alongside the shared rules they sit inside.
Sources are recorded per ship, not per class. Each hull's page carries what its calls were checked against and when.