hilts-vaughan / openorpg Goto Github PK

Currently there is no security on passwords, and plaintext is obviously unacceptable.

• Requirements
  • Add salts to database
  • Hash passwords with salts
• Recommendations
  • Secure the local storage of passwords, or remove password saving
  • Password recovery system that provides a key to change the password
  • Secure the client-server connection to prevent password sniffing
  • Secure the passwords client side so there can't be any password sniffing by the server/administrator

Enter key should set the focus to the chat box.

Looks like the color mapping is off; check and make sure the logic is good.

NullPointerException; we should check that someone is actually nearby to communicate with before trying to advance dialogs.

Add the SPARK module into OpenORPG and add multi-server playerworlds.

The dialog editor really should not refresh constantly, as it is irritating to use.

Create a method to find a node and then expand around that node.

Animations do not start fast enough, and this causes a desync between when the player inputs for about 150-200 milliseconds before the sprite actually starts animating.

This also causes an issue where it will not start an animation if you stop before it starts animating, which allows you to press the same key and repeat the process to move across the entire map without animating a single frame.

Since the client uses the index relatively to decide what option to select, when an option is missing it is difficult to pinpoint exacts.

Option 1: Send indexes with the actual strings
Option 2: Send all options, but hide the strings that aren't available (bigger payload, exposes data?)

This is because removal isn't immediate, but next tick. Zoning into the same map should be made illegal.

As the title says, if you de-select a target you cannot re-select them until you select something else first.

Dialog's should be able to complete certain step's, perform actions such as healing and the like. This will allow for rudimentary interaction.

This happens while in the editor. Not sure the root cause of how to reproduce though.

Happens on this line:
List accounts = context.Accounts.Where(x => x.IsOnline).ToList();

More information:
https://dl.dropboxusercontent.com/u/67149765/OpenORPG/Error1.txt
http://i.imgur.com/NGlzw0w.png

Hello,

i'm a hobbyist gamedev with some background in C#/unity in making games and I've been doing a ton of research all day in looking to do a phaser-based RPG game on the web with a client-server authoritative architecture. I landed here through all my searching and it looks EXACTLY like what I was getting ready to start writing out by hand. Just curious what the state of the development is? Are people still actively working on improvements? I hope to contribute as I get familiar with things.

Update Phaser to complete resolution fixes
As of writing this Phaser 2.4 RC1 has already been released

Registration currently does not exist in any form.
Several methods of implementing this are:

• Creating a web service of some kind (in PHP, Node, etc) for registration outside of the client
• Add registration to the login/main menu, currently there is an HTML element to do so, but it is commented out
  • Requires adding registration request/response packets to the networking model
  • Requires adding registration logic to the server
  • Requires more elements to be added to the main menu for displaying server rejection and more logic to be added for handling a success

Feel free to suggest alternatives/changes to the above

There is a way to Dockerize the application and have it up and running in a few commands. We should include these now where possible.

The default text on the chat box does not disappear after the chat box receives focus. It should of course be put back after losing focus, but it should lose visibility upon receiving focus.

I dont see any releases, do I need to build the project in order to try it out?

So we can validate requests which require filtering up front rather do null checks to make sure the player exists in every handler.

Encourage DB security practices by adding documentation for creating new DB users and removing "root" as the user in the default App.config.

Perhaps even add batch and shell scripts for helping create new non-root database users.

... should make the server usable on the main thread.