# I'm starting as an indie ! Any advices ?

## Recommended Posts

Hi everyone !

Starting this month, i will be working my personal projects for a year at least. My goal is to release a game and an album before this deadline.

I am :

- A former game designer by degree (3 years)
- Half a programer (i did only 2/4 years)
- Semi self-taught graphist (during my formation as a game designer and afterward)
- Basic 2D animator (i took drawing and 2d animation evening classes)
- Self-taught music composer/producer (my soundcloud ==> https://soundcloud.com/amerjongleur but i didn't post for a while now)


My game is already advanced because i've been working on it now and then for a year already, but it's far from over. It's a small scale game, 1 room, 1 character, maybe less than two hours long, don't think i'll sell it for more than 2 euros.

I use :

- Unity as game engine
- Adobe illustrator/photoshop for the graphics
- Spriter pro for the animations
- Ableton live for the music


I'm looking for every advice i can get from you guys. I'm learning and discovering a lot of things by myself everyday but feel free to share your experience with me and talk about how you started working on your own projects and how it ended up. I'm actually kinda confident for the game itself. My biggest fear is communication. I'm really not a natural to the process and i'm not confident in getting my game noticed once it's done. I'm really looking forward advices on this matter. I'm from France and i think i can send demos and screens to the locals streamers and journalists but i don't know how to not make it a complete flop on steam.

I posted a similar topic on reddit and i've been adviced to start communication right now, to build a community up before the release of the game, which make sense. But how should i properly do that since i don't have much more than a concept and some screenshots/arts to show the world.
Should i get to people like "i have this game about this theme with those artworks, share it if you find it intresting" ? Seems a bit thin to me but i might be wrong. Tell me what you think !

Thanks in advance and have a nice day !

##### Share on other sites

What is a "graphist"?  An artist?

On 9/5/2017 at 0:23 AM, Amer Jongleur said:

But how should i properly do that since i don't have much more than a concept and some screenshots/arts to show the world.

You can advertise at literally any stage in development as long as your methods are in line with how much you have to show.  Don't hype it up and then only show a concept and a sketch of a map.  If you have very little to show, a simple blog post is appropriate.  Once you have more, you can advertise it more aggressively.  If you want to advertise it across several forums and sites, at the very minimum you must have something playable on your side.  That doesn't mean you have to let people play, it means that you have a working prototype or game from which you can take enough screenshots to warrant people's time.

I would generally say common sense should guide you.  Don't pester people unless it is worth their time.  That means that at this time, with what you have, it is definitely not okay to pester people with requests to "share if you find it interesting."

L. Spiro

##### Share on other sites
On 08/09/2017 at 11:16 PM, L. Spiro said:

What is a "graphist"?  An artist?

Yeah ! It's just that i lack of technical skills that are usually required from a real artist, because it wasn't my job in the first place. I'm just good at making clever use of simple visual techniques and arrangements like the cover art of Justice - Cross.
That's why i don't use the word artist, i just do clever tricks and try my best to avoid my flaws when it comes to graphic design.

Thanks for the advice. I started a tweeter account in that purpose. I'm only sharing my progression in the visual parts at the moment, since it's the more remarkable for now. I just let people who are intrigued by what they see follow the progression. But my intentions are definitely not to do any kind of forcing right now, since i don't have enough tangible content to share.
But i hope this step will come soon enough.

Thanks again and have a nice day.

##### Share on other sites

You might want to wait until you have a better idea of what your game will be, and have something to show, before starting to think about a "community" and all that.  When you're just starting out, you have a ton of things to think about and to do.  Focus on those things and set some milestones, then see if you're meeting those.  Are you still working on this a month from now?  Six months from now?  Is your game idea coming into focus the more you work on it, or falling apart?  Trying to get people interested in your project before you even have a project is just going to be a waste of your time, and will probably also bring you a lot of aggravation.

##### Share on other sites

I understand that and it's mainly the reason why i didn't go out of my cave earlier. I've actually been working on this project as a hobby for a year already and it went through different conceptual approaches. It was evolving too much, too quickly, was too unstable to be talked about properly since it wasn't that concrete or solid during that period.
But now it's starting to come together nicely from a game design perspective. I hope that in a month, the design will be settle (it kinda is now, but there are still small areas of shadows/not-fully-working mechanics in micro design parts).

I even considered waiting longer before starting talking about it (like waiting to have advanced/final props to show and all) but i've been adviced not too since i now know what the game is going to be at this point.
That's why i thought it was the time to start promoting it.

##### Share on other sites

A functioning small demo of your game and a video of your product should be a goal to achieve and hopefully get noticed. It's a small step that should help you along on your game development path and get the input you will need.

##### Share on other sites

Insightful article. I've been through a lot of the things you point out.

Three years of disappointing student projects, and my final year project being a total failure due mainly to lack of team motivation, cohesion and organization led me to the idea of not relying on the others that much from a developpement perspective.
Even in a semi-pressured context such as school (diploma, start of career...) , people weren't that involved after all. So let's not even talk about my attempts at internet indie projects...
Industry kinda disappointed me also for its lack of creativity, risk-taking and ability to get me excited/fulfilled overall.

Those are the reasons why i put myself out of the "idea guy" zone and decided to fight on all front in this indie project.
A lot of the things you said to be really careful about i had naturally in mind, from the small scope to the planning.
It's really small, maybe less than an hour long, one character, one room, 2D, price would be less than 5€ for sure. Final game design is due to the end of october and a quick demo for christmas. Content and polish until summer 2018, expected release.
I'm 90% confident that the final game will be interesting and wil stand out among the rest. A bit less for its acutal making, since i'm discovering a lot of concepts at once and i will surely make mistakes (atmosphere, juicyness, visual harmony, lightings and animation mainly).

My worst fear really is communication, marketing and sells. I'm now also 90% confident my game will be missed and forgotten when it's released and that i will sell about 10 copies. I obviously want to decrease that percentage as much as possible.
I'm naturally the opposite of an entrepreneur, i'm naturally bad at involving other people in my projects and i'm naturally bad at communication. But school projects and relationships made me improve on those two last points so it's really not definitive, it just need work and effort on my part.
I kinda have a strong ego that regularly puts in my mind ideas like : "I don't have to communicate or promote because i'm a genius and it's up to the people to follow my actions because everything i do is awesome and they are the ones who will benefit from being in the wake of my awesome character".
I'm aware this is toxic and counter-productive thinking unless you're Kanye West, so i try my best fighting it. But it still results in me not having any good ideas in the domain most of the time.
i started a tweeter where i share work and progression and i can think about people, journalists and streamers to send my demo to when it's ready to get them hyped but beside that (and if i get ignored or don't get the interest of those people), i literally have no idea on how to get my game noticed.

