WARPGATE started as a way to download the 2025-07-16 client and keep it up to date. WARP0716
started as a set of patches for it. Until now they have been two things. Part 3 makes them one, and before we
lock in what goes into it we want to hear from the people who use it.
TodayWARPGATEdownloads your clientWARP0716patches it, in a separate program
Part 3WARPGATEwith LGN-WARP built in: download, patch and keep it current in one window
What WARPGATE is becoming
The one place your client lives, from the first download to the exe you play on.
DownloadEverything you needThe client, the translation and the Ragexe, as today.
PatchIn the same windowNo separate program to open and no folder to find.
Keep currentRebuilt with your choicesWhen a patch or the client updates, WARPGATE tells you and rebuilds with the choices you already made.
Get helpWhere you areReport a problem or suggest a change from inside the app.
What LGN-WARP is becoming
WARP0716 is being renamed LGN-WARP, and it is moving inside WARPGATE.
The same patchesBuilt into the appThe patches you use now, without a separate tool.
Your choices savedAs a profilePick your patches and answer their questions once. Reuse, change and share the result.
Releases we testChecked and signedPatches reach you through WARPGATE as tested releases, so an update is something you choose.
Still openOn GitHubAnyone can read the patches, change them and send improvements back.
And that is not all
There is far more coming with Part 3 than this
page lists. A lot is being added, and we will show the rest as it gets closer.
What does not change
WARPGATE and LGN-WARP stay free, and so do the patches we make. It stays a community project. Until Part 3
is out, WARP0716 keeps working as it does today and gets fixes for bugs.
Tell us what matters to you
About two minutes. Skip any question you like. Open until the end of November.
Thank you. Your answers are in. We read every one, and we will post what we
learned after the questionnaire closes.
Nothing was sent. No question was answered. Answer any of them below and
send again.
Not saved. Too many answers have come from your connection in the last hour.
Please try again a little later. Your browser's Back button brings your answers back.
Not saved. Something went wrong on our side. Press Back in your browser to get
your answers back, then send again. Tell us on Discord if it keeps happening.