...ok... so the message board doesn't like me.

This is now my 4th try to post this as a new topic. Hrm.

Basically, I'll take on the role as leader, if you all want that.

Here's some highlights of my plan:

1. Create a SINGLE, solid, useable build.

This would entail gathering and creating (with the help of the few "main" coders left) all of the features currently implemented across the various releases, and doing a single build, with a single source tree. This release would probably be labeled v2.9

It would be managed by a group of coders, and the build wouldn't be released until all coders gave their nod.

My goal would be to make this happen quickly. Very quickly. Like within a couple weeks.

2. Build the RepoII.

Make a site that supports the development effort. It would be simple to use, probably have a CVS repository, and maybe even it's own IRC server. Don't know. Esper doesn't like me very much. :)

This site would grow to be the primary developer, worldbuilder, and release site. verge-rpg would probably remain as the community/news site. Maybe... maybe not. /shrug --we'd decide that when we get to it.

3. v2.91-v2.99 and a demo

The VERGE developers would be asked to make monthly releases that contained bug-fixes only. No new features... just fixes. These would be defined as v2.91-v2.99 (if they do that many releases).

This would also be a chance for some folks to come together and build an updated (and short!) demo on the v2.9 "final" engine. Nothing fancy, just a short run through it's major features.

4. Prepare for V3.0

All of this will be building up towards a new release, with new features, of VERGE 3.0. This would include all of the features that couldn't make it into 2.9 for whatever reason, and maybe some new ones (plugin support?).

This would then follow the same cycle as the previous build, with incremental bug fixes released as sub-versions (3.1, 3.2, etc..)

5. VO

I would like to get the complete source for VERGE Online, and as a first step (with much help from the developers) update it with the v2.9x engine. Maybe we could get this very promising project going...?

........

And that's to start with. These are listed by order of importance, not by timing. We would tackle the single build issue first, then the site. While doing the 2.9x fixes, we would be looking at the VO code, and trying to update it. On top of this, a few people could be working on the 2.9 demo.

Work on V3 would happen probably in a couple months, and hopefully we could get things rolling into a regular cycle of releases. Maybe monthly bug-fix releases, and quarterly major (new features) releases? Something like that.

So that's what I'm thinking.

How's that sound?

If you don't think this is a good idea, say so. It's not going to hurt my feelings.

But I believe in VERGE's future, and I think, if we can pull it together, we can make something great once again.

Email me with comments.

locke@devnull.sh

-b

---

Sounds very good; However, although you're completely suited to be the leader, wouldn't it be inappropriate to just disregard tSB as ever being anything more than a coder? :P

And now the several points:
a) V2.7 sounds exactly like your visions of V2.9 (why'd you skip ahead?). It should be that "single solid useable build". But wouldn't we need others? VERGE 1 (windows version) for simplicity, the VC version of V2 that works in windows (whatever it's called), and V2.7 should be the main builds we need. Hopefully, VERGE1 will be pushed out due to the standard libraries coming with V2.7. But, a VC version will be needed for a while due to Python-haters.

b) Wouldn't it be more beneficial for the community (and easier/faster) if VERGE Online was ever to be made for it to be made in V2.7? It's possible. As a matter of fact I'm learning how to make chraracters for no reason so if you need a newbie artists I'm here. And I have some experience with coding games using sockets (mostly MUDS).

c) Yes...we need a new repo....desperately....

-- Andrew Rayner

---

I'm a masochist. Satiate my lust for pain. Give me VC.

---

I was raptor151 and a big-time newbie back when you were around (and all the other oldbies posting all of a sudden!) But now I'm a lot more experienced and into the whole thing. Got a big game plan going on, making some progress...

I've been posting things to this effect for a while now, but I am incapable of making most of it actually happen. I can code VC really well, but not C++ and stuff, so I'm kinda useless.

My suggestion to you is to get in touch with tSB and join the v2.7 project. I doubt he'll care if you *really* want to rename it v2.9. I mean, if you could get into the board archives from a week or so ago, you could find a massive flame war on whether v2.7 is "worthy" of the name Verge. Names don't matter. Just watch someone flame me for saying that.

Cyberdude is still working on a fully-cool IDE for v2.7 (I think, anyway) Get together with him also.

I think you guys could be a new dev team! And if you can solidify v2.7, slam out an awesome new release within a few weeks as you hope, I would worship you as the new god of Verge. Remember all those old V1 games that made lame references to vecna? That's you, buddy ol' pal.

Me and auroraborealisis (gemini, from long long ago) are working on a fully-cool game right now that would LOVE V3.

So, yeah.

That is all.

--Invicticide

---

We don't need better engines, we need better creation tools!

As I said before, it's great to have you back, locke. And it was a complete surprise to see someone from "way back when" return here.

Ok, with that out of the way, here's what I think.

You should probably support tSB in his effort to make v2.7 the next-generation build. He's practically finished with it right now, and it can only get better if you(and possibly others) chip in(You came in at a time when the future greatness of Verge is about to appear in full force). And if you wanna make it V3.0 eventually...it shouldn't be a problem if tSB doesn't mind. Afterall, "What's in a name? A rose by any other name would smell as sweet.".

But the entity that I'd REALLY like to see revived is the legendary Verge Online that slipped into oblivion long ago. I think it would be great if a veteran such as yourself saved Verge Online and showcased it to the Online CRPG-gaming world! I'd help in any way that I can, but it would have to be mostly in graphics. In the past I DID make some maps for Verge Online, but they never made it into Verge Online...because Verge Online was never made!

-rpgking

---

Out of clutter, find simplicity. -Einstein

Sounds kewl. However, plans are so much easier than the actual work as we know. My best of wishes to this plan.

---

zaril@hellven.org - ICQ 7698022

I'm mostly interested in VO, simply because I think it would do the community a great good, even though I've gotten some negative feedback on the subject. If the VO project gets started again, I'd love to do all I can to help.

---

urp

2 words:
Ask tSB(andy)

I have been asking him about this, and he wants me to do it in C++. So, I whip out the only C++ compiler I have, MVC5, and he says it's the worst possible MVC I could have. Although I could do a fully-featured IDE for VERGE2.7 in days (or less), it's all up to him in the end. I don't even consider it a "project" considering the short ammount of time it took to make the first two :)

---

I didn't say you *had* to use C++! I just said it was the best choice, since you could do what I've been doing, and have your IDE share code with the rest of the engine. (the map editor not only uses the same map code as the engine, it compiles the exact same file)

Sorry about the mixup.

---

"Ignorance is its own reward" -- Proverb

1) He never said he wanted to make a new version of VERGE. He just wants to lead the development of the official/main VERGE.

2) While some people are trying to get him onto the V27 bandwagon it's not necessarily a bad thing. I quote McGrue who so maturely put it: "Python may help the community in the long run, I just will never support it". Locke's proposal is to lead the dev process of the main engine, not to code it. So we're informing him of what's already been done- those things happen to be within V27. You obviously seem slightly confused on what he was speaking of.

3) Cyberdude was mocked because someone said he was coding it in BASIC and someone else said he coded it solely for MIDI support and because he was bored. Once again, you're thinking that the Python supporters are just trying to jump on everyone's back.

---