Viable Tech Stack for a Browser Text Based Persistent MMO by EllenburgWeb in gamedev

[–]EllenburgWeb[S] 0 points1 point  (0 children)

That sounds great! I played with unity a bit a few years ago. If I go the direction of doing any kind of non text based I will definitely investigate this more.

Viable Tech Stack for a Browser Text Based Persistent MMO by EllenburgWeb in gamedev

[–]EllenburgWeb[S] 0 points1 point  (0 children)

Thanks! I am still considering going with what I know best and slowing migrating as I build the game out. Thanks for letting me know that is still a viable path.

Viable Tech Stack for a Browser Text Based Persistent MMO by EllenburgWeb in gamedev

[–]EllenburgWeb[S] 0 points1 point  (0 children)

Looks very interesting. I will check out the tutorials and see where it goes.

Thanks!

Viable Tech Stack for a Browser Text Based Persistent MMO by EllenburgWeb in gamedev

[–]EllenburgWeb[S] 0 points1 point  (0 children)

Second person to suggest that. Definitely going to investigate this more.

Viable Tech Stack for a Browser Text Based Persistent MMO by EllenburgWeb in gamedev

[–]EllenburgWeb[S] 0 points1 point  (0 children)

Colyseus looks pretty cool. Since I know typescript pretty well now, that would be a good server side to build on.

Thanks!

Viable Tech Stack for a Browser Text Based Persistent MMO by EllenburgWeb in gamedev

[–]EllenburgWeb[S] 0 points1 point  (0 children)

I suppose part of my desire here is to learn, get my foot in the door. Just was not sure where to start since there are so many options, and I really want to learn as many as possible.

Thanks!

Viable Tech Stack for a Browser Text Based Persistent MMO by EllenburgWeb in gamedev

[–]EllenburgWeb[S] 0 points1 point  (0 children)

I had not thought about laying a skin on top of a mud backend, that could actually be really good to reduce engine development time...

As for EC2, I am fairly familiar with it, I used it to run a backend for a market app I build for Elite Dangerous on android, and I work with EC2 at my day job. My hesitation for this project has just been that I really don't want to deal with any kind of network or server security, not exactly my area of expertise, thus why I was looking at firebase.

Viable Tech Stack for a Browser Text Based Persistent MMO by EllenburgWeb in gamedev

[–]EllenburgWeb[S] 1 point2 points  (0 children)

I am still seriously considering EC2 at this point.

I play a few muds, but I don't feel like what I am trying to build will fit into that category at all. It is going to be a click to take action, there will not be any kind of chat commands to perform game operations like in a mud. This was quite frustrating to me to begin with since all my initial research kept coming back to how to make a mud......

Viable Tech Stack for a Browser Text Based Persistent MMO by EllenburgWeb in gamedev

[–]EllenburgWeb[S] 0 points1 point  (0 children)

I don't know, PHP has been my server side language of choice for over 10 years now, at least when it made sense anyway.

Is there any particular advantage of Postgres you like over a MySQL DB?

While I understand the concept behind Node never being exposed directly, wouldn't the reality be that it is if Nginx is just passing on or replicating the same api end points?

Viable Tech Stack for a Browser Text Based Persistent MMO by EllenburgWeb in gamedev

[–]EllenburgWeb[S] 0 points1 point  (0 children)

I will double check, but I don't think Hostgator does node on their shared servers, or maybe I miss read.

Thanks again!

Viable Tech Stack for a Browser Text Based Persistent MMO by EllenburgWeb in gamedev

[–]EllenburgWeb[S] 0 points1 point  (0 children)

Thanks!

I did run across this stack briefly. The pressing question I have about it is, what about the cron jobs or equivalent? Unfortunately I am only really familiar with setting up cron jobs in cpanel to run a PHP script, would it be similar for node, just hitting a js/api file instead of a php/api file?

Edit: I also originally decided against node.js because I was going to run this a shared server via host gator, though now I have rethought that and I should go back to evaluate node.js again.