New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Isn't it a bit early? #10

sgtfrankieboy opened this Issue Mar 23, 2014 · 3 comments


None yet
3 participants
Copy link

sgtfrankieboy commented Mar 23, 2014

I honestly believe that it's a bit early to already start working on a clone of Xbox Live. The actual emulator isn't even properly functional and probably won't be functional for a while.

Also, most of the Xbox LIVE details have to be the same; gamertag, gamerpoints, etc. Because they are hardcoded in most games.

There is also no documentation about how Xbox LIVE works. So before you can begin developing you need a good documentation about how the API works.

If you go ahead with development, the service should have a web interface, not one developed with Qt or some other UI framework.


This comment has been minimized.

Copy link

haneefmubarak commented Mar 23, 2014

The interface is for the admins of the servers - so we don't need to run them all the time, only when an admin needs to do admin stuff, meaning that a desktop GUI is fine.

If you read through the other issues, you'll see that Aixen is to be a bit more than a simple XBL clone. It should support new games that people develop for computers, using it's own interfaces. We don't need docs for the API since we'll be developing our own API and since the XBL stuff is likely coded into the OS, we don't need to match their API.

We can use different details because that's what will show up in other games, but what is hardcoded into the X360 games will indeed stay the same.

Also, let's say that we end up needing to actually emulate the XBL API exactly. No problem, all we will do is write up a simple API translation lib to translate XBL calls to Aixen calls.

I strongly appreciate the input though 😄 - if you have any related concerns, add another comment and I will reopen the issue.


This comment has been minimized.

Copy link

Kalker3 commented Mar 24, 2014

I was wondering, if Aixen will support Xenia and new computer games, will it also support RPCS3?


This comment has been minimized.

Copy link

haneefmubarak commented Mar 24, 2014

@Kalker3 I don't see why not. Aixen connectivity will be implemented as a C library, and any software ought to be able to link into and use the Aixen connectivity library to utilize the services offered by the Aixen network.

In other words, we won't be implementing all that much that is specific the Xenia, just the minimum that is necessary. The remaining will be implemented in Xenia using the library.

I'd be more than willing to accept contributions in the future towards any minimum changes that RPCS3 might need, and the rest can be implemented within RPCS3. Of course, any of this would only be possible with the help of the RPCS3 guys/team.

One more thing - in the future, please open a new issue and cite the relevant issue like so:

I was wondering, if Aixen will support Xenia and
new computer games (#10), will it also support RPCS3?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment