heroes.sourceforge.net

Cascadeur's site offers a free way to try the software and links to paid plans, but the public page does not spell out exactly what the free tier includes or where its limits sit. What it does confirm is the feature set — AI-assisted keyframe animation, AutoPosing, AutoPhysics, Ragdoll, Inbetweening, AI motion generation, rigging, retargeting, and UE Live Link — plus file compatibility with .FBX, .DAE, .GLB/.GLTF, and .USD. If you need a definitive free-vs-paid breakdown, treat the Plans page and the trial start as the two places to check, because the homepage itself doesn't publish export limits, watermark rules, or commercial-use terms.

What the public page actually tells you

The homepage positions Cascadeur as "the easiest way to animate" and invites you to "Try for free" or "Watch demo." It lists these capabilities without marking any as paid-only:

• Inbetweening — AI interpolation that generates motion between keyframes
• Ragdoll — procedural reactions to impacts, falls, and collisions
• AutoPosing — get natural poses by moving fewer control points
• Quadrupeds — rigging, AutoPosing, and one-click retargeting for four-legged animals
• AI Motion Generation — running, jumping, combat, acrobatics, idles, and more
• AutoPhysics — a character double showing a physically accurate result, for tuning secondary motion and inertia
• Rigging — drag-and-drop joints to auto-generate a rig for humanoids and quadrupeds
• Retargeting — copy/paste animation between characters regardless of skeleton or proportions
• UE Live Link — stream animation to Unreal Engine with real-time updates

It also names the solution areas: mocap cleanup, previz, animation editing, AI, video games, prototyping, and markerless mocap. Mocap cleanup is described as fixing foot sliding, knee pops, geometry penetration, poses via AutoPosing, weight via AutoPhysics, and edits via Animation Layers.

None of this is labeled "free" or "paid" on the page, so don't assume the list equals the free tier.

The two "free" paths are different things

The page shows two separate entry points, and mixing them up is the most common source of confusion:

The trial link points to cascadeur.com/plans#trial, which means trial terms live on the pricing page, not the homepage. If your decision depends on whether you can keep using it indefinitely at no cost, that answer has to come from the Plans page — the homepage doesn't provide it.

When the free route is likely enough

Based on the feature list alone, a free or trial route is worth starting with if you are:

• Learning the workflow — testing AutoPosing and Inbetweening on a simple humanoid before committing
• Evaluating mocap cleanup — checking whether the foot-sliding and knee-pop fixes fit your pipeline
• Prototyping — blocking previz or game animation without a production deadline
• Testing file compatibility — confirming your .FBX, .DAE, .GLB/.GLTF, or .USD assets import cleanly

When upgrading becomes the real question

Upgrade pressure usually comes from constraints the homepage doesn't state, so verify each against the Plans page before paying:

1. Export restrictions — if the free tier limits resolution, format, or adds a watermark, that alone can force an upgrade for client work.
2. Commercial use — confirm whether free-tier output can be used in shipped products. The page doesn't say.
3. Team or pipeline needs — UE Live Link and retargeting matter more in production; check whether they're gated.
4. Volume of work — a single test animation and a full game's combat set have very different tolerance for limits.

A concrete example: if you're cleaning up a markerless mocap take for a game prototype and the free route lets you fix foot sliding and apply AutoPhysics, you may never need to pay. If you're delivering that animation into a commercial build and the free tier restricts export or licensing, the upgrade decision is made for you by the terms, not the feature list.

How to decide without guessing

1. Open the Plans page and read the actual tier comparison — this is the only authoritative source in the material provided.
2. Start the trial and test the specific features your project needs: AutoPosing, AutoPhysics, Ragdoll, Inbetweening, retargeting, and UE Live Link.
3. Test an export end-to-end with your real file format (.FBX, .DAE, .GLB/.GLTF, or .USD) and inspect the output for watermarks or quality loss.
4. Check the commercial-use terms in writing before shipping anything.
5. Only then compare cost against the limits you actually hit.

The homepage is useful for understanding what Cascadeur does — AI-assisted keyframe animation for character work, mocap cleanup, and game pipelines. It is not a pricing document. For the free-vs-paid question specifically, the Plans page is the answer, and the trial is how you verify it against your own project.