I already read articles only saying that you should quickly promote and build a community  without discussing how to actually do it...

I have no marketing budget whatsoever, just time. I don't know jack about communication beside creating pages and accounts on social medias. I tried spamming methods with my music but i don't like it very much and usually get ignored. I like the concept of thunderclap and plan to use it. And i think that wraps up my communication abilities.

So if you have any article, link, or advice on this matter,  it would be greatly appreciated.
Thanks a lot.

##### Share on other sites

I wrote an article about ideas guys back in May this year from my own frustrations with dealing with those types of individuals. You have to clear out any dead weight sometimes because most view game development as "I will set back and give my input and that should be good enough" but they will never go through the trenches themselves when it comes to game development. As for marketing well all you can do is possibly go viral but there isn't a simple answer out there to get your game noticed. Just throw them up on forums, YouTube, social media and get feedback.

##### Share on other sites

Even if i kinda saw things this way before jumping into my game designer formation, i've never had the possibility to be just an idea guy myself. Since the first school project, there was way too much to do to stick to ideas or even documents. I've always had to do other stuff in order to get things done in time, from scripting to 3D modeling. That's partially how i've ended being able to do a bit of everything after five years in school. But i saw a lot of them in group projects, the only presence they have is in brainstorming. Even if sometimes, some have actual very good ideas, they are useless in production or rush period, which is a huge problem ^^

