• File size measurements show the distribution of size of files.
• Files are classified in four categories based on their size (lines of code): 1-100 (very small files), 101-200 (small files), 201-500 (medium size files), 501-1000 (long files), 1001+(very long files).
• It is a good practice to keep files small. Long files may become "bloaters", code that have increased to such gargantuan proportions that they are hard to work with.

• There are 48 files with 6,028 lines of code.
• 1 very long files (1,331 lines of code)
• 1 long files (667 lines of code)
• 6 medium size files (1,571 lines of codeclsfd_ftr_w_mp_ins)
• 9 small files (1,279 lines of code)
• 31 very small files (1,180 lines of code)

There are 14 files with lines longer than 120 characters. In total, there are 34 long lines.

File	# lines	# units	# long lines
Client.cs in GameLiftExampleUnityProject/Assets/Scripts/Client	191	9	4
Server.cs in GameLiftExampleUnityProject/Assets/Scripts/Server	413	23	4
deployBuildAndUpdateGameLiftResources.ps1 in FleetDeployment	35	-	4
deployPreRequirements.ps1 in FleetDeployment	28	-	4
Client.cpp in CppServerAndClient/Client	147	3	4
NetworkPlayer.cs in GameLiftExampleUnityProject/Assets/Scripts/NetworkingShared	122	13	3
deploy.ps1 in GameServiceAPI	12	-	2
MatchmakingClient.cs in GameLiftExampleUnityProject/Assets/Scripts/Client	114	4	2
MessageClasses.cs in GameLiftExampleUnityProject/Assets/Scripts/NetworkingShared	42	3	2
processmatchmakingevents.js in GameServiceAPI/gameservice	38	-	1
NetworkClient.cs in GameLiftExampleUnityProject/Assets/Scripts/Client	203	15	1
asset Physics2DSettings.asset in GameLiftExampleUnityProject/ProjectSettings	56	-	1
asset DynamicsManager.asset in GameLiftExampleUnityProject/ProjectSettings	34	-	1
gamelift.yaml in FleetDeployment	146	-	1