Arx Libertatis is an improved, cross-platform, open-source engine for Arx Fatalis, the 2002 first-person RPG/dungeon crawler/immersive sim from Arkane Studios. To play on Linux, you install Arx Libertatis (official Linux builds are provided), then point it at a copy of the original Arx Fatalis game data — the engine itself does not include the game. You need to own or otherwise obtain Arx Fatalis or its demo before you can play.

What Arx Libertatis actually is

Arx Libertatis is a port and modernization of the Arx Fatalis engine, based on the publicly released Arx Fatalis source code and available under the GPL 3+ license. Version 1.2.1 supports modern systems, brings the game to new platforms, and removes bugs and limitations of the original release.

Two things follow from that:

• The engine is free and open source. You can download, inspect, and redistribute the code under the GPL.
• The game data is not included. The license covers the engine only. The art, audio, levels, and other assets remain part of the commercial game, so you must supply them yourself.

The game itself features crafting, melee and ranged combat, and a distinctive spellcasting system where you draw runes in real time to cast the spell you want.

What you need before installing

The original game is sold through storefronts such as GOG.com, the Microsoft Store, and the Bethesda Store, and it also has a demo. Any of these gives you the data files the engine needs.

Installing Arx Libertatis on Linux

Arx Libertatis provides official builds for Windows and Linux. Beyond those, it has been packaged for macOS (Homebrew), FreeBSD, DragonFly BSD, NetBSD, OpenBSD, Haiku, and Pandora, and will likely compile and work on other operating systems.

On Linux, you have two practical routes:

Option 1: Use a distribution package

Check whether your distribution ships Arx Libertatis in its repositories. If it does, install it through your normal package manager. This is the least manual path and keeps updates tied to your system.

Option 2: Use the official Linux build

Download the Linux build from the project's download page and unpack it. This works regardless of whether your distribution packages the engine, and it lets you run a specific version such as 1.2.1.

If neither fits, the source is available on GitHub, so you can build it yourself — the project notes it will likely compile on other systems too.

Pointing the engine at your game data

The engine needs to find the Arx Fatalis data files. The general flow is:

1. Install or unpack Arx Libertatis using one of the routes above.
2. Locate your Arx Fatalis data. If you bought the game from a storefront, the installer places the data files somewhere on disk; if you have the demo, it comes as its own set of files.
3. Tell Arx Libertatis where that data is when you first launch it, or place the data where the engine expects it.
4. Launch the game and confirm it reaches the main menu.

The expected result at each step is simple: the engine starts, finds the data, and loads the game rather than exiting with a "data not found" style error.

If the game does not run

Check these in order:

• Data path is wrong. The most common failure is the engine not finding the Arx Fatalis data. Re-check the path you gave it.
• You installed the engine but not the game. Arx Libertatis alone cannot run — it has no assets of its own.
• Graphics/driver problems. Since the engine targets modern systems, most rendering issues trace back to drivers or to running an old build. Try the current release (1.2.1).
• Wrong build for your system. Make sure you grabbed the Linux build, not the Windows one, if you installed manually.

Where to go next

The project plans to keep improving and modernizing the engine and to enable community customizations and mods. If you want to follow development or get help, the project links to its GitHub repository, Mod DB page, and community forums such as the TTLG Forum and the GOG.com forum. There are also community projects built around the game, including the Arx Insanity Mod and other Arx mods.

A Minecraft block palette works by grouping blocks whose colors sit close together in hue and value, then adding one or two contrasting blocks for accent. The goal is cohesion: from a distance the build reads as one intentional color story, and up close the textures keep it from looking flat. This applies whether you are planning a medieval village, a fantasy tower, or a modern house — the color logic stays the same, only the specific blocks change.

The Three Layers of Color in a Palette

Every block you place contributes on three separate axes. Mixing them up is the most common reason a palette looks "off" even when each block seems fine on its own.

• Hue — the actual color family: red, orange, yellow, green, blue, purple, or a neutral (gray, brown, black, white).
• Value — how light or dark the block is. Stone Bricks and Deepslate Bricks are both gray, but they sit at very different values.
• Texture — the surface pattern: smooth (Quartz, Smooth Stone), rough (Cobblestone, Gravel), or patterned (Chiseled Stone Bricks, Stripped Logs).

