https://github.com/technius/botrpg-online

A work-in-progress, open-source MMORPG for programmers
https://github.com/technius/botrpg-online

Last synced: about 1 year ago
JSON representation

A work-in-progress, open-source MMORPG for programmers

• Host: GitHub
• URL: https://github.com/technius/botrpg-online
• Owner: Technius
• License: other
• Created: 2015-02-12T01:32:54.000Z (over 11 years ago)
• Default Branch: master
• Last Pushed: 2015-10-01T04:01:15.000Z (over 10 years ago)
• Last Synced: 2025-01-31T12:25:06.103Z (over 1 year ago)
• Language: Scala
• Size: 2.29 MB
• Stars: 4
• Watchers: 4
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
BotRPG Online

=============

[![Join the chat at https://gitter.im/Technius/botrpg-online](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/Technius/botrpg-online?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)

BotRPG Online is a work-in-progress, open source MMORPG built with Scala, Play

Framework, Akka, and Scala.js. Unlike most MMORPGs, where *players* are supposed

to play the game, players are supposed to program *bots* to play BotRPG for

them.

An instance of BotRPG is running on Heroku [here](http://botrpg-online.herokuapp.com).

Running

=======

1. Clone this repository.

2. `activator`

3. `project server`

4. `run`

5. In your favorite Internet browser, navigate to `http://localhost:9000`.

To do

=====

In no particular order:

* Client

  * Add ability to bot in a game

  * Add a navigation menu, possibly offcanvas

  * Cleanup `GameCtrl` and `GameService`

  * Always put data of self on the left/top in battles

  * Find way to detect if user changes scroll to bottom in action autoscroll

* Server

  * Cleanup websocket communication

  * Divide `UserActor` into actors for inbound, outbound, and internal

  * Add chat feature

  * Implement a real login system

  * Automatically force a draw if turn exceeds a certain number (30?)

  * Improve concurrency by removing all the asking

* Shared Code

  * Use traits to categorize messages

  * Move game logic from server to shared code for possible 'AI sandboxing'

    on client