Meadowboon

When this creature leaves the battlefield, put a +1/+1 counter on each creature target player controls.
Evoke {3}{W} (You may cast this spell for its evoke cost. If you do, it's sacrificed when it enters.)

Modern Masters

When Meadowboon leaves the battlefield, put a +1/+1 counter on each creature target player controls.
Evoke {3}{W} (You may cast this spell for its evoke cost. If you do, it's sacrificed when it enters the battlefield.)

Morningtide

When Meadowboon leaves play, put a +1/+1 counter on each creature target player controls.
Evoke {3}{W} (You may play this spell for its evoke cost. If you do, it's sacrificed when it comes into play.)

Effects that cause you to pay more or less to cast a spell will cause you to pay that much more or less while casting it for its evoke cost, too. That's because they affect the total cost of the spell, not its mana cost.

Evoke doesn't change the timing of when you can cast the creature that has it. If you could cast that creature spell only when you could cast a sorcery, the same is true for cast it with evoke.

If a creature spell cast with evoke changes controllers before it enters, it will still be sacrificed when it enters. Similarly, if a creature cast with evoke changes controllers after it enters but before its sacrifice ability resolves, it will still be sacrificed. In both cases, the controller of the creature at the time it left the battlefield will control its leaves-the-battlefield ability.

If you're casting a spell "without paying its mana cost," you can't use its evoke ability.

When you cast a spell by paying its evoke cost, its mana cost doesn't change. You just pay the evoke cost instead.

Whether evoke's sacrifice ability triggers when the creature enters depends on whether the spell's controller chose to pay the evoke cost, not whether they actually paid it (if it was reduced or otherwise altered by another ability, for example).