A palette that matches hue but ignores value tends to look muddy. A palette that matches value but ignores texture looks flat and artificial. Good palettes balance all three.

Warm, Cool, and Neutral Groupings

Sorting blocks by temperature is the fastest way to build a palette that feels deliberate.

When to use each: pick one temperature as your dominant group, then borrow from a second only for accents. A warm oak-and-brick house with a few cool stone accents reads clearly. A build that splits 50/50 between warm and cool usually reads as indecisive.

Contrast and Accents Without the Noise

Contrast is what makes a palette readable, but too much of it creates visual noise. A workable rule:

1. Base (60–70%) — the dominant block or two, usually your largest surfaces: walls, floors, roofs.
2. Secondary (20–30%) — a related block that adds value variation, like a darker wood for framing or a lighter stone for trim.
3. Accent (5–10%) — one block that clearly stands out: a bright color, a metal, or a strong texture. This is where a single pop of color earns its place.

If you find yourself wanting four or five accent blocks, that is usually a sign the base palette is too weak, not that you need more accents.

Matching Palette Colors to Build Styles

The same color principles apply differently depending on the style you are aiming for.

• Medieval — warm, low-saturation, textured. Oak, Spruce, Cobblestone, Bricks, and Terracotta. Accents are often dark wood or iron.
• Fantasy — higher contrast and more unusual hues. Deepslate, Purpur, Prismarine, Warped/Crimson stems. Accents can be bold and magical-feeling.
• Modern — neutral and cool, with smooth textures. White and Gray Concrete, Quartz, Smooth Stone, Glass. Accents are minimal and often structural rather than colorful.
• Farm / rustic — warm and earthy, with rough textures. Oak, Hay, Dirt paths, Coarse Dirt, Spruce.

Notice that style is mostly a choice of temperature plus texture, not a fixed block list. You can build a convincing modern house in warm tones if you keep the textures smooth and the contrast controlled.

Testing a Palette Before You Commit

You do not need to build the whole structure to know whether a palette works. A few low-cost checks:

• Build a small test wall — a 5×5 or 7×7 patch using your base, secondary, and accent blocks in the proportions you plan to use. Step back and look at it from a distance.
• Check it in different light — daylight, torchlight, and night change how colors read. A palette that looks great at noon can go flat at night.
• Squint or zoom out — if the build turns into a single blurry mass, your value contrast is too low. If it looks patchy and busy, you have too many competing accents.
• Swap one block at a time — change only the accent or only the secondary, and compare. This isolates what is actually causing a problem.

Sites like Block Palettes collect community-submitted palettes and feature a rotating set handpicked by staff, which makes them useful as a starting reference when you want to see how other builders combine colors before testing your own. You can browse featured palettes for inspiration, then recreate a small test patch in-game to see how the colors behave in your own lighting and build context.

A Quick Decision Path

If you are unsure where to start:

1. Choose the style you are building (medieval, fantasy, modern, farm).
2. Pick a temperature that matches that style.
3. Select two base blocks in that temperature at different values.
4. Add one secondary for framing or trim.
5. Add one accent — and only one to start.
6. Test a small patch before scaling up.

Once the small patch reads clearly, the full build almost always will too.

Yes. CC0 assets can be used in commercial games without paying royalties or crediting the creator. CC0 is a public-domain dedication: the creator has waived copyright and related rights to the fullest extent allowed by law. That means you can copy, modify, redistribute, and sell work built on those assets — including in a game you charge money for.

This article explains what CC0 actually covers, how it differs from other Creative Commons licenses, and how to bring CC0 assets into engines like Unreal and Unity and tools like Blender, Maya, and 3ds Max.

What CC0 actually means

CC0 is not a license in the traditional sense — it is a waiver. When a creator applies CC0 to their work, they give up their copyright and agree not to enforce related rights. You are free to:

• Use the asset in personal, educational, or commercial projects
• Modify, remix, and build derivative works
• Distribute the asset or your derivative as part of a larger project
• Do all of the above without attribution

