V3 Question

[Dabomstew]

As far as v3 development goes, we've hit a snag that we would like input on.

Basically, to develop v3 from scratch in the way we would like to, we'd have to almost completely abandon any support for v1/v2/Redux mods. Basically, the new engine would have a new database & file structure that would make using old mods impractical at best and impossible at worst.

There is, however, another option... and that is offering a possible closer successor to v2 either seperately, or as a more "immediate" v3 before releasing a completely new engine.

Obviously, the v2 successor would still have many new features... while retaining the essential parts to maintain compatibility with v2 mods with few changes.

Your input on this, as a current or past user of MCCodes and/or developer of MCCodes mods, would be appreciated. While we won't be necessarily taking what is said here as the final word, we want to hear what the community has to say on this issue.

[CavellA]

Code it from scratch. As far as the old mods and versions their just that, with time everything progresses and if you really want mc to progress you need a fresh start for v3 not more of a v2.9 as far as the older versions this forum is here to help out with mods and stuff and for the new one people will develop new mods anyway so nothing is holding you all back. Scratch is whats needed.

[rulerofzu]

Go the extra mile and convert a large chunk of the v1/v2 mods and release them as downloadable bolts for those with a valid lic.

[Dave Macaulay]

You could attempt to create a very confusing and potentially lengthy "compatibility layer". Which would attempt to allow original V2 mods to be imported into the new engine and in essence emulate the V2 functions from the V3 code.

This is a pretty lengthy and confusing process, but if you don't want to lose your entire userbase you need support for the V2 mods which are available due to that being one of McCodes mains USP's.

[Dominion]

Mccodes, even if you don’t care to admit it, is never going to be aimed at the more seasoned developer. If you wish to change this then you can drop mod compatibility, and expect a tiny amount of sale compared to your past. On the other hand keep it and keep your appeal to the newer developer.

Personally, and having seen the first alpha and given my opinion on that, I say keep compatibility.

The other option is not dropping v2 for sales. You could outsource it a little, and allow for some updates without killing mod compatibility on the original engine. I doubt that you could make it modular or for that matter change things as much as some would like (such as changing the database to a better design), but it could certainly be improved.

[illusions]

Youd be silly at this stage to do away with V2 its been your main income and you would be wise to build on it,,

[CavellA]

Logically v2 should be just that. Everyone want it to be compatible but you need to think about whats best for the future of the engine. If people who are on v2 doesn't buy v3 who cares because if its that good you will build up a new user base. When something upgrades just a little it should be v2.99 or something but if you are making a whole new version it needs to be just that. Yea v2 made you all cash but thats because of how different it was, some what original also and its pretty easy to use. You need a new engine in itself, 100% new, v2 is the past thing so dont let it ruin a future for v3. I play call of duty modern warfare 2 just because I have all my guns on there doesnt mean its logical to carry them over to MW3. If people want to use v2 by all means let them use v2, but when they want to upgrade to a totally new version they have to be ready to do that. A more logical solution would be to take the top 10 - 15 mods and code them and add those in as a given bonus. you can add those in to the first 20 buyers first 50 or for everyone but atleast they have some mods to work with and you have a totally new engine which will go alot further than trying to go into the future using things from the past...Its a new age, live in it.

[Spudinski]

Working with redundant scripts is a pain, and from personal experience it suppresses the ability of future generations of the application.

A application I'm currently assigned to is much like this, even though it's more SaaSy.
We can not upgrade to PHP 5.4 because it still uses features deprecated in the new release, and because of a few other reasons.
Neither can we develop a new version of the application, because so many other features requires certain parts of the code base.
I even had a bug today where one javascript file w so old that it created a bug because of deprecated features within the JS engine of most browsers.
But most of all, we really do not have the time to develop a new system purely because of the maintenance(bug fixes, additions, client-specific, etc) of the current application.

If you have the chance to develop a new generation/version of the engine, I would say do it.
I wouldn't say you drop previous versions right now, but they shouldn't be your highest priority.

[illusions]

With V2 you had something to build upon but with V3 you cant locate one file to basically help you build on another thats my rant over

[Djkanna]

Drop it, all new.

I'm sure if your product is worth our time a few community members probably would be willing to redo a chunk of the freely available mods for v3.
However those willing members should get early access to the script therefore upon release there is already a few addons available.