Repository navigation
Releases
Moonwell 0.19.1
Moonwell 0.19.1 fixes how a build warning that lists files reads in the moonwell tool's new output.
The full suite passes. No game check was needed: only the tool's output changed.
Fixed
- A warning with a list, such as the one for assets nothing in the map names, shows its message on its own, then each item on its own line. Before, the first path ran on at the end of the message and the rest followed with commas. Plain output (not a terminal) still puts each problem on one line.
Known
- Update the
moonwelltool withdotnet tool update -g Moonwell.Cli. - Big-area heights (0.15.1) are experimental: on one map, classic graphics drew the ground flat while trees and units followed the heights.
- Multiplayer is not checked yet, nor a game in another language.
Moonwell 0.19.0
Moonwell 0.19.0 makes the moonwell tool clear to read: a build shows a checklist of its steps with a spinner while each runs, problems read the same way whichever step found them, and moonwell run starts the game in borderless windowed mode, still running when you click away.
The full suite passes, and Moonwell's cases pass on .NET and in Lua, in development and release builds. moonwell run was checked in the game (3.0.1.24371): the new output in a terminal, the borderless window, and the game running on while another window had focus.
Changed
- The build's output is a checklist of its steps: Compile C#, Read objects, Compile to Lua, Pack the map. Each shows a spinner and a timer while it runs, then a tick or a cross with its time. Errors and warnings from
dotnet buildand from the Lua step read the same way, once each, under the step that found them, with the place and code on one line and the text under it.--verboseshows everything that's hidden. - Outside a terminal (CI, a redirected file, an editor's panel), the same checklist prints as plain text, one line per step as it ends, with no colours or spinner.
NO_COLORdoes the same in a terminal. moonwell runandwatch --runstart the game in borderless windowed mode, with-nowfpause, so the game keeps running when its window loses focus.
New
- Pick a command:
moonwellalone in a terminal shows a list of its commands to pick from, then asks what the picked one needs. moonwell mdx <model>shows a tree of the files a model uses (textures, replaceable textures, particle emitters' models, popcorn effects) and what those use in turn. Each file is marked as the game's, the map's own, both, or missing.
Known
- Update the
moonwelltool withdotnet tool update -g Moonwell.Cli. - Big-area heights (0.15.1) are experimental: on one map, classic graphics drew the ground flat while trees and units followed the heights.
- Multiplayer is not checked yet, nor a game in another language.
Moonwell 0.18.1
Moonwell 0.18.1 moves to CSharp.lua 2.0.4-moonwell.25, which fixes two ways the C#-to-Lua step got || and && wrong.
The full suite passes, and Moonwell's cases pass on .NET and in Lua, in development and release builds. No new game check was needed: it is a compiler fix, covered by a Lua case.
Fixed
- An
outvariable across a chain of||: ina.TryGetValue(k, out v) || b.TryGetValue(k, out v) || c.TryGetValue(k, out v), the Lua declared the flag twice, so the third call still ran after the second found a value and overwrote it. A chain of two worked before. - A
||or&&kept in abool: when it came out false, the variable held nil instead of false, so it printed as nothing and== falsedidn't match.
Known
- Big-area heights (0.15.1) are experimental: on one map, classic graphics drew the ground flat while trees and units followed the heights.
- Multiplayer is not checked yet, nor a game in another language.
Moonwell 0.18.0
Moonwell 0.18.0 adds rectangular level places to Moonwell.Procgen, for clearings and bases laid out on a grid, such as the map project's 32 by 32 tile colony.
The full suite passes, and Moonwell's cases pass on .NET and in Lua, in development and release builds. A square clearing in a forest was checked in the game (3.0.1.24371), in single player and classic graphics. Multiplayer checks are still to come.
New
- Rectangular places:
Level(Bounds area, blend)makes a level place the shape of a rectangle, so a region drawn in World Editor works too, andBounds.FromCentergives one by its size. It is kept level and free of trees and blocking, as a round place is. Its edge blends into the ground around it in an even band with rounded outer corners, while the level rectangle itself keeps sharp corners.PlacesandExitstay round.
Known
- Big-area heights (0.15.1) are experimental: on one map, classic graphics drew the ground flat while trees and units followed the heights.
- Multiplayer is not checked yet, nor a game in another language.
Moonwell 0.17.1
Moonwell 0.17.1 makes flat Procgen land load in less than half the time, fixes the guide's unit frame example, and gives new maps an .editorconfig.
The full suite passes, and Moonwell's cases pass on .NET and in Lua, in development and release builds. No new game check was needed: the changes are loading steps, the guide and the template.
Faster
- Flat land skips the heights work. With a biome's
LowestandHighestat 0,Makeno longer works out hills or fits wide craters that would all come out flat. Roads and level places are still cut, filled and levelled. A flat 480 by 480 land like the map project's takes 411 loading steps instead of 986: about 8 s instead of 20 s at 20 ms a step (measured in .NET).
Fixed
- The guide's
UnitFrameexample now places the frame at the left edge. At the top left, the game's top bar covered its name. The guide says which edges of the screen the game's HUD covers for frames added withScreen.Add, and thatAddOverdraws over them. Where a frame goes stays the map's choice.
New
- An
.editorconfigin the map template: a map made withmoonwell newordotnet newgets UTF-8, LF line endings and 4-space indents (2 for project and JSON files), and leaves the game's and World Editor's files inmap/as they were written.
Known
- Big-area heights (0.15.1) are experimental: on one map, classic graphics drew the ground flat while trees and units followed the heights.
- Multiplayer is not checked yet, nor a game in another language.
Moonwell 0.17.0
Moonwell 0.17.0 grows Moonwell.Frames and Moonwell.Kit for HUDs like the map project's WoW-style UI: textures cut, coloured and rounded by the build, labels with their own size and font, pixel layout, frames on the game's own HUD pieces and portrait, text that moves by itself, and Kit's HUD parts: unit frames, bars, action buttons, cast bars, buff rows and a list of the selected units. It includes 0.16.0's AI package.
The full suite passes, and Moonwell's cases pass on .NET and in Lua, in development and release builds. Each part was checked in the game (3.0.1.24371) in its own probe or check map, and the Kit parts and moving text together in one map, in single player and classic graphics. Multiplayer checks are still to come.
New
- Looks: a
.looks.csvbeside a texture lists copies the build makes of it: a piece (mirrored too), a colour, a round cut, and for bars 64 cut steps. Code reaches each by a typed name (image.Texture = Looks.UiTargetingFrame.PlayerFrame), so a wrong name is a compile error. A row with no texture of its name is a flat colour. AProgressBargiven a bar look cuts instead of squashing, andLooks.Round(path)gives a listed icon's round copy. - Labels:
Size,FontandShadow, read when a label is made, from text templates the build writes for the game's font and each.ttfin the assets.Scalesizes the text only and keeps its place.label.ShowNameOf(unit)shows each machine its own name for a unit. - Pixel layout:
frame.Add(child, x, y, width, height)places a child from its parent's top left, y down, inScreen.DesignHeightunits. - The game's HUD:
piece.Fill(frame)puts a moved HUD piece over a frame at its size.GameUi.Portrait.Fill(frame)places the game's moving portrait in a frame, fitted to the window's shape.Screen.AddTo(frame, gameFrame, scope)makes a frame that shows and hides with one of the game's. - Text that moves: an
EffectonLabelandFloatingText.TextEffect.Rainbow()turns the rainbow along the text, andTextEffect.Sweep(main, sweep, shape)passes a band. Moonwell redraws them on one shared timer until the effect is set to null or the text ends. - Kit's HUD parts:
UnitFrame(icon, name, level, life and mana bars, buffs),StatusBar.Follow(unit, Vital.Life),ActionButtonwith a hotkey, a count and a clockwise cooldown sweep,CastBarwithStartandInterrupt,BuffRowwith the icons the build reads from each buff's object data, andSelectionList.Follow(player). Each is laid out in the theme, and each piece is a frame of its own to place again or retexture. - Selection changed:
OnSelectionChanged(Player player)on game and player components, so a map no longer pollsSelection. - From 0.16.0:
Moonwell.AI,Moonwell.AI.CombatandMoonwell.Simulation, with 0.15.1's fixes.
Known
- The guide's
UnitFrameexample puts the frame at the top left, where the game's top bar covers its name. Place it lower until 0.17.1 fixes the example. - The game takes a label's font and height only from its template, so
Size,FontandShadoware read when a label is made. - A frame drawn under a game HUD frame that is a simple frame never shows, so
Screen.AddToshows it over the HUD and follows the game frame's visibility instead. - Big-area heights (0.15.1) are experimental: on one map, classic graphics drew the ground flat while trees and units followed the heights.
- Multiplayer is not checked yet, nor a game in another language.
Moonwell 0.16.0
Moonwell 0.16.0 adds Moonwell.AI, a base for AI that any map can use: brains for units, players and the game, a blackboard of facts, behaviour trees and utility AI that call each other, full control of a unit beside the game's own AI, development tools that show what a brain thinks, and a fast simulation in .NET to test AI code without the game. Moonwell.AI.Combat builds lane fighters on top of it. It also takes in 0.15.1.
The full suite passes, and Moonwell's cases pass on .NET and in Lua, in development and release builds. Each part was checked in the game (3.0.1.24371) in its own probe or check map, and all of it together in one map, in single player and classic graphics. Multiplayer checks are still to come.
New
- Brains:
UnitBrain,PlayerBrainandGameBrainare components that think on one shared 0.02 s loop and end with what they belong to. A brain's ownOrder,OrderAtandOrderOnreach the game only when they change. In the game's probes, 1,000 brains thinking every 0.25 s cost about 40 to 50 ms of Lua a game second; orders, not thinking, are the limit. - Facts:
Fact<T>is a typed key. A fact is written by any code or worked out when read, remembers when it was set, and is read up the chain from a unit's brain to its player's and the game's. A unit's brain reads its current owner's facts. - Behaviour trees: a
Treeper brain, built in C# from node helpers (using static Moonwell.AI.Nodes:Select,Sequence,When,MoveTo, ...). AWhenin aSelectis checked at every think and cuts in on a lower branch. Unit actions cover moving, attacking, casting, following a route and using items (Unit.UseItem,UseItemAt,UseItemOn, also new in core). A map's own node is a class inheritingNode, or aDo(...)one-liner. - Utility AI: a
ChoiceofOptions, each with an action, a weight and inputs through curves (Line,Power,S,Step,Points). The best score wins. An option's action can run a tree, and a tree can hold a choice. - Full control:
UnitBrain.FullControltakes a unit from the game. Orders the game or an AI script gives it, and a player's clicks, are answered with hold position, so only the brain's orders stand. Set it false, or end the brain, and the unit goes back to the game. The melee and campaign AI scripts stay natives, and the guide says how they meet brains. - AI tools, development builds only: the debug panel shows a brain's trees, its choices' scores and its facts (Ctrl + click a unit, or
-brain <class>).-brainlogwrites a decision log of what won, its score and the facts read.-force,-factand-wakesteer a brain from chat. A release build carries none of them. - Fast simulation:
Moonwell.Simulation, a package for a map's test project.Simulation.Start(map)runs the map's components outside the game, units walk, fight and cast at their type's numbers, andsim.Run(seconds)plays it faster than real time, the same each run from the same seed. - Combat:
Moonwell.AI.Combatgives a readyLaneWalkerbrain that walks a route, such as a Procgen road, fights what it meets and goes on. It picks targets by rules (Target.Nearest,Weakest,MostDangerous,Attackeror a map's own), casts its spells in priority order when their conditions hold, and pulls back when hurt or outnumbered, coming back when its reason is gone. Its tree is made of public combat nodes, so a map can build its own. - From 0.15.1: hills on a whole 480 by 480 area, no leak report for generated ground,
IsMadeafter a world ends, and text extensions in a packaged map.
Fixed
- A
Fact<T>declared in a file whose name sorts before Moonwell's ownFact.csno longer stops the script at load.
Known
- The game gives code no way to end a unit's chase, so the lane walker's leash is the only limit on how far it chases.
- The simulation plays orders, walking, attacks, cooldowns and mana, not spell effects or pathing.
- Big-area heights (0.15.1) are experimental: on one map, classic graphics drew the ground flat while trees and units followed the heights.
- Multiplayer is not checked yet, nor a game in another language.
Moonwell 0.15.1
Moonwell 0.15.1 fixes what a 480 by 480 map found in 0.15.0's Moonwell.Procgen: a whole map of that size can now be made with hills, a generated forest is no longer reported as a leak, and core's text extensions build in a map that uses the packages.
The full suite passes, and Moonwell's cases pass on .NET and in Lua, in development and release builds. It was checked in the game (3.0.1.24371) on a 480 by 480 map, in single player and classic graphics. Multiplayer checks are still to come.
Fixed
- Hills on a whole 480 by 480 map.
Makewith heights over a map that size stopped partway and play never came: the game slows as craters pile up, from about 10 µs a crater at first to over 500 µs at 85,000. An area of over 20,000 corners is now raised with one wide crater every 4 by 4 corners, fitted to the hills, and its tiles, blocking and trees follow the ground as made. A whole 480 by 480SnowyForestwith a road was made in 19 s at 20 ms a step. Smaller areas are made as before. - A making that stalls shows it. The heights step paces itself by the craters already held, so late steps stay near their budget, and a development build reports a step that takes over a second.
- No leak report for generated ground.
Make,Applyand growing worlds keep what they make out of the leak count, so a large forest no longer reports a leak at 500 trees and each doubling. A map's own scopes are still reported. IsMadeafter a world ends. Every chunk now readsIsMadefalse once its growing world has ended.- Text extensions in a packaged map.
"...".Rainbow()and core's other extension methods built in C# but failed in the Lua step of a map using the packages. Moonwell now uses CSharp.lua 2.0.4-moonwell.24, which fixes this.
Known
- A big area's hills are a little smoother than a small area's, and two big areas don't meet seamlessly. For more detail over a map that size, use a growing world (
Grow). - The minimap still shows the ground the map was saved with, not the generated land.
- Multiplayer is not checked yet, nor a game in another language.
Moonwell 0.15.0
Moonwell 0.15.0 grows Moonwell.Procgen from hills and tiles into whole worlds: trees, biomes, places and camps, roads with path data for units to follow, ground made in steps with progress to show, and growing worlds made chunk by chunk around the heroes. Tiles can be declared in code. A map on 0.13.4 builds on it, but the same seed gives other ground than before (below).
The full suite passes, and Moonwell's cases pass on .NET and in Lua, in development and release builds. Each part was checked in the game (3.0.1.24371) in its own probe, and all of it together in one map, in single player and classic graphics. Multiplayer checks are still to come. There is no 0.14.0 yet: that number is kept for the Frames and Kit work planned before this.
Changed
- Plans of one seed meet at their edges. Ground now follows the world, so two plans of one seed line up, and an area's ground depends on where it is. Heights stay between
LowestandHighestinstead of being stretched to each area's own range, and aLevelplace is level at the ground as it was. The same seed gives other ground than in 0.13.
New
- Ground in steps:
TerrainGenerator.Make(area, scope)makes the ground over frames and gives aTerrainMakingwithProgress,Step(its name) andDone, for a loading screen or a bar. Made in steps of 4 ms, no frame was longer than the game's own. - Trees:
Forest,WallandScatterrules, each limited by height, slope and tile. Trees are real destructables, cut for lumber and regrown, standing at the ground's height on generated hills.Destructable.Createtakes a height for a map's own trees. - Places and camps:
Levelgives aPlace;Places(...)picks spots from the seed with a difficulty by distance,Exit(...)one on a side, andplaces.Add(difficulty, types...)makes a camp or building group in each. - Roads and path data:
Road(a, b, width, through)cuts and fills a lane between two places at an easy slope, andJoin()links every place. Each road gives its points, width and length;road.Toward(place)gives it as aRouteeither way,Route(a, b)the way over the roads, androad.Outline(from, to)aPolygonfor an area along a stretch.Routemoved toMoonwell.Maths, same type and namespace. - Biomes and presets: a
Biomehas its own hill shape, tiles, trees and blocking;Use(biome, area)puts one in an area andMix(area, size, ...)several in patches, blended at the borders. PresetsGrassland,RockyHills,SnowyForestandDesertname their rules, so a map changes or removes them one by one. - Growing worlds:
Grow(area, scope)makes a world chunk by chunk near every living hero and takes chunks back when every hero is far, the same each time.MadeandTakingBackevents give each chunk and a scope for what the map makes in it. Units by new trees or blocked ground are moved out, and camps are made once and kept. - Tiles in code:
TilesonMap; the build adds the tiles the map lacks to its tile list, up to the game's 64.
Faster
- A grid
Blockwalks only its blocked corners, where it walked the whole area.
Known
- Each tree made and removed leaves about 5 KB and a handle id behind, so a growing world that remakes forests often grows the game; the guide gives the numbers.
- The game makes no cliffs, ramps or water while it runs, so generated ground is slopes and tiles.
- Multiplayer is not checked yet, nor a game in another language.
Moonwell 0.13.4
Moonwell 0.13.4 fixes what building a WoW-style UI on Moonwell.Frames ran into: the game's own HUD now stays the way a map leaves it, and the build stops the calls that crash the game on the HUD's texts and textures. A map on 0.13.3 builds on it unchanged, and its object data comes out the same.
The full suite passes, and Moonwell's cases pass on .NET and in Lua, in development and release builds. The GameUi changes were checked in the game (3.0.1.24371), in single player, in classic graphics. Multiplayer checks are still to come.
Fixed
GameUiholds with the HUD hidden:- command and item buttons take the game's frames they sit in along when they move, so nothing is left behind taking clicks;
- the hidden HUD hides the invisible frame that blocked clicks where the command card was, and turns the game's own placing off once a piece is moved;
- the hero buttons' glows stay hidden;
- item buttons show on their own, without the inventory's text and cover art;
- what the game shows again by itself, and after a letterboxed cinematic, is set again.
- Two builds of one map at once: a second build now waits for the first, where it crashed the build tool.
- A frame's parent and children can be read outside
Local.For(BlzFrameGetParent,BlzFrameGetChild,BlzFrameGetChildrenCount); two rules together refused them everywhere.
New
- The game's HUD as pieces:
SelectionIcons(the units selected together, movable),UnitDetails,UnitName(a unit's or building's name line),InventoryText,InventoryCoverandBuildQueue(a building's training queue, a click on a queued icon cancelling it), each with aVisiblethat holds. - MW0057: the build refuses the natives that crash the game when given one of its HUD's texts or textures found by name (
BlzFrameSetAlphaonSimpleNameValueand the like). The list of 117 names is read from the game's own frame files. Unit.Icon: a unit's icon, read on one machine (Local.For), as some units' icons differ between Classic and Reforged.unit.Default.Iconnow works on any unit.Game.LogAtOnce: a development build writes Moonwell's log at once on every line, so a crash to the desktop keeps the last lines. A busy map can turn it off; a release build can turn it on to hunt a crash.-framesin a development build writes the game's frame tree toCustomMapData\Moonwell\frames.txt.
Known
- A cinematic a map makes with the game's natives, not
Cinematic.Play, does not set the HUD again after it. - Multiplayer is not checked yet, nor a game in another language.