There is no requirement to credit the creator, no share-alike clause forcing you to open-source your game, and no non-commercial restriction. For a studio shipping a paid title, that combination is unusually permissive.

One practical caveat: CC0 applies to the rights the creator holds. It cannot waive third-party rights the creator never owned. A scanned statue, a branded product, or a recognizable logo in a texture may still carry trademark or personality-rights issues. Treat CC0 as clearing copyright, not as clearing everything.

CC0 vs. other Creative Commons licenses

The differences matter most when you are choosing assets for a commercial build. The table below summarizes the common variants.

| License | Commercial use | Attribution required | Share-alike | Notes for games | |---|---|---|---|---|---| | CC0 | Yes | No | No | Closest to public domain; safest for closed-source commercial titles | | CC BY | Yes | Yes | No | Fine for commercial use, but you must credit — plan for a credits screen | | CC BY-SA | Yes | Yes | Yes | Derivatives may need to be shared under the same license; risky for proprietary code/assets | | CC BY-NC | No | Yes | No | Excludes commercial projects; avoid for any monetized game | | CC BY-ND | Yes | Yes | No | No derivatives — you cannot modify the asset, which limits integration |

If your goal is a commercial game with no legal overhead, CC0 is the simplest choice. CC BY is workable if you can maintain attribution. Avoid NC and ND for anything you intend to sell or heavily adapt.

How CC0 assets fit into game engines and pipelines

CC0 libraries typically provide HDRIs, PBR textures, and 3D models. Each type has a natural place in a game pipeline.

HDRIs

HDRIs are high-dynamic-range environment maps. In Unreal, they are commonly used for sky lighting via a Sky Light set to use an HDRI cubemap or a Sky Sphere material. In Unity, they feed the skybox and the environment lighting in the Lighting window. You can also use them as reflection probes or as the basis for image-based lighting in Blender, Maya, or 3ds Max for look development before export.

Textures

PBR texture sets usually ship as albedo (base color), roughness, metallic, normal, and sometimes ambient occlusion or height maps. These drop directly into Unreal's material system or Unity's Standard/URP/HDRP shaders. Keep the resolution appropriate: 4K textures are useful for hero assets, but 1K or 2K is often enough for background props and saves memory.

Models

Static meshes and props can be imported as FBX or OBJ. Check the scale and pivot before placing them in a level. If the asset was authored for offline rendering, it may have very high poly counts — decimate or LOD it before use in a real-time scene.

Practical steps for importing and adapting assets

1. Download and verify the license. Confirm the asset page states CC0. Save a screenshot or the license text alongside the file.
2. Organize by type. Keep HDRIs, textures, and models in separate folders. A consistent naming convention (for example, env_forest_01_4k.hdr) saves time later.
3. Import into your engine. In Unreal, drag the FBX into the Content Browser and set up materials. In Unity, import the FBX and assign a PBR material, then wire the texture maps to the correct slots.
4. Adapt scale and orientation. Real-world assets may be authored in meters or centimeters. Check against a reference cube of known size.
5. Optimize. Reduce texture resolution where it will not be seen up close, generate LODs for models, and bake lighting where appropriate.
6. Test in context. Place the asset in a representative scene and check lighting, reflections, and performance before committing it to the project.

What CC0 does not cover

CC0 clears copyright, but a few things still deserve a second look:

• Trademarks and logos. A texture containing a recognizable brand mark is not automatically safe to ship.
• Recognizable people or property. A model of a real person or a distinctive building may raise personality or property-rights questions.
• Third-party content inside the asset. If a creator included someone else's work without permission, the CC0 dedication does not fix that.

For most generic assets — rocks, foliage, generic furniture, abstract HDRIs — these concerns are minimal. For anything depicting a real brand, person, or landmark, verify independently.

Documenting asset sources for teams and clients

Even though CC0 requires no attribution, keeping records is good practice. It protects you if a client or publisher asks for provenance, and it helps when a team member needs to know where a file came from.

A simple tracking sheet works:

Store this alongside your project files. If you later combine CC0 assets with CC BY assets, the sheet makes it obvious which ones need credit.

Bottom line

