Artemis vs Medusa — the battle has no fixed spin count

Artemis vs Medusa by Quickspin is a medium-volatility ways game with published maximum exposure of 5,288× the bet. Its central distinction is an Unlimited Free Spins Battle: there is no fixed starting spin count, but there are clear resolution conditions.

“Unlimited” describes a feature without a fixed spin allocation, not a feature that can never end. Every spin updates a battle meter through monster accumulation and Artemis removals. The battle closes when the final monster type is destroyed or when the meter exceeds 15 and Artemis retreats.

Verified facts and missing specification

Quickspin confirms medium volatility, ways evaluation, 5,288× maximum exposure, base-only Monster Bounty Coins, last-reel golden-frame Artemis collection and a condition-led Free Spins battle triggered by three Scatters.

The readable page does not publish grid dimensions, number of ways, RTP, stake range, full paytable, Monster Coin values, exact bounty formula or New Zealand operator availability. Those fields require the exact live help. Do not derive them from artwork or another mythology title.

Base-game Monster Bounty Coins

Any medium-value monster symbol can contain a Monster Bounty Coin. The coins appear only in base play. Record the underlying monster type, its paytable value and the coin-marked positions.

The source does not state a separate printed denomination on the coin. It says the bounty depends on the value of the medium symbol that contained it and the number of coins present. Use the live history for the actual calculation.

A coin-bearing monster does not automatically pay a bounty. The collection condition requires the golden-frame Artemis on the last reel with accompanying bounty coins present.

Last-reel Artemis collector

When Artemis with a golden frame lands on the last reel, all Monster Bounty Coins present are collected and a bounty pays. Save Artemis’s coordinate and every coin-bearing monster on the screen.

The last-reel restriction is part of the condition. An Artemis image elsewhere should not be treated as the collector unless the live rules identify it. Distinguish the golden-frame version from any ordinary Artemis symbol.

After collection, compare the server credit with the live bounty table. The public page does not provide enough numeric detail to reconstruct every amount independently.

Bounty calculation evidence

Build a row for each collected coin: source monster, symbol value, position and contribution shown in history. Add coin count and final bounty as separate fields.

Do not assume a simple sum or multiplier formula. The provider only says the amount is related to source-symbol value and number of coins. “Related” is not a complete equation.

If the live history gives only the total, retain the component symbols and mark the intermediate formula unavailable rather than reverse-engineering it from one round.

Three-Scatter feature entry

Three Bonus Scatters trigger Unlimited Battle Free Spins. Capture the trigger grid, Scatter payment if any and opening battle meter.

There is no fixed spin allocation in the provider description. Do not place a conventional “10 Free Spins” value in metadata or FAQ. The number of feature spins depends on the battle’s evolving state and termination conditions.

Record each spin sequentially until the server declares victory or retreat.

Monster accumulation

During the battle, one or more Artemis symbols can land with accompanying medium Monster symbols. Those monsters are added to the meter. Record Artemis count, accompanying monster types and meter change.

The source says any time one or more Artemis symbols land, accompanying medium Monsters are accumulated. The live help should define exact positional or association rules. Do not add every visible monster without confirming it qualifies.

Keep meter count and monster-type composition. A total alone cannot show which type will be removed next.

Artemis removals

For every Artemis symbol that lands, one Monster type is removed from the meter, proceeding from the lowest value to the highest. The removal awards a bounty.

Record the ordered monster hierarchy from the live paytable. When multiple Artemis symbols land, log each removal separately and verify the sequence. Do not skip to the highest-value type simply because it offers a larger bounty.

The bounty is a settlement event distinct from the reduction in meter pressure. Both should appear in the feature ledger.

Lowest-to-highest priority

The battle rule creates deterministic priority once the current monster set is known. Identify the lowest-value remaining type before evaluating each Artemis removal.

If several copies of that type are accumulated, consult the live help to see whether an Artemis removes the type as a category, one unit or another defined amount. The marketing copy says a Monster type is removed but does not expose all counter detail.

Preserve the before-and-after meter rather than choosing an interpretation from animation alone.

Retreat condition

If at any time the meter exceeds 15, Artemis retreats and Free Spins end. “Exceeds 15” means the terminal threshold is above 15, not merely reaching 15, under the provider wording.

Record the opening meter, additions and removals in event order. If a spin both adds monsters and lands Artemis, the live history must establish whether removals occur before the threshold check. Do not guess the sequence.

