Code Style / Refactoring - Unwrapping highly nested functions

I'm looking through the implemented classes and trying to look for any issues or places to make them easier to read, learn from, and maintain.

Some cards seem to feature very heavily nested if statements, while others seem to return as soon as possible to keep the code flat.

Is one preferred by by the project over the other?

I personally find the flat style easier to read and reason about.