Hey! Just saw this post, I sent you a message! (I don't really know how this particular forum software works hahah, but I hit the 'Chat' button on your profile, which looked like the thing to do private messages on here.) Feel free to email me at the address I sent! We can definitely put the Verge Online code up.

I think most of the source is now backed up, thanks to the archives that people sent me! Check the page here (as linked before): https://github.com/verge-rpg

Now we have source for Verge 1's June 1998 release, WinVerge, v2chr (distributed as zip-only, per request), Verge 2.01a, Verge 2.5, Winv2, Verge 2.5j / v2k+j, and a few revisions of 2.6. Also the Verge 3 source code was moved to the verge-rpg Github organization -- I kept a fork at my github account to preserve any existing outgoing links, however.

However, we're still missing source code to official Verge 2.5's VCC, and the source we currently have of WinV2 appears to be from unstable build, not a release version. It seems like Verge 2.6 revision 9 might be able to do a lot of the same things that 2.5 could do + some extensions added later.

If you have any copies of these missing source files, let me know and I can put them on the github repo. Also, if you made any tools for Verge-related stuff and want us to host it, let me know and please let me know any licensing/terms for distribution! For now the GH is for preserving the engine source code, we still need to figure out a different solution for demos and games.

If someone has a good idea for hosting our own organized file directory, maybe we can figure something out! For now we have the vrpg archives, but they're incomplete, and it would be nice to recover and preserve what we can in a collective effort.

Also, Andy (implicit_cast / thespeedbump) has been working on a WASM web player port of V1, and it's open to bug reports and contributions: https://github.com/andyfriesen/v1wasm -- it can sort of run parts of Sully so far, so that's exciting news!

Just started a Github page to archive some the source code. Big thanks to aen, andy, zeromus, and rainwarrior who all helped out with providing some zips.

https://github.com/verge-rpg

Not everything source is on the archive yet, still taking time to sort through stuff. But so far, winverge, v1 + vcc, v2chr, and winv2unpack tools are up. Going to try to get v2.5, 2.6, winv2, and others on there.

Also, zeromus made a modern branch to winverge at https://github.com/verge-rpg/winverge that makes it work on Visual Studio 2019 and run in Windows 10 with GDI (master contains the original DirectDraw 320x200x256-color code), I wonder if we could make a zip release on the GH?

Still need to figure out a solution for hosting and organizing the games, but archiving the engine source code so the old code isn't lost goes a long way.

Lately it's come up a few times on the Discord chat about how to run older Verge games on modern PCs. So I thought it would be cool to share a few tips on how to run older Verge games in DOSBox. And eventually while writing this, I started thinking about Windows Verge as well.

I won't run down how to setup DOSBox and mount a drive and stuff like that, but the setup is pretty minimal mostly. If it makes things more convenient, I've used D-Fend Reloaded as a nice frontend on top of DOSBox to configure a lot of stuff up-front. Mainly you just need to mount the drive, and the rest of the presets can stay the same. There might be memory/mouse/CPU speed stuff to mess with too, but you probably don't need to

General Advice

• Make a copy of your game, and do any changes on the copy rather than the original.
• To be extra safe, don't run the original either. Run a copy.
• Why? Things could potentially modify files (eg. if you try to recompile scripts and compilation fails), or if you replace an executable (as some steps advise) it might not be compatible so it's potentially good to keep the original

Verge 1 games in DOSBox

• Get a newer copy of cwsdpmi from here http://sandmann.dotster.com/cwsdpmi/ and paste it over the cwspdmi.exe included with the game.
• Open DOSBox
• Go to your game folder
• Run cwsdpmi -x to disable its 1.0 extensions (which crash will Verge, and DOSBox itself)
• Run main to launch the Verge game
• For viewing maps, you can open maped or open the V1 map files in Maped 3. The map files will request something about creating a basic obstruction tileset when you import them.
• For compiling scripts, you can use vcc, I believe the command is vcc all?
• Configuration can be edited in setup.cfg
• edit FILENAME can open text files in DOSBox, you could also inspect in a text-editor outside of DOSBox.

Verge 2 - 2.5 games in DOSBox

• Open DOSBox
• Go to your game folder
• You need to use DOS4GW to run the games, I think there's a way to get this DOS4GW launch automatically for any executable that needs it, but I forget how to set this up. So I usually just prefix the executable with dos4gw instead.
• Type dos4gw verge to run the game.
• dos4gw vcc all to compile all scripts (be extra careful with this! you might want to do this only if you're sure you have a backup first)
• dos4gw maped to open maped2 and look at maps. For opening V2 maps on Windows. There's also maped2w by aen written in allegro that could work for opening stuff, but it is a bit unstable.
• edit FILENAME can open text files in DOSBox, you could also inspect in a text-editor outside of DOSBox.
• user.cfg is the config file, and you can use the startmap FILENAME directive to change what map gets loaded

Winverge Games (V1)

• fullscreen mode will probably not work right on a modern display, and will force the display into an indexed color mode + hardware fullscreen at an very low resolution.
• Maybe there's an option to pass to setup.cfg that overrides fullscreen mode? (Does anyone know? I can't find any mention of extra config options in the winverge.txt document)
• This uses DirectDraw. On Windows Vista, 7 (and 8?) I think desktop composition / aero will be disabled.
• Currently not sure how to run Winverge correctly. Is there a compatibility setting you can apply to winverge.exe to get it to run with the correct colors fullscreen mode? (trying 256 color mode crashes on startup) Otherwise, is there a way to run in windowed mode? I looked through the executable with the strings command and couldn't seem to see the string setup.cfg referenced anywhere.

WinV2 Games (Verge 2.5)

• Should mostly work out of the box,
• Might randomly run way too fast. In this case, it might be better run the DOS version of Verge 2.5 in DOSBox.
• Sometimes DOS games written for V2.5 can work in WinV2, but not always. There are incompatibilities, and unlike DOS, Windows has memory protection, so any game that accidentally corrupt memory will likely crash instead of carrying along unnoticed.
• fullscreen mode will probably not work right on a modern display, and will force the display into 256-color mode + hardware fullscreen at an unsupported resolution. It's recommended to open user.cfg and add windowmode 1 to force windowed mode.
• Add eagle 1 to double-size the window with a 2xSAI scaling filter applied.
• You can resize the window manually (but unfortunately, if you the scaling doesn't snap to integer factors or obey aspect so you'll need to be careful)
• This uses DirectDraw. On Windows Vista, 7 (and 8?) I think desktop composition / aero will be disabled. It works fine on Win10.

Verge 3 Games

• These should work out of the box on Windows 10
• Older versions of Verge 3 use DirectDraw. On Windows Vista, 7 (and 8?) I think desktop composition / aero will be disabled. It works fine on Win10.
• Verge 3.2 uses GDI, it's mostly a drop-in replacement, but you might get some conflicts if you run a game that defines min, max, sgn, or other newer functions.
• Some settings can be adjusted in verge.cfg - More documentation about the config options can be found here: https://archive.verge-rpg.com/docs/the-verge-3-manual/verge-cfg-options.html
• system.xvc and precompiled scripts in .map files might not be compatible between Verge versions if you replace the executable. So any game that doesn't have the original .vc scripts and is running with releasemode 1 in its verge.cfg will always have a harder time loading nowadays.

Using the Archive

For that matter, getting files from the Verge archive can be a bit tricky at the moment, because the mimetypes are a bit messed up. To navigate the archive, go to https://archive.verge-rpg.com/ - and click the Downloads link at the top. The search box won't work anymore (since the site is a snapshot), so you need to use Downloads tools > File directory in the left-side bar of the page.

Oh!! Or you can just click here to go directly to the Directory, hahah: https://archive.verge-rpg.com/downloads/directory/index.html

If you try to click the download button directly, it will present you with page of indecipherable binary garbage because the webserver currently tries to serve downloads as HTML pages. Once you find the file, right click the download button and click "Save Link As". Manually save as a .zip file. (Hopefully most files are .zip and not .rar or something else!) If all goes well, you should be able to extract the zip and get it working.

Request for Archives

I think it'd be great to pool together the resources to make a bigger archive of Verge-related zip files. If you have your own webserver, or someone else can host, it'd be nice to make publically browseable lists of the stuff people managed to save from the older Verge days. The verge-rpg site archive has a lot of stuff, but it's incomplete and it's currently difficult to navigate

Especially:

• source code for various Verge versions, as well as source code for old tools. Not immediately useful but could help anyone who wants to further any archival efforts down the road.
• earlier variants on released games (such as different versions of Sully, etc)
• games that were released or shared but aren't in the site archive.
• unreleased games

Other

It'd be very cool if there were was a "Verge emulator" that could support V1 and V2 games of various versions out of the box. Even if it's extremely niche and limited appeal, it'd be great for archival purposes to not have to rely DOSBox exclusively. As much as something like on-the-web would be cool, Verge has a few features that depend on a physical filesystem, so I would recommend it be done in C++ for making the effort of porting existing source more possible. Use SDL 2 since it's cross-platform, support conventional keyboard controls but also allow the SDL game controller APIs for support that out of-the-box. Could always be tied to emscripten to allow compile-to-the-web.

But this is just tossing the idea in the air, it's a pretty huge undertaking to support in general. Honestly, just reimplementing V1 on its own would be extremely neat. DOSBox is ok in the meantime though

--

Anyway that's all I have for now! Hopefully other people can chime in some tips, and throw out advice, etc. It'd be cool to get advise for Verge 2.6, ika, and other Verge-adjacent engines in here too.

I'd love to see more recordings to help show off older Verge games. Hatcher has been talking about this a little bit on the Discord channel lately. I also remember a few videos posted online by rainwarrior that showed off some older DOS games, including a playthrough of Sully Chronicles.

here's an updated link! I set this one to not expire, hopefully that works? https://discord.gg/5EVb3w7

Very cool to see there's still Verge projects being made these days! Let alone Verge games that have plans for a Steam release! ^^ This looks like a cool RPG project, congrats on making this! It's neat to see Epic of Serinor go through so many changes over the years and see it's still going. also I like that story-book style HUD around the game!

Hearing about that Steamworks stuff, it would be nice to merge those changes into the Verge repository some day (if you're willing to share!)

I think deprecating VC and a few other features was a bit of a misstep looking back, since their replacement (the VC-to-Lua cross-compiler) was never fully realized, although Kildorf did make some decent progress on it. I think we probably could bring back those removed features, and merge in the new changes. It looks like most development on Verge sort of froze in 2011, but it would be neat to make a small QoL style release that makes it usable on older VC projects again, and merges in the other changes.

Heyyy! What's new with everyone these days?

I figured it would be nice to start a topic since the forum reboot and stuff and see what's new.

.

Something lately has made me interested in looking at Verge again for fun. The other day I was feeling nostalgic, and started messing around with Maped2 in DOSBox and drawing tiles and maps. (It's pretty fun! even if DOSBox crashes frequently!)

I've also played around with PICO-8 a bunch and something about an environment where it's easy to draw sprites to the screen and make little scripted stuff is fun. I think some of the appeal that PICO-8 has is similar to what Verge had going for it, quick and easy to throw together projects and make small games.

(Part of me sorta wants to go back and revisit Verge 3 (and bring back VC from the 3.2 release into the master) and port it over to SDL2 for better portability, and add some sleep/vsync stuff to ShowPage so it runs with less CPU consumption for most games. It could be kinda neat as a small change to make the engine more usable/preserve older stuff and make it run more stable on new computers)

.

So yeah, other stuff. For a while I worked at Tribute Games in Montreal here. In April 2017, I released a game called Flinthook for PC/PS4/XB1/Switch, which is a roguelike action platformer with pirates in space and run-and-gun action. Since then, I did a few odds and ends and eventually left there. This year has been all over the place (part freelance, part new job) but been poking around with little projects here and there.

What has everyone else been up to?