Once the retreat condition is settled by the server, do not add hypothetical later battles or bounties.

Victory condition

The feature also ends when Artemis destroys the last monster. Record the final remaining type, Artemis event, bounty and terminal state.

Victory does not mean the player receives the published maximum exposure. It is a narrative resolution with whatever bounty and spin settlements the actual round produced.

Keep victory and retreat mutually identifiable in the history. A generic “bonus complete” screen should be paired with the final meter state.

The Medusa bounty concept

Quickspin’s introduction says every Medusa symbol added to the battlefield increases the Medusa Bounty and that defeating Medusa can produce a potentially large win. The readable rules excerpt does not give the exact Medusa formula.

Track Medusa separately from the other medium monsters if the live interface provides a dedicated bounty display. Record additions, removals and final award.

Do not turn the narrative phrase into a guaranteed jackpot or copy a value from a different version.

Complete battle ledger

Use one row per Free Spin with opening meter, Artemis count, qualifying accompanying Monsters, additions by type, removals in priority order, bounty credits, closing meter and terminal status.

Add a separate Medusa Bounty field where shown. The meter total should reconcile with additions and removals before checking the retreat threshold.

Because there is no fixed spin counter, the row sequence itself establishes feature length.

Worked battle example

Suppose the meter holds two lower-value monster types and Medusa. A spin adds more monsters and lands one Artemis. Under the stated priority, the live game should remove the lowest eligible type first and award its bounty, while the remaining composition carries forward.

If the additions push the meter above 15, event order becomes decisive. Use the server history to determine whether the Artemis removal occurred before retreat evaluation.

This example demonstrates the audit question, not an assumed formula or probable outcome.

Ways evaluation in base and bonus play

The provider calls Artemis vs Medusa a ways game but does not publish the number of ways or grid dimensions in readable copy. Record those from the live help.

Do not call the game a fixed-line slot. For ordinary wins, capture matching positions by reel and use the active paytable. Bounty settlements remain separate from normal ways credits.

The portrait-oriented design noted by the producer does not itself establish layout dimensions.

Maximum exposure and volatility

Quickspin labels medium volatility and 5,288× maximum exposure. Volatility describes the distribution of results, while maximum exposure is the model ceiling.

Neither metric determines how long one battle lasts. “Unlimited” does not raise the maximum beyond the published cap.

Do not use victory, retreat or Medusa count to calculate probability of reaching 5,288× without a complete model.

RTP and stake range

No readable RTP or stake range appears on the official page. Capture both from the launched game help with operator, game ID, version, currency and date.

If alternative RTP profiles exist, list them separately. Do not infer RTP from medium volatility, observed returns or maximum exposure.

Currency limits and New Zealand account access are deployment facts, not provider-wide assumptions.

Mobile and accessibility checks

The battle meter, monster-type composition, Artemis removals and Medusa Bounty must remain readable in portrait orientation. Symbols should have text or icons beyond colour alone.

The interface needs to show why a battle ended—victory or meter above 15. A hidden event log makes settlement difficult to audit.

After reconnecting, verify the same round, meter composition, battle state and balance before continuing.

Common interpretation errors

Unlimited Free Spins do not mean endless play. Three Scatters start a battle governed by two terminal conditions. The meter must exceed 15 for retreat under the wording, not simply equal it.

Bounty Coins are base-only and require the golden-frame last-reel Artemis for collection. They are not the same as monster accumulation inside Free Spins.

Medium volatility is not RTP, and 5,288× is not a promised bounty.

Who may prefer the game

The title may interest readers who prefer a feature with visible tactical state rather than a fixed counter. Monster composition and removal priority make every feature row auditable.

It may not suit anyone who wants a predictable feature length or who treats a rising Medusa Bounty as guaranteed credit. The battle can end by retreat before a desired removal.

Set a budget before entry and do not increase stake to chase a particular ending.

Interrupted battle procedure

Save the round ID, spin number, opening meter, monster types, Artemis events, bounty credits, closing meter, terminal state, stake and balance. Reopen the same version and compare restoration.

If the battle ends unexpectedly, provide the final meter and event order to authenticated support. If a base bounty fails to collect, show the golden-frame last-reel Artemis and coin-bearing monsters.

Never disclose passwords or authentication codes. Server history and screenshots provide the relevant evidence.

New Zealand scope

The provider page verifies the international product, not availability through a New Zealand-facing operator. A dated catalogue, eligible account and launchable help are required.

