github ProjectReclaimer/project-reclaimer-releases v0.10.8

one hour ago

0.10.8 fixes crashes and hangs: Forge maps whose part has no model loaded, whose palette is past the engine's memory or that are too big to load, a ray in Havok's collision that never finished, a dedicated server whose map fails to load, a settings file with a setting this version does not know, a Forge AI whose animation is not loaded, and a Halo 3 canvas started in the wrong game. It also fixes the Flood infection, the teleport flash and Halo 2 and CE missions for co-op guests, Linux fonts and Discord status, film videos and Theater exports, lobbies, parties and rejoining, and server health and RCON scores.

Changes since v0.10.7.

What's new

  • Settings, Communication: Talk keys in menus. Choose whether your talk keys still talk while a menu is open: On (the default, as before), Keyboard only (keyboard keys and mouse buttons the menus don't use; never controller buttons) or Off.

  • Servers: the hit check logs and no longer removes players unless a server turns that on. The hit check now logs and reports what it finds and no longer removes players by itself, on dedicated servers and when you host a game. The rest of the anti-cheat works as before. A dedicated server's new anti_cheat_hits setting (off, detect, enforce; detect when unset) turns removal back on with enforce. anti_cheat = "off" turns both off. A change applies from the next game after a reload.

  • Forge AI spawners: AI color. An AI spawner's AI color gives its AI's armor or body one of the team colors, where the body has a color to change. Its own keeps the character's.

  • Forge AI spawners: damage, speed, difficulty, skull rules and several AI from one spawner. More settings on an AI spawner's Properties in the Forge menu and in the Reclaimer Kit:

    • Number alive: one spawner keeps up to eight AI alive at once.
    • Lives each round: how many AI the spawner places in a round, or
      unlimited.
    • Damage: 25% to 500% of what the AI's weapons, grenades and blows do.
    • Speed: 50% to 200%.
    • Difficulty: Easy, Heroic or Legendary for this spawner's AI, as
      their characters play on that difficulty in a mission.
    • Tough Luck skull and Catch skull: this spawner's AI play by the
      skull's rule.
    • Uses teleporters: an AI on foot that walks into a teleporter that
      takes players comes out of its receiver.
    • Takes empty vehicles: the AI walks to an empty vehicle nearby and
      gets in without waiting for a player to board first.

    Joined players see AI sizes, speeds and shield recharge as the host has them.

  • Forge AI spawners: recharge, camouflage, size, grenades and more. An AI spawner's Properties in the Forge menu, and its rows in the Reclaimer Kit, have new settings:

    • Shield recharge: its own, never, slow, fast or instant.
    • Armor regenerates: a Brute's broken power armor comes back like a
      shield.
    • Active camouflage.
    • Size: 50% to 300%.
    • Grenades: its own, none, or frag, plasma, spike or firebomb.
    • Always knows where players are: the AI keeps track of players it has
      noticed and goes after them.
    • Starts berserk: for Brutes.
    • Joins its killer's team: after a player kills it, it comes back on
      that player's team, every time or the first time only, until the round ends.
    • Wanders without a route: with nobody to fight, it walks about the
      range it may move in.
  • Forge: new objects can be made at the crosshair when the room search finds none (Experimental, off). A new Forge setting, forge.grab.create_at_crosshair (Experimental, off by default, as Halo 3): when the search for room cannot place a new object, which a large object such as a wide Shield Door can cause even in open air, or would place it past the level, the object is made at the crosshair instead. A kind at its limit, and a create with no point given, are still refused.

  • Servers log a player's join that stops making progress, and can ask that player to join again. A player whose game is joining a server's running game and makes no progress for 20 seconds is now noted in the server's log, with what the join is waiting on, so a host can tell why players are dropped while loading into a game. With the new setting rejoin_stalled_joins (off by default; in [defaults] or a server's section), after 45 seconds without progress the server asks that player's game to join again, which it does by itself into the game in progress, instead of the player being dropped back to the menus when the game's own three-minute limit runs out.

  • Reclaimer Kit: Pivot Point. The viewport header has a Pivot Point menu beside Transform Orientation, as in Blender: Median Point (as before), Individual Origins, Active Element and 3D Cursor. With Individual Origins each selected object turns and is resized where it stands, so with Local orientation several objects each turn about their own axis in place.

  • Split-screen players choose their own characters. Every saved player on your PC now keeps their own order of looks and their own character, armour and colours of each customization mod, beside the name, service tag, armour and per-game looks they already had. Open Customize, pick a player's tab and set up their looks: nothing changes for the other players. In a game each split-screen player plays the character they chose, and everyone online sees it. Before, every player on a PC shared player 1's choices and the other players always played Halo 3's own Spartan or Elite. Which mods are turned on or off stays one choice for the whole PC.

  • Theater: an MP4 export shows how far it is and how long is left. While EXPORT MP4 plays a film, the badge in the top right says EXPORTING with the percent done, the time left and the key that stops it (the one Record video is bound to; the video keeps what it has), with a bar along its foot, as in Project Reclaimer 0.9.

