30 seconds or less cast

How it works

The phrase names a ceiling, not a typical length. “Or less” means anything from a moment up to thirty seconds, inclusive of thirty. A cast that takes thirty-one seconds fails the test. A cast that takes two seconds passes. The format you write on a sheet has to show that ceiling clearly, or someone will treat 0:30 as a target instead of a limit.

On a clock, thirty seconds is half of one minute. It is 1/120 of an SI hour. It is 30,000 milliseconds. Those are the same span in different unit clothing. A timer that shows 00:00:30, a timer that shows 0:30, and a field that shows 30 are only as honest as the labels on their columns. If the column is minutes, 30 is half an hour, and you have left the “or less” window by a factor of sixty.

How it works in practice is a unit check, then a start, then a stop: Write the limit in one notation and stick to it for the whole turn. Start the timer when the action actually begins, not when someone announced it.

Stop at completion, or at 0:30, whichever comes first if the rule is a cap. If the tool shows tenths, still treat 30.0 as the same ceiling as 30. A countdown and a count-up are different formats for the same limit. Countdown starts at 0:30 and dies at 0:00. Count-up starts at 0:00 and must not pass 0:30. Mixing them in one scene is how a table argues about whether the spell went off.

Clock spellings for a half minute

Common spellings of a thirty-second span are easy to swap by accident. 0:30 as m:ss is thirty seconds. 0:30 as h:mm is thirty minutes. 00:30:00 as hh:mm:ss is thirty minutes. 30 without a unit is a trap. ISO 8601 duration form PT30S is ugly on a character sheet and hard to misread as half an hour. PT0.5M is thirty seconds as a decimal minute; some parsers dislike the decimal.

Frames on video are not seconds. At 30 frames per second, thirty seconds is 900 frames. At 24 frames per second, thirty seconds is 720 frames. If a “cast” here means sending a clip to a screen, the time limit is still seconds. The frame count is a conversion after you know the frame rate. Do not write “30” in a frame field and a seconds field as if they matched.

Tabletop games that set a combat round at about six seconds give you a clean conversion: five rounds are thirty seconds. A single action inside one round is well under the ceiling. Published spell lists for that family of rules usually jump from one action to one minute, with nothing sitting at a dedicated thirty-second casting time. A filter labelled “30 seconds or less” therefore keeps the action, bonus-action, and reaction casts, and drops the one-minute work.

Thirty seconds is long enough to say the words and short enough that nobody should need a sandwich while you finish.

Cap, target, and ritual

A cap of thirty seconds or less is a rule about speed. A target of thirty seconds is a rule about pacing. A ritual that happens to finish in twenty seconds still had whatever casting time the text named. Do not rewrite a one-minute ritual as “or less” because this table was fast. The format on the card is the contract. The stopwatch is only the witness.

If two people share a scene, agree whether the thirty seconds is shared wall-clock time or a per-person budget. Shared wall-clock time means the scene ends at half a minute no matter who is talking. A per-person budget means each speaker gets a half minute. Those are different formats. Write which one you are using on the same line as 0:30, or you will hold both readings at once.

For kitchen work, “30 seconds or less” is a stir, a rest, or a blast of heat, not a roast. For a presentation, it is a single thought. For a game, it is in-world time unless the group said it was real-world time. In-world six-second rounds and real-world debate do not share a clock. Pick the clock before someone starts talking.