Quote:
Originally Posted by DarkCloud_PK
It isnt as easy as simply removing the custom systems and whatnot.
A lot of classic, both the big parts down to the smallest of detail would have to be rebuilt to support default HD and movement.
Most of the GC events and tools involving any HD or movement would have to be restructured to work around default, and as we saw with the introduction of clientside HD. Even after being set up for default HD, it would alter the way most events are played, especially CTF, as we have already scene with introduction of clientside HD, which more closely resembled default HD than serverside did.
It wasn't exactly a transistion for the better, since CTF relies on players able to kill each other relatively easily. To both hold up any sort of flag defense and more importantly, being able to kill a flagcarrier who is trying to not be killed. This caused so much of an uproar in CTF that the HD was made toggleable in GC events, and mostly left to serverside.
But I digress, the main point is, it isn't a simple flick of a switch, any conversion to default systems would require exceptional amounts of scripting manpower. Not exactly what Classic has a lot of. If the little amount scripting power that we do have were diverted to reconstructing classic to handle default systems, I could see the project going into years, as in plural. All the while, development on Classic would completely stagnante, as you can't really go on and make anything worthwhile, as your scripting team is busy converting, remember?
As for the old levels before NPC server? That would take even more time than converting the current classic to default.
Fun fact: GTA as of 2004 contained over five THOUSAND levels, remember, it is over 6 years of content.
A vast majority of these levels are in gs1 of varying quality and age, and are not converted to work with the npc server.
This means all 5000+ levels would have to be converted to at LEAST clientside/serverside functionality, as well as removing and updating depreciated scripting commands.
A very thankless task to do by the way, you can barely find people that want to convert levels now for using on Classic, much less Classic as it existed in 2004 in its entirety. It isn't a fun job to convert levels, and in the end, you are left with an end product that contains none of your original work, none of your own creativity.
Needless to say, while many people say they're going to do it, help out and convert some levels, they never do stick around to do it. It is simply not fun at all to do, if you say converting levels to work with the npc server is fun, I would call you a liar. Honestly, find me a team that is capable enough, and large enough, to convert 5000 levels in a respectable time period, people that will actually stick it through one painful level after another.
Oh.
|
All true but please read the following quote.
Quote:
Originally Posted by DustyPorViva
The problem is though, if you add content now, it will be accustomed to the HD that will eventually need to be revisited. Then there is going to be the same problem that is right now, except even more that will need to be fixed when the HD is finally changed.
|
Couldn't have said it better myself! (Thank you Rufus for posting a relevent quote by Dusty.)
Classic should break down the work in what is to be done. For example spars, events, Angel Clan, etc. The work starts from the top.
Needs to break up the work and focus on a peice by peice at a time, with the big picture in mind.
The current staff and new hires should be made aware that there is a 'things to do list'. For example:
- New HD in all Spar Rooms----------------------------Whichever staff is assigned, and last date to work on it.
- New HD in Angel Clan--------------------------------contego 05/13/09
- Update all Spar Room scripts (AFTER new HD.)--------Whichever staff is assigned, and last date to work on it.
- New event project (In new HD.)----------------------Whichever staff is assigned, and last date to work on it.
- Update the ________ quest to work with default HD.--Whichever staff is assigned, and last date to work on it.
- New economy item.----------------------------------Whichever staff is assigned, and last date to work on it.
- New gani's (shift h.)----------------------------------Whichever staff is assigned, and last date to work on it.
- New emots (ctrl n.)----------------------------------Whichever staff is assigned, and last date to work on it.
People should indicate if they are working on the project and post results daily, if possible, as to the last date they worked on it. Keep the 'things to do list' minimal but always keep it up and current.
Help is definitely appreicated by your staff but it's more important to make sure people have something to do.
Dev Admin should be developing work for people rather than developing the game itself (i.e. CTF Sumo).
Many will need to know that what they are working on is
important.
Keep posting and looking for more help. Have someone go out and pound the pavement looking for talent.
A large enough team can be put together to make a difference and get Classic in the right direction.
Otherwise this will only lead Classic into a tail chasing syndrome.
*All of the above are things I've experienced hands on and learned from my degree in
Management Studies.