Changed

  • Server browser marks where a server was found with a symbol. Each row shows a small symbol in place of the THIS PC, LAN and INTERNET tags: a screen for this PC, linked machines for your network and a globe for the internet. Point at it to read every way the server answered. Long server names leave more room for the map and the game type.

  • Joining a server whose mods you already have goes straight in. The required mods window no longer opens with ACCEPT & JOIN when every mod the server uses is already on this PC. It still opens when something has to be downloaded or enabled, or for a customization mod you have not chosen about yet.

  • Reclaimer Kit: Local orientation turns and resizes each object on its own. Choosing Local as the Transform Orientation now also sets the Pivot Point to Individual Origins, so several selected objects are each scaled and turned where they stand instead of spreading from the middle of the selection. Choosing Global sets it back to Median Point, and the Pivot Point menu still picks any other.

  • Windows and Linux x86-64 builds run on every 64-bit processor again. The Windows and Linux x86-64 packages no longer need a processor with SSE4.2, so the game, the dedicated server, the Kit, the customization editor and the bot start again on older processors such as an Intel Core 2 or an AMD Phenom II. Newer processors lose nothing that was measured: the game still uses their newer instructions where it gains from them, chosen as it runs.

  • The loading screen shows from the start's first frame. The game's window no longer stays black on a first start. As soon as it opens it shows the logo and LOADING, with a line saying what is under way (starting the engine, or loading the menus' scenery), and keeps showing it until the engine takes over. The maps' list is read behind that screen, so a start with many mod maps no longer sits in an empty window while it reads them. The asset library's build also says that the next starts skip it.

Fixed

  • Linux on ARM64: the game starts on systems that give programs 48-bit addresses. On most ARM64 Linux systems (Steam Frame and other Snapdragon devices, and the usual distributions' kernels), 0.10.2 stopped before the menu with "Halo 3 could not be made ready for this computer". The game now accepts the higher memory addresses these systems use. Helmet fire colors, which looked for memory the same way, work there too.

  • Talk keys in menus: a setting to keep a talk button silent while you move through a menu. A controller talk button on the D-pad (or any talk key) talks while the game menu, Settings, the lobby, a pinned scoreboard or Forge's menu has your input, so moving down a menu can broadcast your microphone. Settings > Communication > Talk keys in menus can now keep new presses silent there (Off), or let only keyboard keys and mouse buttons the menus don't use talk (Keyboard only). It is On by default, as before. Whatever it says, what was talking as a menu opened goes on: a held key until you let go, and a mic you toggled on stays on. In split screen, another player's menu leaves your talk key working.

  • Split screen: another player's controller no longer presses your talk button. While a split-screen player moved through their own menu with a controller, their presses could also press the first player's talk button on the same button and send the first player's voice. Now only the first player's own controller counts for their talk keys while another player's menu is open.

  • AI spawners no longer crash on Ultimate Forge 2.0's maps. Placing a Brute Chieftain or jump-pack Brute AI spawner on one of the Ultimate Forge 2.0 mod's maps crashed the game, and the Brute, Brute Captain, Brute Stalker, Grunt, Drone and several Flood and Elite spawners made no AI there. The mod's maps carry incomplete copies of those characters' animations; the spawners now bring the complete ones from the campaign.

  • Every AI spawner makes its AI on Ultimate Forge 2.0's maps. The Marine, Marine Sergeant, Jackal, Jackal Sniper and Elite AI spawners placed on the Ultimate Forge 2.0 mod's maps but made no AI: the mod's maps carry copies of those characters that the maps never load. The spawners now bring the campaign's, as the Brutes and Grunts already do.

  • The game starts on ARM64 Linux again. On ARM64 Linux (handhelds and boards such as the Retroid Pocket 6) the game stopped at every start with "Halo 3 could not be made ready for this computer", right after it had made the engine's code. It starts there again.

  • Big games: players in view no longer slide frozen on a PC that holds a frame limit. In a multiplayer game of more than 16 players, a PC running at a frame limit (the default) was taken for one that cannot keep up as soon as a game tick took a quarter of its time. It then stopped simulating other players and vehicles more than a few steps away, also the ones in view: they slid along in a frozen pose, drivers and passengers too. The time the game waits for its next frame no longer counts as work, so a PC with time to spare simulates everyone again, and one that really falls behind still sheds the players it cannot see first.

  • Campaign canvases: a game type other than Forge on a bare canvas is refused instead of crashing the game. Starting Slayer (or any game type but Forge) on a Halo 3 campaign canvas with no map saved on it crashed the game as the game started. The lobby now says that the canvas plays Forge only: build it in Forge and save the map, then play other game types on the saved map. Forge on a canvas, games on maps saved from one, and ODST's canvases are unchanged.

  • Halo: CE's opening shows the bridge as soon as it fades in. In The Pillar of Autumn's opening cutscene, the first shot of the bridge (Captain Keyes at the window) stayed black for about two seconds after the cut from space, because its camera starts just outside the level and the game drew it from the wrong part of the ship. Cameras outside the level are now drawn as the original game draws them, so the bridge fades in at once.

  • Halo: CE infection forms no longer block the player. Infection forms stood in the player's way as solid bodies. As in Halo: CE, the player now runs through them, and they through him and one another.

  • Halo: CE characters walk and run at CE's pace. Marines, crewmen and the other characters of Halo: CE's missions played their walk and run a fifth slower than in CE, so they covered less ground: in The Pillar of Autumn's opening the Marines running past the camera stopped short, in the camera's path, and the shot showed an empty deck. They now move at CE's pace, and the Marines run into the shot and line up in front of the camera.

  • Halo: CE cutscenes pause between lines as in the original. A character's next line in a Halo: Combat Evolved cutscene waited only as long as the line before it, so lines ran into each other with no pause and could start over the end of the one before (Sgt. Johnson's speech in The Pillar of Autumn's opening). Each line now waits as long as the original game waits for it.

  • Halo: CE characters no longer cut off their own lines. When a Halo: Combat Evolved cutscene started a character's next line while their last one was still playing, the last one was cut off mid-sentence (the cryo technicians in The Pillar of Autumn's opening, and scenes in The Truth and Reconciliation, The Silent Cartographer, 343 Guilty Spark, Two Betrayals and The Maw). Both lines now play out, as in the original game.

  • Halo: CE infection forms pop on your shield and latch on without it. On The Library and every Flood level, an infection form that reaches a shielded player now pops against the shield, dealing its small hit once and dying, as in Halo: CE; before, the forms stood beside the player and struck the shield again and again without dying. With the shield down, a form latches onto the player and bites until it is killed.

  • Halo: CE shotguns hit with their own 15 pellets. Each pellet of Halo: CE's shotgun struck many times over, so one shot from a shotgun-carrying Flood combat form could kill the player from full health on Normal. A shot now hits with at most its 15 pellets, as in Halo: CE; the player's own shotgun is fixed too.

  • Halo: CE's space cutscenes show the sky from their first frame. The Pillar of Autumn's opening showed the ring alone on black for its first shots, the planet, stars and nebula appearing only some seconds later; the lifeboat's escape and The Maw's ending lost their sky in the same way whenever only the ring or the ships were in sight. The sky is now drawn in every shot, as in the original game.

  • Co-op guests: an infection form that bursts shows its death effect. In host-authoritative campaign co-op, an infection form the host kills now bursts with its effect on a guest too; before, a guest saw the form vanish without it. Multiplayer is unchanged.

  • Co-op guests see the checkpoint notice and the teleport effect. In host-authoritative co-op a guest now sees the host's "Checkpoint... done" notice, and the effect as a player is placed or brought to a teammate, as the host and Halo 3 show them.

  • Co-op guests see marines turn when the Flood infects them. In host-authoritative co-op a guest now sees a marine bend over as an infection form takes it, and hears the form's bite and, most of the time, its pop, as the host does. Older builds can't join such a game: the co-op messages changed.

  • The Maw's engine room and Warthog run no longer slow to a crawl. Halo: CE's lens flares were tested one at a time, each test making the graphics card set the whole picture aside and pick it up again. Where a level holds hundreds of flares, as The Maw's engine room and its closing Warthog run do, the frame rate fell to a fraction of the rest of the mission's. The flares are now tested together, as Halo: CE tests them, and look the same.

  • A player dropped from a server's game again soon after rejoining is asked before joining once more. A player whose game falls out of a server's game joins it again by itself once, after a short random wait, so that many players dropped at once do not all come back in the same second. If the game falls out again within five minutes of that rejoin, the main menu asks whether to join the server again instead of trying by itself, so a struggling server is not joined over and over. Lobbies hosted by a friend are told apart from servers only once every player of the lobby is known.

  • Theater videos: a recording that ends while it holds the film gives its speed back. A film video that ended while the film waited for the encoder no longer leaves that speed behind: the film plays on at its own speed, and the next film watched or exported is not set to it.

  • A failed copy of the old player folder no longer resets the profile for good. When the first start could not copy the 0.9 player folder (a file in use, an old cache Windows would not let go of), the game started with a new profile and never looked at the old folder again. Now a file that will not copy is left out and tried again at the next start, a failed copy is tried again, and players already reset by 0.10.1 or 0.10.2 get their profile, settings and files back once; the new profile made in their place is kept in a folder of its own, never deleted.

  • Forge: a spawned AI whose animation graph has a resource that is not resident no longer crashes the game (it plays without those animations).

  • Forge games with many object sources no longer crash while the map loads. Hosting Forge with several games' objects and mods turned on (for example Halo 3: ODST, Halo: Reach, Halo 2 and a few Workshop map packs) could need more memory for the map's content than the game has. The map then loaded without any of it and the game crashed, at once or on its first moment of play. Now the palette leaves out the objects your saved map does not place until the content fits, and says so: "N objects of X left out: the map's content fills the engine's memory (needed of room)". Objects your saved map places are never left out; if those alone do not fit, the game does not start and tells you how much it needs and which maps it took the most from, so you can turn off a source the map does not use.

  • A Forge map no longer crashes when an object's model is not loaded. On some saved Forge maps, mostly those brought from an older build onto a mod map, the game could close with a crash a few seconds or several minutes into the game. When an object's model is not loaded, the game now leaves that object out of the picture and writes the object's name in the log.

  • A shielded object whose model is not loaded no longer crashes the game. The fix for objects whose model is not loaded now covers the shimmer drawn over a shielded object when it is hit, and a model that came without the pieces that draw it. The log now names each such object once, up to four.

  • Forge no longer freezes after placing objects on maps with AI. On a Forge map with an AI spawner, the host's game stopped for a moment about a second after every object was placed, moved or deleted, while the ground the AI walk on was worked out again. The pause grew with the map: barely noticeable on an empty map, several seconds on one with thousands of objects. That work now happens in the background, so the game keeps running smoothly while you build; the AI use the new ground a moment later. Placing the first AI spawner in a running game no longer pauses it either.

  • A Forge game too big for the game's memory stops with a message instead of crashing. A hosted Forge game with many object sources turned on (other games' objects and several mods) could merge more content than the game's memory holds for one map. The game then loaded the map without that content and crashed as it started. Now the game does not start and says why: "The game could not start: the map's content needs N MB of memory and the engine has room for M MB", which sources its objects come from (to turn some off in the lobby and start again), and, on a PC whose map memory pool setting is smaller than the default, that setting. The program closes after the message. A dedicated server marks that game as unplayable, says why in its log, goes on to the next game in its list and does not draw that game again.

  • Forge on Halo 2 maps picks up the map's own crates. In Forge on a Halo 2 map, the fusion coils, drums, crates, pallets and other loose objects the map itself places could not be selected, moved or deleted, and were missing from the object list. They are Forge objects now, on Halo 2's maps and wherever Halo 2's objects are turned on. The energy sword, sniper ammunition and teleporters a Halo 2 map places can be selected too. The level's fixed scenery, doors and machines still cannot.

  • A server's health check fails while its game is down or crash-looping. dedicated status (Docker's health check) said a server was healthy ("lobby · 0/32 players") while its game had crashed and the supervisor was waiting to start it again, even through many crashes in a row, because the game's last status stayed fresh for a while. It now fails with a plain reason while no game is running, and after three crashes in a row until a game has run for two minutes. A normal next game or an empty server's restart does not count as a crash.

  • Host Settings: Player votes can be turned off again. Hosting a game from Host Game, players could always call votes (kick, end the round or the game, shuffle the teams), with no way to turn them off as Reclaimer 0.9 allowed. Host Settings has a Player votes switch again: on by default; off, no one can call a vote, and the host and their admins still kick and ban from chat.

  • A player still loading a big map is never taken for a stalled join. The server's watch on joins into a running game now counts a player's map load as progress, so a slow first load of a large mod map is not logged as a stall or asked to join again. A load that stops moving is logged as "still loading the map" and is never asked to join again, because that would start the load over. A player the server asked to join again is not asked again for ten minutes, in the following games too.

  • Spawn points added in the Reclaimer Kit show their team's colour. A spawn point dragged into a map in the Reclaimer Kit kept the marker's own blue whatever its team, while the map's own spawn points showed their teams' colours. Added spawn points now show their team's colour, grey for no team, and change as soon as the team does. The same holds for Halo: Reach's spawn points and its other team-coloured objects added in the Kit.

  • Reclaimer Kit: Blender JMS files import as exported, and a lone plane is refused instead of crashing. Import Tags read JMS files written by Blender's Halo exporters a line off (their vertices carry a colour the Kit didn't expect): a plane came in with scrambled geometry, and a re-exported model could fail with "JMS VERTICES: a count below zero". They now read as exported, and a file the Kit can't read says which section and line went wrong. A model whose collision would collide with nothing (a lone flat plane, or triangles without area) is refused with what to change in Blender: weld with Merge by Distance and give the collision a closed shape, or end the material's name with % to make a flat surface two-sided.

  • Copying text works in the Reclaimer Kit. Nothing copied in the Reclaimer Kit reached the clipboard: text copied from a field (a transform's values, a name) could not be pasted anywhere, and the Preferences window's "Copy Claude Code command" and "Copy address and token" buttons copied nothing. Copying now works in every field and button of the Kit and in the console over a played map.

  • Halo: CE levels full of lens flares take less processor time. Where the graphics card already tells the game whether each lens flare is hidden, the game no longer also traces a line through the level for every flare in view each tick. In The Maw's Warthog run that cost about a third of the game's time a tick.

  • Linux: the HUD's text shows with a game folder Windows installed, and the menus' font fits as on Windows. On Linux, a Master Chief Collection folder installed by Steam on Windows (a shared library on a Windows partition, or a copied folder) left the game without its text font: the HUD showed its icons but no numbers, names or messages. The game now finds MCC's font files whatever case their folders are spelled in.

    The menus use Bahnschrift, a Windows font, where the PC has it: now also from the Windows partition of a PC that runs both, or from fonts installed in a subfolder. Without it, the menus' built-in replacement is now drawn at Bahnschrift's size, spacing and line height, so labels fit and line up as they do on Windows.

  • Linux: MCC's saved maps and game types, Discord Canary and Vesktop, and alerts on KDE. On Linux the game now finds what the Windows game finds:

    • the maps and game types saved in MCC itself, which MCC under Proton keeps
      inside its prefix;
    • the Discord status with Discord Canary or PTB from Flatpak, or Vesktop;
    • Steam installed as a Snap.

    Its error alerts and folder windows also use KDE's kdialog when zenity is missing, so a fatal error still says why on a KDE desktop.

  • Long map and game type names no longer overlap on the loading screen. A map or game type name too long for its side of the loading screen's title card is drawn smaller, and past that on two lines, ending in "…" only when even two lines cannot hold it, so it never runs into the other name or off the screen. The creator's name and the line over each name end in "…" at their side's edge. Short names look exactly as before, and the picture and the rest of the card stay where they were.

  • Names with a line break or a tab stay on one line on the loading screen. A map, game type or creator name with a line break, a tab, a carriage return or another control character in it (from a server's listing, a host's lobby or a mod) is shown on one line on the map loading screen: each such break, or a run of them, shows as one space. A line break no longer draws a second line over the rest of the title card, a tab is no longer as wide as four spaces, and a carriage return no longer joins the words on either side of it.

  • Leaving a lobby that is still being created stops its work at once. A Forge lobby with other games' objects can take minutes to create. LEAVE LOBBY used to let that work run to its end, and hosting again (even the same lobby) or joining a friend then waited for it, sometimes for minutes. Now leaving stops the work within seconds and frees its memory, and the next lobby or join starts as soon as it has stopped. A friend's JOIN, an accepted invite or the server browser used while your own lobby is being created used to do nothing; now it leaves that lobby and joins.

  • The lobby's player list no longer jumps while someone's join keeps failing. A game that got into a lobby and fell out of it again within seconds, over and over, was added to and removed from every player's list each time, and the rows under it jumped up and down. A player who arrives after you now gets a row once they have stayed five seconds; players who leave still go at once.

  • Lobby logs no longer fill with the same lines. A lobby on a map with no picture looked for it again on every frame, reading every installed mod and logging the mods' ODST maps about 25 times a second. A missing picture is now looked for once, the ODST maps are logged only when they change, and loading a big saved Forge map says how many budget entries it added in one line instead of one line each.

  • A map change gets the next map ready much sooner with many mods installed. At every map change the game read its whole mods folder again before it said the next map was ready: three to five seconds with 120 packages, for a game on the installed maps too, which was longer than a server's countdown, so the game was sent away to join again. A map change now goes by the mods as the join read them, and reads the folder again only when the next game names a mod that read did not have.

  • The message for a game too big for the memory fits who reads it. Only the host is now told to turn off sources in the lobby, since only the host can. A player who joined is told that the host's game needs more of the game's memory than this PC has, a film goes back to Theater with the reason, and a campaign mission no longer mentions a lobby. The map memory pool's sentence now says where that setting is written.

  • The Linux and macOS builds find MCC with a player folder from the Windows build under Wine. A player folder brought over from the Windows build run under Wine or Proton named the MCC folder as Windows did (C:\Program Files (x86)\...). The native game took that for a folder beside its own program and opened on the "Where is MCC?" page, even when a working MCC folder was on its command line. It now reads such a folder through the Wine prefixes that have that drive, and when none holds MCC it looks in Steam's libraries as it does on a first start. The saved folder is left as it was, so the Windows build still finds it.

  • A party ends when everyone else has left it. When the other players left your party, it stayed open with only you in it. It now ends by itself, with one line on the FRIENDS page. A party still waiting on an invite you sent, searching for a match, or holding a place for a player who dropped and may come back stays open.

  • Player counts say the bots apart from the people. A friend's game on a server with 100 bots and one person read "101 (120 Max)" in the friends list's GAME DETAILS. Counts now say the people against the places and the bots apart: "1/120 [100 bots]", "95/120 [1 bot]", and nothing in brackets with no bots. This is on the friends list's rows and GAME DETAILS, the party's state line, Discord, the server browser's rows and server card, and a dedicated server's console (status, players, dedicated status) and status.json. Bots never count toward a server being full, its queue or the browser's player totals. Friends who play an older version still send their old count.

  • A selected custom button layout stays selected beside another build's settings. When a saved player's record or the client settings held a setting another build added, a custom controller button layout the player had selected was set aside with it: they played with the stock layout, and the notice named the layout as another build's. A setting refused only for one read after it is now tried again, so only what this build truly cannot use is set aside.

  • A saved player's own controls can be changed again after playing another build. A saved player whose keyboard and mouse settings were saved by a feature-test build could not have their controls changed: Apply Changes left the changes waiting under a red "Invalid player record; not replaced" line. Their record now loads with everything this build can use; what it cannot (a setting another build added, an option it does not have) is kept in the file for that build, named once under Own Settings, and written back untouched. The same holds for the ODST trooper. A record that is truly damaged is still never saved over, and the message names the file and what to do.

  • Back on the main menu calls off joining a server again by itself. While the game waits to join a server again by itself (after a rejoin of the server you had just left never got in), Back on the main menu calls that join off, as choosing another game does.

  • Joining a server you just left no longer leaves you alone in its lobby for good. When you left a server and joined it again straight away, you could sit alone in the lobby ("WAITING FOR THE SERVER") for as long as you waited, because the server still had your place from the game you had just left. The join now gives up after 16 seconds and, when it was a rejoin of the server you just left, joins it once more by itself half a minute later, once the server has let go of your last game. If that try does not get in either, the main menu says so. Choosing another game in the meantime cancels the second try.

  • The automatic rejoin never pulls you out of something else you started. While the game waited to join a server again by itself, starting a Halo 3: ODST, Halo: Reach, Halo or Halo 2 mission (and some other games) from the menus did not call that rejoin off, so it could join the server once you came back to the menus. Anything you start now calls it off, and the wait is shown on the main menu, where Back also calls it off.

  • The automatic rejoin's message leaves the screen as soon as you call it off. The message at the top of the screen ("The server still had your last game. Joining again in a moment…") stayed for its whole half minute after you left the lobby, because it was already showing as a notice. It now goes the moment you leave.

  • Calling off the automatic rejoin takes its message away at once. After a rejoin that never got in, leaving the lobby (LEAVE LOBBY, Escape or the controller's Back) during the half minute before the game joined again by itself left "The server still had your last game. Joining again in a moment…" on the main menu for the rest of that half minute, though nothing was going to join. It now goes as you leave.

  • Dedicated servers: the remote console's player list shows the running score. During a game, the remote console's players command (and its JSON reply) listed every player's score as 0, whatever they had scored: it read the score that is only filled in when the game ends. It now shows the score the in-game scoreboard shows, as it stands.

  • Halo: Reach maps with fires and explosions run much faster. On Halo: Reach maps the game drew the whole level a second time every frame while certain effects were alive: building fires, rocket, mortar and tank shell explosions, and an overheating plasma pistol. Boardwalk and Exodus, which burn such fires all game long, ran at a third to a half of the frame rate they should have. Those effects no longer cause the extra drawing, and they look the same.

  • Co-op: Halo 2 and CE guests in host-authoritative co-op play the mission instead of a black screen. Halo 2 and Halo: CE guests in host-authoritative co-op now play the mission instead of sitting on a black screen.

  • ODST lockstep: squads past 352 no longer read uninitialized bits. Squads beyond the 352nd in ODST's big maps no longer read uninitialized memory in lockstep co-op.

  • Reclaimer Kit: a scaled object's collision scales with it. A crate or a piece of scenery made bigger or smaller in the Reclaimer Kit kept the solid shape of its original size: players stood inside a big crate's picture and walked through its outer part. Its solid shape now takes the object's size, in the Kit, in its playtests and on maps compiled from now on (compile an older map again to get it), and when an object is resized during a multiplayer game. Weapons, vehicles and characters keep their own shapes, and other maps play as before.

  • A player dropped from a server's game no longer hosts a copy of the server. When a player's game could not get into a dedicated server's game in time (on a big server, several players loading a large mod map at once), it fell back to a lobby of its own. The game then thought the server's session had moved to this PC: it closed its connection to the server, hosted that empty lobby under the server's name and listed it, so the player sat alone, believing the server was gone. Dozens of players could leave a full server this way within seconds. Now a dedicated server's session never moves to a player's PC: a player whose game falls out of the server's game while the server still answers joins it again by itself, and one whose server stopped answering is told so on the main menu. Lobbies hosted by a friend still move to another player when their host leaves.

  • Servers: a map that fails to load no longer crashes the server. A dedicated server could crash at a game's start when the game's map failed to load (seen on a Forge map with Reach objects on a mod map). The failed load is now logged and the engine is left with no map: the server tells its players in chat that the game failed to load, asks their games to join it again, and starts again with that game (a voting server counts it down first, without a ballot). It tries that game up to three times in a row; after that it skips the game for 30 minutes and plays the next one. A skipped game is never picked or offered on a ballot, by the server or its failover standby, and comes back by itself once its 30 minutes are over. A game the console picks outside the playlist is never tried again or skipped for a failed load, and no playlist game is blamed for it. Failed loads alone never stop a server. A reload of the configuration keeps the game the lobby is about to start (a retry or a console's choice alike) while that game is still in the playlist (a game the reload removed is dropped only on a voting server whose countdown has not begun; a countdown already running, or a server that does not vote, still plays it), and keeps each skip on its game, wherever the playlist now has it; editing a skipped game's playlist entry, or restarting the server program, clears its skip.

  • A dedicated server whose next game is too big for its memory keeps its players. When a dedicated server's next Forge game merged more content than the game's memory holds for one map, its engine now goes on without a map instead of closing: the server tells its players in chat that the game needs more memory than it has, asks their games to join it again, and starts with another game of its list. That game is left out at once, never tried again (other maps that fail to load are still tried again a few times first), and is never offered on a ballot.

  • A voting server short of playable games rotates them with lobby sizes too. When a dedicated server's voting playlist has fewer playable games left than a ballot needs, because some are marked unplayable, the next game is now drawn by weight on playlists with lobby sizes as well (those played the same game every round), and it starts with the usual countdown without being shown as the console's chosen next game. A game marked unplayable never fills a ballot in, so a ballot is full while three playable games are left.

  • A server's standby skips the games marked unplayable too. A dedicated server's failover standby was started without the list of games its server had marked unplayable, so after a failover it could draw such a game again and drop every player once more. The standby is now told the same games as the server itself.

  • A server whose playlist lost a game it cannot play still rotates its games. When a dedicated server marks a game of a voting playlist as unplayable and fewer games than a ballot needs are left, the lobby now draws the next game by weight, as a short playlist does, instead of playing the same game again.

  • A server's ballots no longer offer a game whose content it cannot make. A dedicated server that found a game's content cannot be made skipped it when it chose the next game itself, but its ballots could still offer that game, and a vote for it dropped every player once more. Such games are now left out of every ballot and draw, on the server and on its failover standby alike.

  • The game no longer refuses to start when its settings file holds a setting this version does not know. A setting saved by a newer version (or one this version reads another way) is left out when the game starts, with one line in the log naming where it is, and everything else in the file is used as saved. The file itself is not changed by starting the game; the next time settings are saved, the settings left out stay in the file for the version that wrote them.

  • A freeze when the engine traced certain lines through the world no longer happens. A game could stop on its last picture mid-match and never recover (the window stayed open, the game had to be ended) when the engine traced a line through the world whose coordinates were broken, or which lay flat along the very bottom of the map's space. A freeze like this one hit a player on Hugegrass as a Light of Judgement's cruiser came in. Such a line now meets nothing and the game plays on.

  • Switch camera works for ODST troopers and other third-person characters. On a server whose camera is Players choose, a player whose character starts in third person (Halo 3: ODST's trooper, a mod's third-person character, or a game type whose traits set the camera to third person) could not get out of it: the Switch camera key could only ask for third person, never for first. A press now picks the other view from the one you have, whatever put you there, and every player in the game sees your shots leave from the same place. The host or server needs this build for it: on an older one the key works as before.

  • Third person no longer follows you from a class mode's server to the next game. After playing a game mode whose classes play in third person (UNSC vs Covenant among them) and leaving it before its round ended, the next game you joined, and sometimes later ones, could show you in third person too, on a server that plays in first person. The game now forgets the last mode's cameras when you leave its game, when the game you join runs no mode, and when you host the next game yourself.

  • A player who joined the lobby first gets the scoreboard in the game. A player who joined a custom game's lobby before the host started the game pressed Back for the scoreboard and it closed the moment it opened, and Tab held showed nothing: the game's results never reached that player. The host now sends every player the whole results of the started game, so the scoreboard shows the scores and rows the host has. Players who join a game already running were not affected.

  • A freeze when an object's test gave back a broken distance no longer happens. The game could stop on its last picture mid-match, and never recover, when the engine traced a line past an object and the object's own test gave back a distance that is not a number. Such a distance is now left out of the trace, as the Xbox 360 game leaves it out, and the game plays on.

Install

Project Reclaimer needs Halo: The Master Chief Collection with Halo 3 installed. ODST, Halo: Reach, Halo: Combat Evolved and Halo 2 show in the game once they're installed in MCC too. No game files or game code are included: the game finds MCC in your Steam libraries, or asks where it is, and prepares the engine from your own copy the first time it starts.

  • Windows: run project-reclaimer-client-v0.10.8.exe. An installation of 0.9 offers this update itself.
  • macOS (Apple Silicon): unzip project-reclaimer-client-v0.10.8-macos-aarch64.zip, move Project Reclaimer.app to Applications and open it. Apple hasn't checked these apps, so macOS blocks each one the first time: close the message, open System Settings > Privacy & Security, choose Open Anyway under Security and enter your password. Updates don't ask again. If macOS says an app is damaged, or Open Anyway doesn't appear, run xattr -dr com.apple.quarantine "/Applications/Project Reclaimer.app" in Terminal, with that app's name.
  • Linux: unpack project-reclaimer-client-v0.10.8-linux-x86_64.tar.gz (-linux-aarch64 on ARM64) and run project-reclaimer; its README says how to add it to your applications.
  • Dedicated servers: project-reclaimer-dedicated-v0.10.8.exe on Windows, project-reclaimer-dedicated-v0.10.8-macos-aarch64.zip on macOS, project-reclaimer-dedicated-v0.10.8-linux-x86_64.tar.gz (or -linux-aarch64) on Linux, or the Docker image ghcr.io/projectreclaimer/project-reclaimer-dedicated:0.10.8. macOS blocks a server downloaded in a browser too: run xattr -dr com.apple.quarantine on the unzipped folder in Terminal, once, before its first start.
  • Tools: each is a download of its own and needs nothing else from this page, so get only the one you want. The remote console is reclaimer-rcon-v0.10.8, with RCON.md for setup and commands, customization mods use reclaimer-customization-editor-v0.10.8, and the Reclaimer Kit is reclaimer-kit-v0.10.8, which needs only MCC and updates itself as the game does. A bot for a dedicated server's chat and voice is reclaimer-bot-v0.10.8, with BOT.md for setup. Each comes as .exe for Windows, -macos-aarch64.zip for macOS (each app opens the first time as the game does, and the bot needs the same xattr command as a server) and -linux-x86_64.tar.gz (or -linux-aarch64) for Linux.

The game's log is Logs/client.log in its player folder: %LOCALAPPDATA%\ProjectReclaimer on Windows, ~/Library/Application Support/ProjectReclaimer on macOS, ~/.local/share/ProjectReclaimer on Linux.

Don't miss a new project-reclaimer-releases release

NewReleases is sending notifications on new releases.