2.9.26
Released 2 November 2026
JunctionCode is a Windows agent that edits your ARK server configs, mod lists and launch scripts on your own PC. Version 2.9.26 shows every step, and you approve each change.
./server-configs6 filesGameUserSettings.ini42 linesMultiplier GameUserSettings.ini3 matchesGameUserSettings.inibackup savedGameUserSettings.ini+3 -3XPMultiplier GameUserSettings.ini1 matchReleased 2 November 2026
64-bit (x64) only
Setup; portable file is 25 MB
Interface languages in the app
No sign-in needed
No telemetry
ARK mods are built in the ARK Dev Kit with Blueprints and assets, and JunctionCode does not edit those binary project files. It works on the text beside them. That is the whole scope. It covers 2 INI files, a launch script, mod lists and logs.
You want a 2x weekend on your own server, so you ask JunctionCode to raise XPMultiplier, TamingSpeedMultiplier and HarvestAmountMultiplier in GameUserSettings.ini. It runs read_file to open the file, grep to find the three keys, and copy_file to save a backup first. Then edit_file changes 3 lines. You see the diff. In Ask first mode the agent pauses before every write, so you read the change, restart your server and test the new rates in game.
read_file GameUserSettings.ini → 42 lines
grep Multiplier → 3 matches
copy_file GameUserSettings.ini → backup saved
edit_file GameUserSettings.ini → +3 -3A friend wants a calm PvE server, so you describe it in one sentence. JunctionCode uses write_file to draft a GameUserSettings.ini with ServerPVE=True and AllowFlyerCarryPvE=True, plus a Game.ini for breeding settings. Then grep checks that every key sits under its section header. That makes 2 files. In Plan only mode you read the plan first, and in Ask first you approve each write before you start the server and test.
write_file GameUserSettings.ini → +14
write_file Game.ini → +8
grep ServerPVE → 1 matchAfter an update your server acts differently, so you keep the old file next to the new one and ask JunctionCode to compare them. It uses read_file on both copies and grep on the keys you name, then write_file saves a notes file with each difference it found in them. That covers 2 configs. The notes are only a list, and you decide which value stays before you test it.
Your game shows "couldn't load mods library from disk" and you want to know why. Save the log as a text file in the working folder, or keep a screenshot of the message. The agent uses grep to find the error lines, read_file to read the text around them, and ocr to read the screenshot, then it explains the message in 3 plain steps. You apply the fix. Test it.
Version 2.9.26 works directly on the files in your working folder and shows every change as a diff, instead of only describing steps to you. That is the difference.
| Typical chat assistant | JunctionCode | |
|---|---|---|
| Config edits | Gives you text to copy and paste. | Edits the INI file and shows the diff. |
| Log errors | Guesses from a few pasted lines. | Searches the whole log with grep. |
| Control | Has no approval step. | Ask first pauses before every change. |
| Where it runs | Works from what you describe. | Runs on your Windows PC, no telemetry. |
Server owners who run a private ARK server for friends will get the most out of it. You change a handful of INI values a few times a month, and the diff shows you exactly what moved. Mistakes are easy to spot.
Mod makers who build in the ARK Dev Kit can use it for the paperwork around Blueprints, such as design notes and a written list of the 5 mods a server loads. The Blueprints stay in the editor. Nothing there is touched.
Beginners who feel lost in INI files can start with 1 file and ask the agent to explain each line before it changes anything. Plan only mode is made for that, because it explains and plans but never writes. Start small.
ARK mods are add-ons that change or extend the game. Creators build them in the official editor with Blueprints and assets. JunctionCode does not build mods. It helps with the server configs, mod lists and logs around them, and you review every change before it is kept.
Yes. This is the official JunctionCode website, and the download here is the original build. Compare its SHA-256 checksum with the published manifest before you run it, and use the Send feedback button inside the app to reach support.
No. Mods are Blueprints and assets inside the editor, which are binary project files that an agent does not edit directly. It can plan Blueprint logic and write design notes, while the building stays in the editor.
The number depends on your hardware and on the mods, so JunctionCode sets no limit, but it can list every ID in ActiveMods so you can count them yourself. Add mods slowly.
The message points to a mismatch you need to check. JunctionCode can read ActiveMods in your server config and compare that list with the mods you wrote down, so you can see the difference. You decide which stay.
No. Choosing a mod is a matter of taste, and JunctionCode has no ranking of mods. It can write down what you need, such as 3 changes you want, and keep a tidy list of the mods you try.
No. In Ask first mode, the agent pauses before every action that changes something and shows you the diff first, so nothing is written behind your back. Auto-run applies changes at once, while Plan only changes nothing at all. You pick the mode.
Download the 34 MB setup, point JunctionCode at a folder with copies of your server files, and ask for one small change. Review the diff.
Download JunctionCode for Windows ↗Every page on this site is also available in 20 languages.
What the agent does ↗ Connecting a model ↗ Server config guide ↗ Download and checksum ↗ Answers on mods ↗ Data handling ↗