Do not infer local access from provider licensing or a foreign demo. RTP, stakes and exact bounty tables must come from the active deployment.

Final editorial audit

Check medium volatility, ways label, 5,288× maximum, base-only Bounty Coins, golden-frame last-reel Artemis, three-Scatter entry, low-to-high removals and the two terminal conditions.

Remove unverified grid, ways count, RTP, stakes, formulas and New Zealand access. The article passes when the battle meter can be reconstructed without inventing a fixed spin allocation or bounty equation.

Resolving simultaneous additions and removals

A single battle spin can show Artemis together with several medium Monsters. Capture the pre-spin meter, all qualifying additions and every Artemis removal. The order determines whether the meter crosses the retreat boundary before a low-value type is destroyed.

The readable page does not state that timing in enough detail. Use the live animation only as supporting evidence and obtain the server event order from history when a terminal condition is disputed. Do not rearrange events to produce the preferred ending.

Monster-type inventory

Create a type-level table from the live paytable: symbol name, relative value, current units on the meter and bounty state. This table makes the low-to-high removal rule auditable without guessing from icon size or colour.

Medusa should have her own row when the interface tracks a distinct bounty. Harpy, Griffon and Minotaur names appear in the provider’s theme description, but their precise pay hierarchy still requires the live paytable.

Battle settlement review

At feature end, reconcile ordinary ways wins, Artemis removal bounties and any Medusa award separately. The final screen may combine them, so retain component history where available.

A victory banner does not add an undocumented prize, and retreat does not erase already settled feature wins. Use the account balance and server round total rather than narrative animation.

Privacy and support evidence

Share the round ID, game version, meter states, symbol positions and balance through authenticated support. Redact unrelated account activity and never disclose a password or one-time code.

The vertical battlefield is visually rich, but a sequence of clear state screenshots is more useful than a video that omits the paytable and timestamps.

Comparative review method

Compare Artemis vs Medusa with fixed-spin games by termination logic, not feature length alone. Its two ending conditions replace a conventional counter, while the meter composition determines risk.

Any value comparison requires verified RTP and bounty formulas. Maximum exposure and medium volatility do not establish which battle structure returns more in practice.

Final state export

Retain the operator’s history with the trigger, every battle spin, meter changes, Artemis removals, bounties and terminal reason. Pair it with the live paytable used to order monster types from lowest to highest.

If the export reports only a combined feature win, keep the detailed worksheet as an editorial aid but do not claim its inferred component values are official. The server total remains authoritative.

Before closing the review, confirm that the final meter either shows the last monster destroyed or a value above 15. A feature that ends without either condition needs a versioned explanation from authenticated support.

Monster Bounty Coins in base play

Monster Bounty Coins appear only in the base game and can be embedded in medium-value monster symbols. When Artemis lands in a golden frame on the last reel with accompanying monster symbols, she collects the bounty coins present. The award depends on the source symbol values and the number collected.

Unlimited Free Spins Battle

Three Scatters trigger the feature. Monster symbols accumulate on the meter when Artemis lands with the relevant medium-value monsters. Each Artemis removes a monster type from the meter, starting with the lowest, and awards its bounty.

The battle ends in one of two ways:

• Artemis destroys the final monster; or
• the Monster meter exceeds 15 and Artemis retreats.

That structure makes meter position and remaining monster types more useful than a conventional “spins left” count.

RTP and availability

The readable Quickspin source does not expose one RTP percentage. It also does not confirm that the game or a specific casino is available to New Zealand users. Maximum exposure is not a promise, average return or recommendation.

Frequently asked questions

What triggers the battle? Three Scatters.

Is there a fixed number of Free Spins? No; the feature ends through its battle conditions.

Where do Monster Bounty Coins appear? Only in the base game, within medium symbols.

What causes Artemis to retreat? The meter exceeding 15.

What is the published maximum exposure? 5,288× the bet.

Is New Zealand availability confirmed? No.

Official source

• Quickspin: Artemis vs Medusa

Bottom line: read Artemis appearances, monster removals and meter level as one battle state rather than looking for a fixed spin counter.

How to verify the version you can actually open

A provider page proves that a title exists and describes the supplier's intended rules. It does not prove that a casino accepts players in New Zealand, that the title is enabled for a particular account, or that the highest published RTP is the version in the lobby. Treat availability, operator eligibility and product configuration as three separate checks.

Start with identity, then configuration

