It is common to see "developer" and "publisher" collapsed into a single credit line, especially on older or informally maintained game lists. That shortcut throws away a genuinely useful distinction.
Two Different Jobs
A developer is the studio that actually designs and builds a game — writing code, creating art, tuning mechanics. A publisher funds production, handles marketing, negotiates retail or storefront distribution, and frequently owns the resulting intellectual property outright, regardless of how much creative control the development studio retained.
Why This Split Matters for Research
A developer's portfolio across different publishers reveals their design sensibilities and technical strengths consistently, while a publisher's portfolio across different developers reveals genre bets and business strategy instead, a pattern explored directly in Old PC Games by Publisher. Merging the two fields erases both signals at once.
Rights Complexity Often Traces Back to This Split
When a studio closes but its publisher survives, or a publisher dissolves while a development studio continues independently, the resulting rights confusion frequently stems directly from this developer-publisher relationship — exactly the kind of history that makes legal status verification genuinely necessary rather than a formality.
Keeping the Fields Separate in Practice
A well-structured database links both fields independently, letting a visitor browse either the full developer listings or publisher listings on their own terms, rather than forcing one to stand in for both.