For the marketing, i've been reading a lot of articles and will continue to do so, i have a better idea of what to do now. I'll keep communication up until i have enough content to make a trailer, then i'll start sending to journalists, bloggers...
Then i'll see what happens

##### Share on other sites

I'd agree that exposure is key; You may get feedback on things that people dislike in what you have so far, or what they think is awesome and want to see more of. If you put out a cool game, but no one knows about it, it will be like a drop of water in the ocean.

## Create an account

Register a new account

• 31
• 11
• 17
• 11
• 13
• ### Similar Content

• hello, I am trying to implement a realistic simulation of a roulette wheel. it is not clear for me what is the proper way to simulate the initial status of the ball, when it spins against the edge of the wheel until it loss energy and start falling towards the centre.
I modelled the conic table as a height map, as I assume that would provide the smoother surface. but I see anyway there is rough squared corners everywhere, so really I don't have a smooth inner wall to slide against.
I wonder if I should ignore the wall and simulate the sliding by code. i.e: apply force (or impulse?) each frame to keep the ball at a fixed radius and somehow force it to follow a desired angular speed..  later, when I want to execute the falling behaviour, just stop applying that forces and let the simulator and the gravity do their work.. makes sense?

• I'm having some difficulty understanding how data would flow or get inserted into a multi-threaded opengl renderer where there is a thread pool and a render thread and an update thread (possibly main). My understanding is that the threadpool will continually execute jobs, assemble these and when done send them off to be rendered where I can further sort these and achieve some cheap form of statelessness. I don't want anything overly complicated or too fine grained,  fibers,  job stealing etc. My end goal is to simply have my renderer isolated in its own thread and only concerned with drawing and swapping buffers.
My questions are:
1. At what point in this pipeline are resources created?
Say I have a
class CCommandList { void SetVertexBuffer(...); void SetIndexBuffer(...); void SetVertexShader(...); void SetPixelShader(...); } borrowed from an existing post here. I would need to generate a VAO at some point and call glGenBuffers etc especially if I start with an empty scene. If my context lives on another thread, how do I call these commands if the command list is only supposed to be a collection of state and what command to use. I don't think that the render thread should do this and somehow add a task to the queue or am I wrong?
Or could I do some variation where I do the loading in a thread with shared context and from there generate a command that has the handle to the resources needed.

2. How do I know all my jobs are done.
I'm working with C++, is this as simple as knowing how many objects there are in the scene, for every task that gets added increment a counter and when it matches aforementioned count I signal the renderer that the command list is ready? I was thinking a condition_variable or something would suffice to alert the renderthread that work is ready.

3. Does all work come from a singular queue that the thread pool constantly cycles over?
With the notion of jobs, we are basically sending the same work repeatedly right? Do all jobs need to be added to a single persistent queue to be submitted over and over again?

