[pingu]

Elysium Engine
The Open Source MMORPG Maker

Visit The Elysium Website

Massively
Multiplayer
Online
Role
Playing
Game

Elysium Engine is a program that will enable you to create your own online game and play with friends on the internet! Battle monsters, collect rare items, and even just talk with people you know from halfway around the world! Also, the program is completely open source, so you can code in your own changes to the game, and make it better!

Elysium Engine is written in Visual Basic 6, so anyone with a basic knowledge (or anyone with enough patience to learn and copy tutorials) will be able to add in their own neat features (Or maybe start from scratch?).

And... The Elysium things don't stop here! If you don't know Visual Basic, you can use your "own" Scripting Language called Sadscript, where you can do a lot of things just pasting codes on txt and the commands will be executed in-game!

Not convinced? Here are some screenshots. Click on the picture to see it full size.

Main Menu Screen

Server

Character Select

Main Game

Map Editor

Item Editor

The Code

Anybody for a partial feature list?
- Private Chat
- Scrolling Maps
- Day/Night System
- Guild System
- Party System
- Music/SFX
- News System
- Items
- Arrows
- Customizable GUI
- Security on Server/Client data.
- Flash Player
- Advanced Scripting Ability
- 6 Graphics Slots
- Warp System
- Editors in-game (Map-Editor, Item Editor, and much more, all in-game, you can edit with only one command!)
- So Many Attributes It Isn't Funny
- Everything else you'd expect from a MMORPG!

The list above is only partial because it is off of the top of my head.

For help, downloads, and support from all of our members, please visit the forum here.


I hope I'll see you soon!

[BadMrBox]

seems nice pingu. Keep up the work. :)
_________________

[pingu]

[tunginobi]

This is looking quite nice. And I'm happy to see somebody who consciously comments their code.

[LeoDraco]

[tunginobi]

Actually, that did cross my mind. Still, after seeing code from so many other people over the intarwebs, I supposed it was better than nothing.

I didn't want to rant; what's been shown here is overall a commendable effort, not to be outshone by nitpicking.

[pingu]

The "actually move them" thing twice is because there are two types of NPCs, normal ones and ones that spawn a certain number from a certain spot. I don't know why there are two, but the original creator decided to do a lot of extra work to make something that doesn't work well.

I'm going to scrap it for the next version, though, because it makes no sense.

And I'll safely say that not every part of the code is as commented as that part (it's the game loop). I was going to comment everything for the next version, so anything you specifically want me to do?

[tunginobi]

I vote for the existence and usefulness of comments. I don't support commenting everything. If you write it well enough, most of your code should document itself.

[RuneLancer]

[LeoDraco]

RL: I know the whole anti-over-abstraction crowd will probably start throwing tomatoes in my general direction, but that seems a lot more complicated than it should be: for instance, a (cartessan) vector class could probably help clean that up a bit. Or something. Uh, but that really is not important, here. (For all I know, that was just some random example you pulled from somewhere, heh.)

All: Again, comments should not describe what the code already describes: it's code, and with the exception of the original programmer being obtusely clever, it should not need its functionality explained; what it does need, however, is an explanation for its existence: why does it exist? what purpose does it play in the grand scheme of things? how does it interact with other modules of the program? Note on the latter two, those are very differenct questions from what does it do and how does it do it; the good comments provide more information (one could even go as far as to say that they are a form of meta-code, and certainly there exist languages which provide functionality similar to that (e.g. .NET attributes come to mind), but that might be a relatively weak argument) about code in a given context than is obtainable from simply looking at the context by itself. This includes simple function documentation, which would purport to describe intended values for parameters, expected return values for those parameters, intended and potentially unexpected (though possible) side-effects, invariants, and so forth.

Like other elements of good style and design, comments should enhance the code, rather than obfuscate and clutter it.
_________________
"...LeoDraco is a pompus git..." -- Mandrake

[Rainer Deyke]

[pingu]

New version.

Elysium Diamond (v 2.0)
Made by pingu.


:: Intro ::

Okay, this is absolutely final! I'll be doing the compiled version tommorow and I'll include an updater. Look at the posts further one for the code changes and a copy of the license.


:: License ::

Here is the license in a nut shell. The full version is in the download and in the post below. This is not an official interpretation and may not be 100% correct (I'm just adding this in so you guys can't say "but pingu said...").

[tcaudilllg]

I love that presentation. You successfully turned a project description page into an veritable info center for your project!

I think I'll take a page from your technique...

I'll look into your engine later.

[pingu]

That post doubles as the advertising post and the download post. I'm trying to look very professional with this release. Professional to the point where I make a note of always using caps in file names and things like that.

Tell me if you do look into it and what you think of Elysium!

[BadMrBox]

Hey Pingu, is there any games made with Elysium Diamond?
_________________