Last night, vecna the ever-giving gifted the world with [a new build of VERGE 3].

In addition to several [bugfixes], V3 now has:

...and much more importantly...

That's right, VERGE now has network capabilities. Here is [VergeChat], a VERY simple chat server app and client app demonstrating how to use the netcode. Use this as a little tinkering-guide in the meantime. Remember, you need to have two or more people to enjoy the wonders of most of the netcode.

Vecna will be accepting feedback on net stuffs for the next few days and he will probably release a followup build in about a week with some tweaks and additions. Then his next priority for the following major build will be adding floats.

In addition to all these wonders, Tatsumi has released a new build of Maped 3 (which is included in the engine zip). The changelog is [here] and I'm sure he'd appreciate feedback as well.

Also, Zip and the gang have been hauling arse on the packin. Sully is now complete up through Dread Castle Heck... so we're Real Real Real Close Now.

The easiest netfunctions to use are

string GetUrlText(string url)


int    GetUrlImage(string url)

When doing GetUrlText, it's smart to use newlines as your data delimiter, and to make your first token something unique so you can check against it for verification purposes, lest you get a 404 page or an error message.

GetUrlImage returns an image handle. I would imagine it retorns 0 if it failed (have not tested it yet).

There will be a very simple premade library in the Sully Zip to run conversations from web-based scripts, like so: [clicky].

Also, yes, the revisions to maped are probably the most useful part of this release. Everything else is just whizbang neat. ;)

Now, with this netcode, does it just use standard TCP Sockets, and if so, how does the data get sent? If a server I write in C++ could get this data, then my dreams of a MORPG Verge game may come true!

The lack of the first M means only Multiplayer Online RPG, meaning that as long as I support two people, I'm golden =P

Quote:Originally posted by rpgking

MORPGs should be very possible. MMORPGs would be insane to attempt...

Anyways, I love the custom color filters, and Maped3's new features. :)

Since when are VERGErs known for sanity. The foundation of our community was built around a talking clam.

I would utter the words Verge Online... but... oh wait, oops.

It wouldn't really work with V3 anyway.

Duuuuuuuuude.

Props to Vecna. This makes me want to program a creepy-cool experimental single-player online game that changes as time passes and everything goes great until someone hacks the site it's connecting to and uses it to format their computer or unleash a robot army or such.

Bah. I think I'll make it anyway.

Ok, finally the new build is MINE! Yay! Now off to have some FUN!

I'm not on the dev team, so take my words with a grain of salt, but I really don't see the Map() exit thing being changed. The reason is that when you change the map, you have to unload the symbols (functions, global vars, etc...though I think map VC doesn't allow globals) defined in that map so they don't conflict with the symbols defined in the new map. Having two functions with the same name in different maps would screw you up...you wouldn't be able to switch between those maps without a conflict.

And that's the reason that the Map() call stops execution of the previous context once it loads the new map. The call stack is emptied because the old functions are no longer in memory. Plus you open up the possibility for funky errors...if you keep going after a map transition then you might end up trying to access entities, tiles or whatever that are no longer loaded. Or worse, trying to access stuff that used to be there, but is now different stuff under the same name.

Anyway, the only way that would be fixed (in my estimation) is if the engine architecture is changed to disallow maps from defining functions with the same name (either by giving each map its own namespace or just flat-out disallowing identical names, both of which would be a pain in the neck for the dev team and the users), load every map at startup, and keep it in memory until shutdown. Which is not a good idea, no matter what Grue says about RAM being meant to be used ;P

The music thing would be nice, though. And if my understanding of the engine is sorely lacking, I'd greatly appreciate some enlightenment from a friendly dev.