4. Are resources destroyed with commands?
Likewise with initializing and assuming #3 is correct, removing an item from the scene would mean removing it from the job queue, no? Would I need to send a onetime command to the renderer to cleanup?
• By devbyskc
Hi Everyone,
Like most here, I'm a newbie but have been dabbling with game development for a few years. I am currently working full-time overseas and learning the craft in my spare time. It's been a long but highly rewarding adventure. Much of my time has been spent working through tutorials. In all of them, as well as my own attempts at development, I used the audio files supplied by the tutorial author, or obtained from one of the numerous sites online. I am working solo, and will be for a while, so I don't want to get too wrapped up with any one skill set. Regarding audio, the files I've found and used are good for what I was doing at the time. However I would now like to try my hand at customizing the audio more. My game engine of choice is Unity and it has an audio mixer built in that I have experimented with following their tutorials. I have obtained a great book called Game Audio Development with Unity 5.x that I am working through. Half way through the book it introduces using FMOD to supplement the Unity Audio Mixer. Later in the book, the author introduces Reaper (a very popular DAW) as an external program to compose and mix music to be integrated with Unity. I did some research on DAWs and quickly became overwhelmed. Much of what I found was geared toward professional sound engineers and sound designers. I am in no way trying or even thinking about getting to that level. All I want to be able to do is take a music file, and tweak it some to get the sound I want for my game. I've played with Audacity as well, but it didn't seem to fit the bill. So that is why I am looking at a better quality DAW. Since being solo, I am also under a budget contraint. So of all the DAW software out there, I am considering Reaper or Presonus Studio One due to their pricing. My question is, is investing the time to learn about using a DAW to tweak a sound file worth it? Are there any solo developers currently using a DAW as part of their overall workflow? If so, which one? I've also come across Fabric which is a Unity plug-in that enhances the built-in audio mixer. Would that be a better alternative?
I know this is long, and maybe I haven't communicated well in trying to be brief. But any advice from the gurus/vets would be greatly appreciated. I've leaned so much and had a lot of fun in the process. BTW, I am also a senior citizen (I cut my programming teeth back using punch cards and Structured Basic when it first came out). If anyone needs more clarification of what I am trying to accomplish please let me know.  Thanks in advance for any assistance/advice.

• The more you know about a given topic, the more you realize that no one knows anything.
For some reason (why God, why?) my topic of choice is game development. Everyone in that field agrees: don't add networked multiplayer to an existing game, you drunken clown.
Well, I did it anyway because I hate myself. Somehow it turned out great. None of us know anything.
Problem #1: assets
My first question was: how do I tell a client to use such-and-such mesh to render an object? Serialize the whole mesh? Nah, they already have it on disk. Send its filename? Nah, that's inefficient and insecure. Okay, just a string identifier then?
Fortunately, before I had time to implement any of my own terrible ideas, I watched a talk from Mike Acton where he mentions the danger of "lazy decision-making". One of his points was: strings let you lazily ignore decisions until runtime, when it's too late to fix.
If I rename a texture, I don't want to get a bug report from a player with a screenshot like this:

I had never thought about how powerful and complex strings are. Half the field of computer science deals with strings and what they can do. They usually require a heap allocation, or something even more complex like ropes and interning. I usually don't bother to limit their length, so a single string expands the possibility space to infinity, destroying whatever limited ability I had to predict runtime behavior.
And here I am using these complex beasts to identify objects. Heck, I've even used strings to access object properties. What madness!
Long story short, I cultivated a firm conviction to avoid strings where possible. I wrote a pre-processor that outputs header files like this at build time:
namespace Asset { namespace Mesh { const int count = 3; const AssetID player = 0; const AssetID enemy = 1; const AssetID projectile = 2; } } So I can reference meshes like this:
renderer->mesh = Asset::Mesh::player; If I rename a mesh, the compiler makes it my problem instead of some poor player's problem. That's good!
The bad news is, I still have to interact with the file system, which requires the use of strings. The good news is the pre-processor can save the day.
const char* Asset::Mesh::filenames[] = { "assets/player.msh", "assets/enemy.msh", "assets/projectile.msh", 0, }; With all this in place, I can easily send assets across the network. They're just numbers! I can even verify them.
if (mesh < 0 || mesh >= Asset::Mesh::count) net_error(); // just what are you trying to pull, buddy? Problem #2: object references
My next question was: how do I tell a client to please move/delete/frobnicate "that one object from before, you know the one". Once again, I was lucky enough to hear from smart people before I could shoot myself in the foot.
From the start, I knew I needed a bunch of lists of different kinds of objects, like this:
Array<Turret> Turret::list; Array<Projectile> Projectile::list; Array<Avatar> Avatar::list; Let's say I want to reference the first object in the Avatar list, even without networking, just on our local machine. My first idea is to just use a pointer:

