You can view/download this whole message in a .pdf file by going to this link. Dl.dropbox.com
(Developed by Dark Water Game Studio)
Contact Information
Email: apply@darkwatergamestudio.com (email should be checked every 3 hours, if not wait 2 days then resend your email)
Please leave a reply to this thread if you have emailed us, and we will confirm that we have received your email.
Please do not PM this forum account as it will be sent to an unattended mailbox and not read. Even if it is read, we will ask you to resend to the email address supplied.
Previous Work by our team
We currently have another project in development, and that should be in beta soon. We don’t want to stress with two projects with the same team so we are starting a second team under the same name to continue working on this project. Here is the link to the previous project we were working on. Forums.epicgames.com
What every team member gets
Every team member will receive a team email and be added to the group chat. Also we will be sharing royalties after game is completed, the percentage of your earnings will depend on the amount of work you put into Dark Assassin.
How to apply
To apply please email us using the email provided above and include an application and images of your work. (Images of your work are required).
What we are looking for in a member of the team
You must have Skype for team communications and you must have Dropbox to share files both of these are free to download and register to.
We are looking for a member who knows his way around UDK and his position he is applying for. We also prefer that you have worked on a team before and know the work flow, even though that the work flow for each team will be different we just want you to have the general idea. You must also be respectful to each and every member of the team and have mature and appropriate conversations on the group chat via Skype group chat. You must also be willing to put your best effort into this project, we would rather not have a member on the team that is working on three or more projects.
Introduction
We started this project a while back, but stopped the development due to inactivity within the team and lack of programmers. We are now going to make a new approach and start a whole new team for this project. Some models are already made and ready to be put into the game. If you read the Pre-Production Plan you will see that we are going to create a simple test level first so our programmers can have scripts to play around with while the rest of the team develops the graphic and design aspects of the game. Testers now are not a high priority and I would rather have testers on the team that can also fill one of the other positions as well. Game design document is complete but is only shared to elder members of the team; you must show effort in order to receive the game design document. I will be working on a more user friendly game designer document embed into a wiki for only the team to be able to see if they are supplied with the username and password requested on our website.
What is Dark Assassin?
Dark assassin is a RPG being developed by Dark Water Game Studio; it will have FPS style combat, and the full RPG concept. Meaning you can do whatever you want there is no direct path you will have to follow. You start as a prison guard tricked by a prisoner held captive “The Dark Assassin”, which you then are lead to releasing her and then sentenced to the “council” in the game and you have to find and return the “Dark Assassin” to spare your life. This is a very rough description of the game and more has been drawn up, but I would rather not release whole game idea to the public for various reasons.
Questions
If you have any questions don’t be afraid to contact us by email and/or submit a reply with your regards, please use the email above to contact us our of the forum.
The first three chapters of the story will be available upon request by email, but the story will need to be re written by the creative writer(s) of the team.
"Dark Assassin" DEVELOPMENT PLAN
Not Game Design Document
Pre-production Plan
Please note this is a draft and does not contain everything that needs to be done we will take in suggestions and constructive criticism in order to grow the team therefore maybe taking away or adding features.
1. Team requirements
2. Gathering team members. (Better start with small number of members)
3. Role assignments. Role categories :
a. Programmers
b. Designers
i. Music Composer(s)/Artist(s)
ii. GUI Artist(s)
iii. Voice Actor(s) (must have the talent in music editing as well)
iv. Level Designer(s)
v. Concept Artist(s) (High Priority)
1. Enviermental Concept Artist(s)
2. Organic Concept Artist(s)
vi. Cartographer(s)
vii. Creative Writer(s)
c. Modeler(s)
i. Enviermental Modeler(s)
ii. Organic Modeler(s)
d. Animation Expert(s)
e. Game Tester(s)
4. Addressing general guidelines and info about the game. Issues should be addressed in the following order:
a. Short description of the game
b. game's genre
c. detailed game play description
d. features
e. setting
f. world map
g. story
h. target audience
i. hardware platforms
j. estimated schedule
5. Meetings of all team members to discuss issues from step 4 and address the following design guidelines and strategies :
a. Hero
i. Classes
ii. movements and actions
iii. abilities (Strength, Dexterity etc)
iv. skills (stealth skills, hunter skills, thieving skills etc)
v. role play system ( leveling, XP gathering, points distribution etc)
vi. …
b. Items
i. weapons (categories, properties etc)
ii. armor (categories, properties etc)
iii. magic items (categories, properties etc)
iv. quest items
v. other items (potions, consumables etc)
vi. …
c. Inventory
i. Structure - appearance
ii. Inventory categories (armor, weapons, magic, quest items, other items)
iii. Items in categories (e.g. swords, axes etc in weapons category, rings in armor category or in magic category)
iv. Inventory functions (equip, drop, examine etc)
d. enemies
i. Classes – categories
ii. A.I. (reactions to hero’s presence, attack strategies, path finding)
iii. …
e. NPCs
i. Categories (friendly – enemy)
ii. A.I. (path finding – enemy sighted)
iii. Important NPCs (quest givers, masters etc)
iv. …
f. Dialogs
i. in form of dialog trees
g. Levels design
i. levels names, place on map, importance etc
ii. NPCs locations
iii. Enemies locations
iv. items locations
v. props locations
vi. building locations
vii. …
Production
First, a tests level should be created where all models, scripts, mechanics etc will be tested. For most phases described below designers must make concept sketches, modelers will create animated and textured 3d models and finally programmers will integrate code:
1. Player character design
a. Hero model
b. Hero animation
c. Armor models
d. Hero properties (role playing system, abilities, skills etc)
e. Weapons
f. Movements and actions
2. Items (weapons and armor are created on player character design phase)
a. magic items
b. quest items
c. other items (keys, potions, letters etc)
3. Inventory
a. Inventory structure and functions
4. GUI
a. Life – Mana- XP indicators
b. Game messages (for level up, examine object etc)
c. quick slots
d. other info on screen GUI
5. interactive items (chests, boxes, hotspots)
6. Enemies
a. models
b. animations
c. AI
7. NPCs
a. models
b. animations
c. AI
8. dialogs trees
a. texts
b. texts assignment to NPC models
9. quests
a. quests code
10. Levels design
a. After all previous steps are completed, level design can commence
11. Audio
a. speech – dialogs
b. music
c. SFX
d. ambient sounds
12. Start kick starter to raise some money for advertisement and other needs for development (if raised enough money we may start paying members of the team)
13. Testing - bugs correction - Beta version- clean scripts and review code
14. Alpha BETA – Released to public for beta testing
15. General Release
a. Where will we sell the game
b. How will we sell the game
c. For how much will we sell the game
d. Advertisement
16. Royalties cut form total production value and distributed within the whole team, depending on the total work completed by the (designer, modeler, programmer, and or tester).
<!-- / message -->
