fpsware
Community Developer
- Joined
- Jan 15, 2010
- Messages
- 5,287
- Reaction score
- 133
As some of you may already be aware I've been working on my new base CC template for a couple of weeks now. It is a complete rewrite of my 'core' system I use with all my CCs.
As part of the rewrite I've been developing it with generic reuseability in mind, to put it in laymans terms, it is as generic as possible and all class specific logic/code is segregated. This has resulted in an unexpected bonus for me, it lends itself very well to being implemented as a single CC or imbeded into a multi CC project.
Thus brings me to my question, do we need another all in one CC, do we need Fpsware Unity?
Regardless of how my new range of CCs are implemented they will look exactly the same, the UI will be no different if you are using a single CC or Unity. Maintaining this actually becomes much easier than if it were individual CCs, the core/common features exist as a single project and is used by all class specific CCs, the class specific files (3 logic files + Settings XMLs) are the only things that differ between them. Each class will still have the same "Fpsware CC" look and feel about it.
For those of you who have been around since the very early days this is a project I have undertaken before. The results at the time were .... mixed to say the least. The only thing that has changed now is knowledge and there are a lot more developers to spunge ideas from
Will this allow users to create logic files such as Singular does?
No.
Will this make development of CCs quicker?
YES! Utilizing the Unity framework I have been able to create a raid DPS capable Warlock for all THREE trees in about 2 hours - including testing. It does not have a UI, it does not have any customiseability its a straight out DPS machine.
As part of the rewrite I've been developing it with generic reuseability in mind, to put it in laymans terms, it is as generic as possible and all class specific logic/code is segregated. This has resulted in an unexpected bonus for me, it lends itself very well to being implemented as a single CC or imbeded into a multi CC project.
Thus brings me to my question, do we need another all in one CC, do we need Fpsware Unity?
Regardless of how my new range of CCs are implemented they will look exactly the same, the UI will be no different if you are using a single CC or Unity. Maintaining this actually becomes much easier than if it were individual CCs, the core/common features exist as a single project and is used by all class specific CCs, the class specific files (3 logic files + Settings XMLs) are the only things that differ between them. Each class will still have the same "Fpsware CC" look and feel about it.
For those of you who have been around since the very early days this is a project I have undertaken before. The results at the time were .... mixed to say the least. The only thing that has changed now is knowledge and there are a lot more developers to spunge ideas from

Will this allow users to create logic files such as Singular does?
No.
Will this make development of CCs quicker?
YES! Utilizing the Unity framework I have been able to create a raid DPS capable Warlock for all THREE trees in about 2 hours - including testing. It does not have a UI, it does not have any customiseability its a straight out DPS machine.
Last edited: