Mierza, indeed anything can be accomplished with time and a bit of hard work, but these particular ideas require a bit more than most. As I mentioned before, the best feasibility test for someone who isn't a programmer is to compare the requirements to existing systems. If you're asking for something new that isn't done anywhere, that's a potential problem because there's nearly always a reason it's not been done yet. Or, look at it from the other side; what you're asking for are many of the features in a massively-multiplayer online game... and they usually take large teams of professionals years to produce.
Realistic according to who? Your lead coder who is no longer with you, who spent a year working (as an 'employee' ) and yet didn't leave you code or documentation? If you were paying him, you own that code and those docs. If you weren't, then I still can't see why you didn't arrange to have an up-to-date copy of these things at all times as part of the deal. Definitely something to keep in mind next time around.
You probably also know that you're unlikely to get great coders for your project by posting here. For every 1 coder there are 5 designers such as yourself looking for coders, each of whom thinks they have a great idea. And in some cases, the coder is (or believes they are) that designer and will make their own game instead. So maybe you'll get lucky, or maybe you'll end up with someone who will bail out when it gets tough. Good luck.
Do you have any screenshots or examples of some of these features you mention in action? Like those injury outlines? Or are these still just concepts on paper?
In answer to the questions you posed in your reply to Netwyrm:
"since I guess I'll have to start the code over.. is it realistic for a new coder to come in and do the same job as my former" - well yes... starting from scratch is no harder the second time around, really. You may find some things get finished quicker while others take longer, however.
"is it hard to code for the allowance of graphics in a separate window." - not hard, but time-consuming. You need to develop a protocol for exchanging these graphics and write the interface for displaying them. Java is one platform you could use for this. I personally might use wxWindows. Although I'd also be tempted to see if much of what you want to do can be approximated with MXP so that you can use an existing client such as ZMud for testing and prototyping at least.
|