Home » FULL CONTROL GAMES » #JAFDEV » Open Source - The future of Flashback - or the future of a new game
Re: Open Source - The future of Flashback - or the future of a new game[message #340174 is a reply to message #340167] Sun, 22 March 2015 19:14 Go to previous messageGo to previous message
SceenOfDeath is currently offline SceenOfDeath

 
Messages:28
Registered:December 2007
Location: Germany
Yes you are right - but I like to have some basic assets so we can see whats needed and how to handle the animations.
So some basic assets / animations is still needed, I would like to see a almost full set of the needed animations
so we can build the animation system for it if we are at that point. (But we are at the planing right now)

The "main" basics - the core, path finding, event system, combat system, cam, stats etc need to be done first, after the big planing.

There is still the need for money of course, but I see more problems when we collect money
(even through donation) - like someone should collect everything and it must be official etc, and we can't buy any asset for just one person.
There is something needed like a small dev team - maybe even official - so we can share the assets. Sadly, the bought assets
are not possible to release in it's raw format, so only the people who have access to it can change them.
( This doesn't affect legal free assets )

But there are much to do if we want to have something which looks better than JA:F at Kickstarter,
we are still not working on it yet.

So I think we need a good plan how to start.

Maybe we should write our goal in small pieces, so we can take a piece and work on it to get a detailed version.
The goals could be split up in possible classes, after we are "done" with them, we collect them to a generally UML diagram.

With this generally diagram we have basically collected all needed classes at one diagram.

If we have the generally diagram, we need to define a much more detailed diagram of it,
so we need to split it again and work on each class again, so we are going to iterations of each diagram / class.

After we have a detail diagram for each possible "main" class, we could start to write code for it.

This isn't the most interesting thing I could imagine, but we need a very good plan and design
if we want to get good results without writing everything from scratch after an iteration.

This takes much time, if we just start to code we see some results in weeks, but it could happen that we
need to write them from scratch because the design of the class or what ever was bad at that beginning, so that's frustrating and some people are going to leave.

Report message to a moderator

Private 1st Class
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: JA:Flashback Mercenary Roster
Next Topic: Thee Jagged Alliance 3
Goto Forum:
  


Current Time: Sat Jun 13 02:02:14 GMT+3 2026

Total time taken to generate the page: 0.01607 seconds