I have been working on a game and brought a few others in on it to develop it and make content. The team is currently unpaid (will be compensated after release/funding)
In this setting, what do you think are some good practices to follow to make the project a success and a good development environment?
The project is still early in development and I would consider this to be my first leading role in something like this
Managing vs Leading:
As I am pretty directly involved in the development of things, from story to design to actual coding, I have tried to steer clear of 'managing', or over-managing as its a small team and nobody is seeing the $$$ to put up with much BS.
I think I have mostly done this with some success, but it has made it difficult for me at times. I have tried taking less of the front seat and letting everyone pedal as well, but I found that people didn't really have much drive to contribute anything unless it was adding to something that I created or was already there.
So far I have created a wiki, a forum, a Google drive, and set up some other tools for the team, as well as a Facebook page and have managed the security of our information (like making everything non-public)
Legal stuff - NDA/other agreements:
When is the best time to do the formalities and write up things like NDA's and other agreements to protect the project? Gauging my team as it is, I think they would not be keen on signing things like this - it seems to be a big turn-off when I start talking about rules and organization. I can understand the reticence as it is unpaid, but it also seems very risky in thinking of the future. I have already had a developer leave the project, and I have yet to see if problems are going to arise from this.
I know these types of things are very standard for larger projects with funding, but it seems difficult to implement in this setting. I have read many stories of failed games due to petty internal conflicts, developers retracting their contributions, misappropriated funding, and dissatisfied developers that probably could have been prevented if everyone had some type of written, formal agreement adhering to some rules of conduct.
I dont see agreements and NDA's as an attempt to disadvantage people or deprive them of freedom, but as something to protect the project as a whole - which is bigger than any one person and affects everyone.
Is it a good idea to put write something up and get some signatures? If so, when is a good time and what would be the best approach (as far as selling it to the team)? Should any agreement be very light and plain, or well written and very detailed?
I recently had started making a game and invited some others to join the team as well to create content and write some of the story. The group is small, and there is no funding currently.
The problem I am having is that I have a vision in mind for the game, but have some difficulty getting others to follow it - it follows certain themes and there are certain things about the world that cannot be changed without it being out of place or disrupting the 'feel' of the game.
I have so far been running things fairly casually as it is still a small unpaid team, but there are some things I feel that can't be compromised on. Don't get me wrong, I don't want to stifle my developers' creativity and I welcome new ideas/changes (we have had several good brainstorms in the past) but I think there needs to be a line somewhere so the game stays close to this vision.
In this example, the game is going to be dark fantasy, and have a rather serious environment, but I have a developer who wanted to add silly easter eggs in as 'comic relief'. When I asked for an example or something similar, he talked about how Saint's Row has some sort of dildo bat that you can use as a weapon in-game. This is very much something I did not want in the game and I had to draw a very firm line there, telling him we are not going to have anything like that (for the reasons above). He said something along the lines of "Well, I am going to put whatever I want in my level". Following that, I had a conversation with him where I told him that while he is in charge of that level, if it is out of place from the theme/doesnt fit in to the 'feel' of the game, that I won't allow it in the game.
The developer then told me I am taking things too seriously, I am thinking too far ahead, and it is not fun to develop the game anymore - he decided to leave the project. I definitely do like to have fun working on this game, and value the input of all my team, but I think there are times when I need to 'get serious'
I am very compromising with a lot of the story and design aspects, as the team is small and unpaid, but do not want to see this game run wild and turned into a joke. I am close to the design and story myself, and consider myself to fulfill the roles of a creative director and project manager - along with a bit of everything else. In the past, when the game was basically a blank slate, I tried to gather people around to come up with new ideas, but there was little contribution and I am seeing much more involvement after I went ahead and created a foundation of the story myself. I do my best to avoid coming off as 'managing' but it has been unavoidable in cases like this.
If you have read thus far, thanks for staying with me!
My question for you all - What is your opinion on this, what are some suggestions you have to avoid this in the future? I have some people with great Ideas and conflict is inevitable.
Do I need to be more picky with/vet developers better? Is there something dysfunctional in how I am approaching the matter? How do you work with your content authors/designers/developers to resolve creative conflict, and where do you draw the line?
Note: Usually I let a lot of stuff go that doesn't completely 'fit the vision', and adapt to it, in order to keep morale up and not stifle others' creativity, but knowing the guy personally, I suspect he had wanted to have a lot more control over the project and I had a feeling that something like this would develop down the road which is why I wanted to nip the problem early on.
A big game project contains a lot of runtime data like
List of all world objects List of all players Game states Viewport ... I have to pass a lot of these data to most of my classes. So I have a huge list of parameters in every constructor.
What's the best practice to avoid this mass of parameters? Is it recommended to summarize all data to one class (something like "GameData") and pass this container to all methods and classes? Is there a common name for this container in game development? I'm a bit worried, because if I pass this class to all classes and methods, I get something like a global variable.
Thanks a lot for your advice!
Good day dear people
I'm completely new here and very nervous to be honest. I started with 3D-Design at my traineeship and can slowly start with my ideas for a survival/rpg game in 3d But since I only used RPG Makers until now I wonder how is the best way to start with a game, and what I would need for that.
Have a wonderful day! ^.^)/)
COMPANY AND THE PROJECT
We are an indie game studio consisted of professional and friendly people. Additionally, we are a team of skilled artists and dedicated indie enthusiasts. Our current project is INT, developed on Unity Engine 5 for platforms Windows, Linux, and Mac.
INT is a 3D Sci-fi RPG with a strong emphasis on story, role playing, and innovative RPG features such as randomized companions. The focus is on the journey through a war-torn world with fast-paced combat against hordes of enemies. The player must accomplish quests like a traditional RPG, complete objectives, and meet lively crew members who will aid in the player's survival. Throughout the game you can side and complete missions through criminal cartels, and the two major combatants, the UCE and ACP, of the Interstellar Civil War.
Please note that all of our current positions are remote work. You will not be required to travel.
For more information about us, follow the links listed below.
INT Official website
Also follow social media platforms for the latest news regarding our projects.
We are looking for a serious and dedicated Community Manager, who will be tasked with providing regular community updates, and grow our fan base in preparation for our funding campaign.
Duties and Responsibilities:
Promote the INT Project through multiple Social Media outlets (E.G. Reddit, twitter, Facebook). Coordinate and work with our web admin to provide content directly to the website. Create regular updates with team highlights. This update will be shared to the broader community on IndieDB, Steam, and official INT website. Attend developer meetings and interact with the team and Project Lead to obtain highlights and material that can be used in updates. Map and manage social media analytics and report updates at team meetings. Manage and potentially host monthly INT Project podcast known as ‘RogueSpace’ and manage the INT Project’s twitch account. REQUIREMENTS
Advanced fluency in written English. Able to structure and create informative and visually attractive articles. Excellent self-management skills. Excellent communications skills, both verbal and written. Preferred
Other Indie Game Developer experience. Be an avid gamer. Have played a broad collection of titles; in sync with the latest news in gaming. REVENUE-SHARE
This is a great opportunity to get into the game development industry. Being an Indie team we do not have the creative restrictions often imposed by publishers or other third parties. We are extremely conscientious of our work and continuously uphold a high level of quality throughout our project.
We are unable to offer wages or per-item payments at this time. However revenue-sharing from crowd-funding is offered to team members who contribute 15-20 hours per week to company projects, as well as maintain constant communication and adhere to deadlines. Currently the crowd-funding campaign is scheduled for the year 2018. Your understanding is dearly appreciated.
Please send your Cover Letter, CV, Portfolio (if applicable), and other relevant documents/information to this email: JohnHR@int-game.net
Thank you for your time! We look forward to hearing from you!
Starboard Games LLC