Avatar* avatar; avatar = &Avatar::list[0]; This introduces a ton of non-obvious problems. First, I'm compiling for a 64 bit architecture, which means that pointer takes up 8 whole bytes of memory, even though most of it is probably zeroes. And memory is the number one performance bottleneck in games.
Second, if I add enough objects to the array, it will get reallocated to a different place in memory, and the pointer will point to garbage.
Okay, fine. I'll use an ID instead.
template<typename Type> struct Ref { short id; inline Type* ref() { return &Type::list[id]; } // overloaded "=" operator omitted }; Ref<Avatar> avatar = &Avatar::list[0]; avatar.ref()->frobnicate(); Second problem: if I remove that Avatar from the list, some other Avatar will get moved into its place without me knowing. The program will continue, blissfully and silently screwing things up, until some player sends a bug report that the game is "acting weird". I much prefer the program to explode instantly so I at least get a crash dump with a line number.
Okay, fine. Instead of actually removing the avatar, I'll put a revision number on it:
struct Avatar { short revision; }; template<typename Type> struct Ref { short id; short revision; inline Type* ref() { Type* t = &Type::list[id]; return t->revision == revision ? t : nullptr; } }; Instead of actually deleting the avatar, I'll mark it dead and increment the revision number. Now anything trying to access it will give a null pointer exception. And serializing a reference across the network is just a matter of sending two easily verifiable numbers.
Problem #3: delta compression
Which by the way is here: gafferongames.com
As I set out to implement my own version of Glenn's netcode, I read this article, which details one of the biggest challenges of multiplayer games. Namely, if you just blast the entire world state across the network 60 times a second, you could gobble up 17 mbps of bandwidth. Per client.
Delta compression is one of the best ways to cut down bandwidth usage. If a client already knows where an object is, and it hasn't moved, then I don't need to send its position again.
This can be tricky to get right.

The first part is the trickiest: does the client really know where the object is? Just because I sent the position doesn't mean the client actually received it. The client might send an acknowledgement back that says "hey I received packet #218, but that was 0.5 seconds ago and I haven't gotten anything since."
So to send a new packet to that client, I have to remember what the world looked like when I sent out packet #218, and delta compress the new packet against that. Another client might have received everything up to packet #224, so I can delta compress the new packet differently for them. Point is, we need to store a whole bunch of separate copies of the entire world.
Someone on Reddit asked "isn't that a huge memory hog"?
No, it is not.
Actually I store 255 world copies in memory. All in a single giant array. Not only that, but each copy has enough room for the maximum number of objects (2048) even if only 2 objects are active.
If you store an object's state as a position and orientation, that's 7 floats. 3 for XYZ coordinates and 4 for a quaternion. Each float takes 4 bytes. My game supports up to 2048 objects. 7 floats * 4 bytes * 2048 objects * 255 copies = ...
14 MB. That's like, half of one texture these days.
I can see myself writing this system five years ago in C#. I would start off immediately worried about memory usage, just like that Redditor, without stopping to think about the actual data involved. I would write some unnecessary, crazy fancy, bug-ridden compression system.
Taking a second to stop and think about actual data like this is called Data-Oriented Design. When I talk to people about DOD, many immediately say, "Woah, that's really low-level. I guess you want to wring out every last bit of performance. I don't have time for that. Anyway, my code runs fine." Let's break down the assumptions in this statement.
Assumption 1: "That's really low-level".
Look, I multiplied four numbers together. It's not rocket science.
Assumption 2: "You sacrifice readability and simplicity for performance."
Let's picture two different solutions to this netcode problem. For clarity, let's pretend we only need 3 world copies, each containing up to 2 objects.
Here's the solution I just described. Everything is statically allocated in the .bss segment. It never moves around. Everything is the same size. No pointers at all.

Here's the idiomatic C# solution. Everything is scattered randomly throughout the heap. Things can get reallocated or moved right in the middle of a frame. The array is jagged. 64-bit pointers all over the place.

Which is simpler?
The second diagram is actually far from exhaustive. C#-land is a lot more complex in reality. Check the comments and you'll probably find someone correcting me about how C# actually works.
But that's my point. With my solution, I can easily construct a "good enough" mental model to understand what's actually happening on the machine. I've barely scratched the surface with the C# solution. I have no idea how it will behave at runtime.
Assumption 3: "Performance is the only reason you would code like this."
To me, performance is a nice side benefit of data-oriented design. The main benefit is clarity of thought. Five years ago, when I sat down to solve a problem, my first thought was not about the problem itself, but how to shoehorn it into classes and interfaces.
I witnessed this analysis paralysis first-hand at a game jam recently. My friend got stuck designing a grid for a 2048-like game. He couldn't figure out if each number was an object, or if each grid cell was an object, or both. I said, "the grid is an array of numbers. Each operation is a function that mutates the grid." Suddenly everything became crystal clear to him.
Assumption 4: "My code runs fine".
Again, performance is not the main concern, but it's important. The whole world switched from Firefox to Chrome because of it.
Try this experiment: open up calc.exe. Now copy a 100 MB file from one folder to another.

I don't know what calc.exe is doing during that 300ms eternity, but you can draw your own conclusions from my two minutes of research: calc.exe actually launches a process called Calculator.exe, and one of the command line arguments is called "-ServerName".
Does calc.exe "run fine"? Did throwing a server in simplify things at all, or is it just slower and more complex?
I don't want to get side-tracked. The point is, I want to think about the actual problem and the data involved, not about classes and interfaces. Most of the arguments against this mindset amount to "it's different than what I know".
Problem #4: lag
I now hand-wave us through to the part of the story where the netcode is somewhat operational.
Right off the bat I ran into problems dealing with network lag. Games need to respond to players immediately, even if it takes 150ms to get a packet from the server. Projectiles were particularly useless under laggy network conditions. They were impossible to aim.
I decided to re-use those 14 MB of world copies. When the server receives a command to fire a projectile, it steps the world back 150ms to the way the world appeared to the player when they hit the fire button. Then it simulates the projectile and steps the world forward until it's up to date with the present. That's where it creates the projectile.
I ended up having the client create a fake projectile immediately, then as soon as it hears back from the server that the projectile was created, it deletes the fake and replaces it with the real thing. If all goes well, they should be in the same place due to the server's timey-wimey magic.
Here it is in action. The fake projectile appears immediately but goes right through the wall. The server receives the message and fast-forwards the projectile straight to the part where it hits the wall. 150ms later the client gets the packet and sees the impact particle effect.

The problem with netcode is, each mechanic requires a different approach to lag compensation. For example, my game has an "active armor" ability. If players react quick enough, they can reflect damage back at enemies.

This breaks down in high lag scenarios. By the time the player sees the projectile hitting their character, the server has already registered the hit 100ms ago. The packet just hasn't made it to the client yet. This means you have to anticipate incoming damage and react long before it hits. Notice in the gif above how early I had to hit the button.
To correct this, the server implements something I call "damage buffering". Instead of applying damage instantly, the server puts the damage into a buffer for 100ms, or whatever the round-trip time is to the client. At the end of that time, it either applies the damage, or if the player reacted, reflects it back.
Here it is in action. You can see the 200ms delay between the projectile hitting me and the damage actually being applied.

Here's another example. In my game, players can launch themselves at enemies. Enemies die instantly to perfect shots, but they deflect glancing blows and send you flying like this:

Which direction should the player bounce? The client has to simulate the bounce before the server knows about it. The server and client need to agree which direction to bounce or they'll get out of sync, and they have no time to communicate beforehand.
At first I tried quantizing the collision vector so that there were only six possible directions. This made it more likely that the client and server would choose the same direction, but it didn't guarantee anything.
Finally I implemented another buffer system. Both client and server, when they detect a hit, enter a "buffer" state where the player sits and waits for the remote host to confirm the hit. To minimize jankiness, the server always defers to the client as to which direction to bounce. If the client never acknowledges the hit, the server acts like nothing happened and continues the player on their original course, fast-forwarding them to make up for the time they sat still waiting for confirmation.
Problem #5: jitter
My server sends out packets 60 times per second. What about players whose computers run faster than that? They'll see jittery animation.
Interpolation is the industry-standard solution. Instead of immediately applying position data received from the server, you buffer it a little bit, then you blend smoothly between whatever data that you have.
In my previous attempt at networked multiplayer, I tried to have each object keep track of its position data and smooth itself out. I ended up getting confused and it never worked well.
This time, since I could already easily store the entire world state in a struct, I was able to write just two functions to make it work. One function takes two world states and blends them together. Another function takes a world state and applies it to the game.
How big should the buffer delay be? I originally used a constant until I watched a video from the Overwatch devs where they mention adaptive interpolation delay. The buffer delay should smooth out not only the framerate from the server, but also any variance in packet delivery time.
This was an easy win. Clients start out with a short interpolation delay, and any time they're missing a packet to interpolate toward, they increase their "lag score". Once it crosses a certain threshold, they tell the server to switch them to a higher interpolation delay.
Of course, automated systems like this often act against the user's wishes, so it's important to add switches and knobs to the algorithm!

Problem #6: joining servers mid-match
Wait, I already have a way to serialize the entire game state. What's the hold up?
Turns out, it takes more than one packet to serialize a fresh game state from scratch. And each packet may take multiple attempts to make it to the client. It may take a few hundred milliseconds to get the full state, and as we've seen already, that's an eternity. If the game is already in progress, that's enough time to send 20 packets' worth of new messages, which the client is not ready to process because it hasn't loaded yet.
The solution is—you guessed it—another buffer.
I changed the messaging system to support two separate streams of messages in the same packet. The first stream contains the map data, which is processed as soon as it comes in.
The second stream is just the usual fire-hose of game messages that come in while the client is loading. The client buffers these messages until it's done loading, then processes them all until it's caught up.
Problem #7: cross-cutting concerns
This next part may be the most controversial.
Remember that bit of gamedev wisdom from the beginning? "don't add networked multiplayer to an existing game"?
Well, most of the netcode in this game is literally tacked on. It lives in its own 5000-line source file. It reaches into the game, pokes stuff into memory, and the game renders it.
Just listen a second before stoning me. Is it better to group all network code in one place, or spread it out inside each game object?
I think both approaches have advantages and disadvantages. In fact, I use both approaches in different parts of the game, for various reasons human and technical.
But some design paradigms (*cough* OOP) leave no room for you to make this decision. Of course you put the netcode inside the object! Its data is private, so you'll have to write an interface to access it anyway. Might as well put all the smarts in there too.
Conclusion
I'm not saying you should write netcode like I do; only that this approach has worked for me so far. Read the code and judge for yourself.
There is an objectively optimal approach for each use case, although people may disagree on which one it is. You should be free to choose based on actual constraints rather than arbitrary ones set forth by some paradigm.

• I am animator by hand, and i am doing game animation for at least 8 years so far. During the last 2 years, i came with a idea for game and maybe some day, i want to start indie game company. As i am thinking to start game company, i am also thinking what kind of value i can give to the company. For example, am experience in animation,sales(I was selling web development services, before i jumped to gaming), bit of rigging- just not for production, i am learning on the side as well. The rest of the gaming production, like modeling, concept art, texturing, i am total noob or to say better, i am no near interest to do modeling for example, don't have such a patience to do it. But before characters and things are made for animating, what the hell i am would do?
Also, what is the ideal size of the founding team of a game company? Positions to be filled mostly are, Concept artist, Modeler/Texture artist, programmer, animator-rigger. And later would need more people to join, like more animators, programmers, sound, fx,etc.

And lastly, do i need to have something,like a prototype, to show people and get them interest, or should i ask someone i know, for skill that i lack, for example, Modeling would be great, texturing and rigging, and to start all together from scratch?