Difference between revisions of "About:Research Methods"

From Game Developer Research Institute
Jump to: navigation, search
Line 11: Line 11:
  
 
===Code comparisons===
 
===Code comparisons===
Thanks to a program developed especially for GDRI, we can perform code comparisons. This program can look at two different files and show what is shared between them. For our purposes, we can compare two ROMs for games we know to be by the same developer and see what code is shared between the two. From there, we can search for this shared data in other ROMs. If there's a significant amount of shared code in these other ROMs, there is a good possibility that these were programmed by the developer of the two games we originally compared.
+
Thanks to a program developed especially for GDRI, we can perform code comparisons. This program can look at two different files and show what is shared between them. For our purposes, we can compare two ROMs for games we know to be by the same developer and see what code is shared between the two. From there, we can search for this shared data in other ROMs. If there is a significant amount of shared code in these other ROMs, there is a good possibility that these were programmed by the developer of the two games we originally compared.
  
 
Sometimes, this is not particularly helpful if there is a lot of generic code used or there are drastically different programming teams. Other times, this can be a powerful tool (especially if it can be backed up by other evidence).
 
Sometimes, this is not particularly helpful if there is a lot of generic code used or there are drastically different programming teams. Other times, this can be a powerful tool (especially if it can be backed up by other evidence).
  
The aforementioned program is not available for download yet, as it is not in a distributable state.
+
The aforementioned program is not available for download yet as it is not in a distributable state.
  
 
''NOTE: GDRI does not condone software piracy.''
 
''NOTE: GDRI does not condone software piracy.''
  
 
===Interviews===
 
===Interviews===
Sometimes, GDRI is able to make contact with former staffers who are willing to help and share info with us. Look at our [[Interviews]] section to see who we have talked to so far.
+
GDRI will try to get information by making contact with former staffers. Look at our [[Interviews]] section to see who we have successfully talked to so far.
  
 
If you are a former staffer with one of the developers covered on GDRI and want to help us, please contact us at smsgenny at vgrebirth dot org.
 
If you are a former staffer with one of the developers covered on GDRI and want to help us, please contact us at smsgenny at vgrebirth dot org.
Line 29: Line 29:
 
Company websites are great resources for information, especially if the company is open about the games it worked on in the past (thus eliminating a lot of legwork for us).
 
Company websites are great resources for information, especially if the company is open about the games it worked on in the past (thus eliminating a lot of legwork for us).
  
Failing that, a great resource is [http://www.review-site.net/developer/ SIT Developer Table], a Japanese site that was the inspiration for GDRI. There, you'll find works lists for a multitude of game companies. If we're interested enough in a company listed, we might be inspired to do some of our own research.
+
Failing that, a great resource is [http://www.review-site.net/developer/ SIT Developer Table], a Japanese site that was the inspiration for GDRI. There, you'll find works lists for a multitude of game companies. If we are interested enough in a company listed, we might be inspired to do some of our own research.
  
 
Information can also be culled from [http://www.wikipedia.org/ Wikipedia] articles or message boards and discussion forums such as [http://www.2ch.net/ 2ch].
 
Information can also be culled from [http://www.wikipedia.org/ Wikipedia] articles or message boards and discussion forums such as [http://www.2ch.net/ 2ch].
Line 43: Line 43:
  
 
===Shared credits===
 
===Shared credits===
GDRI scours the Internet, ROMs, and other sources to find game credits. We might even play through an entire game just to get them. When we've gathered enough credits from various games, we can compare them, see what is shared between them, and hopefully come to some sort of conclusion.
+
GDRI scours the Internet, ROMs, and other sources to find game credits. We might even play through an entire game just to get them. When we have gathered enough credits from various games, we can compare them, see what is shared between them, and hopefully come to some sort of conclusion.
  
As we mentioned before, credits can be found in the ROMs. Usually, these are the same credits that can be seen by finishing the game. This is not to be confused with ROM text (described above), which is typically not meant to be seen by the general public.
+
As we mentioned before, credits can be found in the ROMs. These are usually the same credits that can be seen by finishing the game. This is not to be confused with ROM text (described above), which is typically not meant to be seen by the general public.

Revision as of 12:56, 10 May 2008

The following are the primary ways GDRI tries to determine the developer (company) of a game:

Actual mentions

An "actual mention" is when a company name is actually mentioned in or on the game. Sometimes, a game or game package will say upfront it was developed/programmed by a certain company.

Other times, the mention is not-so-forthcoming. It might say "Produced by Company" or "Designed by Company." And other times still, the company might just be mentioned in the copyright notice. In these cases, we will infer that the company is the developer. Hopefully, there will be other evidence to back that up.

Examples: 1 2 3 4

Another instance of what we would consider an actual mention is when the name of the developer is written on a wall, sign, or other object in a game. An example of this can be found in the unreleased Ninja Gaiden for the Sega Mega Drive. A sign flashing "Opus" backwards can be seen at the end of round 4-2. [1]

Code comparisons

Thanks to a program developed especially for GDRI, we can perform code comparisons. This program can look at two different files and show what is shared between them. For our purposes, we can compare two ROMs for games we know to be by the same developer and see what code is shared between the two. From there, we can search for this shared data in other ROMs. If there is a significant amount of shared code in these other ROMs, there is a good possibility that these were programmed by the developer of the two games we originally compared.

Sometimes, this is not particularly helpful if there is a lot of generic code used or there are drastically different programming teams. Other times, this can be a powerful tool (especially if it can be backed up by other evidence).

The aforementioned program is not available for download yet as it is not in a distributable state.

NOTE: GDRI does not condone software piracy.

Interviews

GDRI will try to get information by making contact with former staffers. Look at our Interviews section to see who we have successfully talked to so far.

If you are a former staffer with one of the developers covered on GDRI and want to help us, please contact us at smsgenny at vgrebirth dot org.

以前ゲームの開発に関わった方なら、どうぞご連絡ください。日本語、他国語問いません。

Online resources

Company websites are great resources for information, especially if the company is open about the games it worked on in the past (thus eliminating a lot of legwork for us).

Failing that, a great resource is SIT Developer Table, a Japanese site that was the inspiration for GDRI. There, you'll find works lists for a multitude of game companies. If we are interested enough in a company listed, we might be inspired to do some of our own research.

Information can also be culled from Wikipedia articles or message boards and discussion forums such as 2ch.

Print

Books, magazines, and other publications can also contain useful information. Check out the Further Reading section of a particular entry for a list of resources.

ROM text

You never know what you will find when you open up a ROM (which is as easy as opening it in Microsoft Notepad). One might find the name of the developer, names of staffers, or other "secret" text strings not otherwise accessible by playing the game.

For example, take the following text string found in the Master System Sonic the Hedgehog 2 ROM:

MS SONIC¥THE¥HEDGEHOG.2 Ver1.00 1992/09/05 SEGA /Aspect Co.,Ltd

Shared credits

GDRI scours the Internet, ROMs, and other sources to find game credits. We might even play through an entire game just to get them. When we have gathered enough credits from various games, we can compare them, see what is shared between them, and hopefully come to some sort of conclusion.

As we mentioned before, credits can be found in the ROMs. These are usually the same credits that can be seen by finishing the game. This is not to be confused with ROM text (described above), which is typically not meant to be seen by the general public.