Open the game only through the authenticated casino lobby. The information or help panel should identify Quickspin, the exact title and the active mathematical return. Compare the reel or grid layout, paylines or cluster rules, named features and symbol behaviour with the official product material. Similar artwork or a matching title is not enough when the help file is missing or inconsistent.

When the supplier publishes several RTP values, report all of them as configurations. Do not assume the highest option is deployed. RTP is a theoretical long-run measure across a very large number of rounds; it is not a refund rate for one player and cannot predict the next result. Volatility is different: it describes how unevenly results are distributed on the provider's scale.

Read stake controls as money, not interface decoration

Provider sheets often quote a reference range in euros. That range does not establish New Zealand-dollar support or the limits in a specific account. Before a paid round, identify the total amount that will leave the balance. If the interface separates denomination, coins and lines, verify the combined total. If Extra Bet is active, calculate its full cost before pressing spin.

Feature-buy prices are multiples of the current bet, not promised returns. A 100x purchase at a $1 stake costs $100; at a $2 stake it costs $200. Availability can vary by market and some mathematical configurations may not support the control. If the live help does not explain the price, delivered feature and active RTP, leave the option unused.

Keep simulation figures in their proper scope

A game sheet may publish a maximum result observed in a large simulation. That is not automatically the contractual maximum payout and never describes a likely session. Preserve the provider's wording, sample size and configuration. Check the live rules for a binding cap and the operator terms for any separate payout limit. Do not turn an extreme result into a promotional headline.

Audit a disputed round

If an animation freezes or a connection drops, do not repeat the wager immediately. Reopen the game through the authenticated lobby and inspect round history. Record the time, total stake, balance movement and round identifier. The result can be settled by the gaming system even when the device never displays the final animation. Send evidence through verified operator support; never disclose a password, recovery phrase or one-time code.

Read the paytable as a calculation document

The paytable should explain what creates a win, which symbols substitute, where special symbols can land and how multiple awards combine. For line games, confirm direction and active paylines. For cluster games, confirm adjacency, minimum group size and the order of collection. For respins, identify what remains locked, what resets the counter and what ends the feature. A graphic effect can illustrate those rules but cannot replace them.

Separate addition from multiplication. Several prize values may be added before a multiplier applies, while reel-specific multipliers can sometimes multiply together only when each reel participates in the same win. Reconstruct one low-stake result from game history. If the arithmetic cannot be matched to the help file, stop and ask the operator rather than guessing.

Do not confuse hit frequency with a profitable round

Provider sheets can publish hit frequency or category probabilities. A hit simply means a round returned a qualifying amount; it can be smaller than the stake. “Big”, “Mega” or “Epic” thresholds are provider reporting categories, not promises. They are useful for comparing mathematical versions only when definitions and samples are the same.

Random outcomes do not become due after a long gap. A feature that appeared repeatedly in a demo or marketing clip has no obligation to repeat in a funded session. Previous rounds do not create a debt from the next random result.

Confirm market and device behaviour independently

A title can exist in the supplier catalogue while an operator disables it for a territory, currency, device or bonus. Language localisation is not evidence of legal availability. Confirm the operator's identity, accepted countries and current lobby separately from the provider review.

On mobile, verify that balance, total bet, feature state and help remain visible without overlap. On desktop, check that browser zoom does not hide a purchase control or change the apparent denomination. Mathematical configuration should not change merely because the screen changes; if the help shows another RTP, treat it as a different deployment and record it.

Keep a compact evidence record

For any fact used in a review, save the title, provider, official URL, document date when available, access date and exact territorial scope. For a live session, add the operator domain, Game ID, RTP, currency and a non-sensitive screenshot of the help panel. This makes later corrections possible when a supplier updates a sheet or an operator changes configuration.

Missing information should remain missing. Do not estimate an RTP from results, convert a euro reference range into an operator's NZD limit, or treat another casino's configuration as evidence. A transparent “not confirmed” is more useful than a precise-looking number without the correct source.

Use limits that survive the feature design

Collection meters, expanding grids, sticky symbols and near misses can make a session feel unfinished. Unless the rules explicitly preserve progress, the visible state has no value after the round or feature ends. Set a money limit and time limit before launch, count feature buys immediately, and stop at the limit even when a meter appears close to an upgrade.

No random game is an income plan. Do not borrow, use essential funds or raise the stake to recover a loss. If play stops feeling recreational, use timeout, deposit-limit or self-exclusion tools and consult the site's responsible gambling guide.