CC0 assets are safe for commercial games, require no attribution, and impose no royalties or share-alike obligations. The main work is practical: verify the license, check for third-party rights, import and optimize the asset for your engine, and keep a record of where it came from. Do that, and a CC0 library becomes a legitimate, low-friction source for production assets in Unreal, Unity, Blender, Maya, and 3ds Max.

A quest in AdventureQuest is a self-contained piece of playable content — a story mission, class trial, daily task, or limited-time event — that you start from a quest giver or menu, work through (usually by fighting monsters or solving a puzzle), and finish for a reward such as gold, experience, items, or Z-Tokens. You can complete most quests solo at any level the quest allows, but some are gated behind level requirements, prerequisite quests, or a limited-time window. This guide covers how quests differ from other content, the main types, the basic completion loop, and where to find what's new.

What counts as a "quest" in AdventureQuest

AdventureQuest is described on battleon.com as "an ever-expanding RPG with two decades' worth of adventures," and quests are the unit that content is delivered in. A few distinctions matter when you're deciding what to click on:

• Quests are playable objectives with a start and an end. They advance a story, unlock a class, or hand over loot.
• Events are time-limited quest lines tied to a real-world occasion — for example, the site's "Talk Like a Pirate Day Event," which sends you aboard the ship Red Betty to take Captain Rhubarb's Pirate Quiz and, if you pass, opens access to the Pirate Scholar Shop.
• Shops are where you spend what quests earn you. The Pirate Scholar Shop is a reward destination, not a quest itself.
• Story chapters are longer arcs made of many individual quests played in sequence.

So "quest" is the core gameplay loop; events, shops, and story chapters are the containers and payoffs around it.

The main types of quests

The site's news for the week of September 21, 2026 shows how these overlap: a 20K Z-Token package (CropStalker gear), a returning Fall Seasonal shop with the Lantern of the Equinox, and a 50K Z-Token Zombie Hunter set with an armor, three weapons, a shield, and a title. These are shop and package content — the quests attached to them are how you earn or unlock the pieces.

The basic completion loop

Every quest follows roughly the same shape, whether it's a five-minute daily or a multi-part story mission:

1. Find it. Quests are surfaced through the game's quest menu, a quest-giving NPC, or the in-game news feed. New weekly content is announced on the site's news section and explained in the Design Notes.
2. Check the gate. Before you commit, confirm you meet any level requirement and that you've finished the prerequisite quest. Event quests also have a date window — the Pirate Day event, for example, is only live while the event runs.
3. Accept and start. Selecting the quest loads its map or encounter.
4. Play it out. Most quests are combat: fight the monsters in the area, sometimes in a set order. Others are puzzles or quizzes — the Pirate Quiz is a knowledge check rather than a fight.
5. Turn in. Return to the quest giver or hit the completion prompt.
6. Collect. Rewards land in your inventory or account. Event quests often unlock a shop rather than handing over the item directly.

Common blockers and how to get past them

• Level requirements. Higher-tier quests and class training won't open until you've leveled. Grind earlier quests or dailies first.
• Prerequisite quests. Story arcs are sequential — if a quest won't start, you've usually missed an earlier step in the chain.
• Limited-time windows. Event quests like the Pirate Day content disappear when the event ends. If you want the reward, do it while the news post is current.
• Difficulty spikes. Some event quests are explicitly hard. The site warns that for the Pirate Day loot, "only those forged of the strongest mettle shall lay claim to these special spoils" — so bring appropriate gear and healing items.
• Not knowing what's new. This is the most avoidable blocker: check the news section and Design Notes each week so you don't miss a quest before its window closes.

Where to find new quests

The reliable sources, all reachable from battleon.com:

• Game News — weekly posts announcing what's live, like the September 21, 2026 "COMING THIS WEEK!" entry.
• Design Notes — the developers' explanation of new content, listed in the site's game navigation.
• Events — the dedicated section for time-limited quest lines.
• The Artix Game Launcher — the site promotes it as the way to get into the games, so it's the practical starting point for launching AdventureQuest and seeing current content.

If you're new, start with the main story quests to build level and gear, then branch into class quests and dailies, and treat event quests as time-sensitive bonuses you check for every week.