[ARCHIVE] Coronium GS (Coronium Game Server)

Third Party Coronium
#1

I’ve had a few requests for the archived Coronium GS project. This is an outdated project, but I reinstated some Amazon AMIs and gathered some of the most recent working links I found.

Additionally, the source code is fully available if anyone considers updating or enhancing the project. If this is something you think you might want to maintain, send me a message and I’ll add additional access.

Things to note:

  • This is an unsupported project. The adventure is yours alone.
  • The underlying core is about 2 years old, but reportedly still works.
  • The core engine is Luvit*, which more information can be found at Luvit.io
  • The current Luvit ecosystem is different than the one used in Coronium GS.
  • Your mileage may vary. A lot. Don’t worry, its not you, it’s the code.

*If you decide to contribute to the source api, you will need an understanding of Luvit usage.

Coronium GS Resources:

Amazon Pre-Built AMIs

North America - East

North America - West

Asia Pacific - Singapore

Asia Pacific - Mumbai

South America

United Kingdom

Documentation

http://gs.coronium.io/server/index.html

Video / Screencasts

https://www.youtube.com/playlist?list=PLlWSohAGdLDtpPYC_QpIJrXU01Mgs1x4Z

Source Codes

https://bitbucket.org/develephant/profile/repositories?search=coronium+gs

There is a cost involved in hosting the images. If you feel the project is useful, consider a hosting contribution.

Thanks to the following for previous contributions:

Corona Labs, Inc.

Jan Frode Maurice

Kerem San

Kevin Hincker

Mario Roberti

Craig Briggs

Vince A

Axtro Apps

Bestcycling S. L.

And other anonymous donors.

Enjoy.

#2

This is an awesome and easily integrated event based framework. I played with it for quite a while, but ultimately was not able to over come an issue with broken pipe errors. I’d go back to using it in a hot second if anyone ever picked it back up and smoothed out that problem. There may have been other issues, but that really was the only one that ever came up for me. 

#3

That was certainly one of the reasons it got retired. I spent so much time trying to debug that :wacko: . I found if I left a terminal connected, I would have the pipe error consistently. Not sure if that was the same for you. 

It could also be the use case, as others have told me they have working apps running.  :ph34r:

I am slowly working up a new OSS project (Socketeer) using the newer Luvit ecosystem, which is much more robust now (no pipe issues so far). Just gotta find time to finish the release up. At last point I was in the midst of docs.

Perhaps I can convince the team to sanction this project as work related.  :rolleyes:

Cheers.

#4

I remember the work you did attempting to track down the pipe error. Ah well. It was a Beta, after all :slight_smile: Very exciting to hear that you are moving toward (eventual) release of a new OSS project. I look forward to it!

#5

This is Brilliant! Thanks for digging everything out and putting it all in one place here. I’m only getting started with playing around with it but If I can ever contribute in the future I certainly will.

I’d love to see a Corona sanctioned version - It would be awesome to be able to take my Corona projects to the next level.

Hopefully some devs will pick this up and run with it.

Thanks again.

#6

This is an awesome and easily integrated event based framework. I played with it for quite a while, but ultimately was not able to over come an issue with broken pipe errors. I’d go back to using it in a hot second if anyone ever picked it back up and smoothed out that problem. There may have been other issues, but that really was the only one that ever came up for me. 

#7

That was certainly one of the reasons it got retired. I spent so much time trying to debug that :wacko: . I found if I left a terminal connected, I would have the pipe error consistently. Not sure if that was the same for you. 

It could also be the use case, as others have told me they have working apps running.  :ph34r:

I am slowly working up a new OSS project (Socketeer) using the newer Luvit ecosystem, which is much more robust now (no pipe issues so far). Just gotta find time to finish the release up. At last point I was in the midst of docs.

Perhaps I can convince the team to sanction this project as work related.  :rolleyes:

Cheers.

#8

I remember the work you did attempting to track down the pipe error. Ah well. It was a Beta, after all :slight_smile: Very exciting to hear that you are moving toward (eventual) release of a new OSS project. I look forward to it!

#9

This is Brilliant! Thanks for digging everything out and putting it all in one place here. I’m only getting started with playing around with it but If I can ever contribute in the future I certainly will.

I’d love to see a Corona sanctioned version - It would be awesome to be able to take my Corona projects to the next level.

Hopefully some devs will pick this up and run with it.

Thanks again.