58 lines
2.8 KiB
HTML
58 lines
2.8 KiB
HTML
|
<!DOCTYPE html>
|
||
|
|
<html lang="en">
|
||
|
|
|
||
|
|
<head>
|
||
|
|
<meta charset="UTF-8">
|
||
|
|
<meta http-equiv="X-UA-Compatible" content="IE=edge">
|
||
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||
|
|
<title>eAmuse API</title>
|
||
|
|
|
||
|
|
<link rel="stylesheet" href="styles.css">
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<body>
|
||
|
|
<table>
|
||
|
|
<tr>
|
||
|
|
<td><a href=".">Contents</a></td>
|
||
|
|
<td><a href="./transport.html">Transport layer</a></td>
|
||
|
|
<td><a href="./packet.html">Packet format</a></td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<h1>Benami/Konami eAmuse API</h1>
|
||
|
|
<p>Why?</p>
|
||
|
|
<p>I was curious how these APIs work, yet could find little to nothing on Google. There are a number of
|
||
|
|
closed-source projects, with presumably similarly closed-source internal documentation, and a scattering of
|
||
|
|
implementations of things, yet I couldn't find a site that actually just documents how the API works. If I'm
|
||
|
|
going to have to reverse engineer an open source project (or a closed source one, for that matter), I might as
|
||
|
|
well just go reverse engineer an actual game (or it's stdlib, as most of my time has been spent currently).</p>
|
||
|
|
<p>These pages are very much a work in progress, and are being written <i>as</i> I reverse engineer parts of the
|
||
|
|
protocol. I've been asserting all my assumptions by writing my own implementation as I go, however it currently
|
||
|
|
isn't sharable quality code and, more importantly, the purpose of these pages is to make implementation of one's
|
||
|
|
own code hopefully trivial.</p>
|
||
|
|
<p>Sharing annotated sources for all of the games' stdlibs would be both impractical and unwise. Where relevant
|
||
|
|
however I try to include snippets to illustrate concepts, and have included their locations in the source for if
|
||
|
|
you feel like taking a dive too.</p>
|
||
|
|
<p>If you're here because you work on one of those aforementioned closed source projects, hello! Feel free to share
|
||
|
|
knowledge with the rest of the world, or point out corrections. Or don't; you do you.</p>
|
||
|
|
|
||
|
|
<h1>Contents</h1>
|
||
|
|
<ol>
|
||
|
|
<li><a href="./transport.html">Transport layer</a></li>
|
||
|
|
<ol>
|
||
|
|
<li><a href="./transport.html#packet">Packet structure</a></li>
|
||
|
|
<li><a href="./transport.html#type">Types</a></li>
|
||
|
|
</ol>
|
||
|
|
<li><a href="./packet.html">The inner packet structure</a></li>
|
||
|
|
<ol>
|
||
|
|
<li><a href="./packet.html#xml">XML packets</a></li>
|
||
|
|
<li><a href="./packet.html#binary">Binary packed packets</a></li>
|
||
|
|
<li><a href="./packet.html#schema">Binary schemas</a></li>
|
||
|
|
<li><a href="./packet.html#data">Binary data</a></li>
|
||
|
|
</ol>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<p><small>This site intentionally looks not-great. I don't feel like changing that, and honestly quite like the aesthetic.</small></p>
|
||
|
|
</body>
|
||
|
|
|
||
|
|
</html>
|