Version

0.0.1

Steps to reproduce

Move mouse on the New Game button when game is starting.

What is expected?

Mouse component should work normally.

What is actually happening?

A pointer icon is also showing on top of the mouse icon.

loms.js and loms.node.js are duplicate

• Terrain should be the children of stage

All other character and pattern should be the children of terrain

• Terrain should render as hexagon side by side

• A star navigation algorithm.

Nice to have:

• Bottom hexagons should be a litter bigger than top in order to make player feel a little 3D-visualized

Example:

Click on the map to make character move, and then try to move screen to left or right.

What you will see is that character will walk into a wrong position.

Right now it's hard to debugging inside nwjs

LOMS Development CLI is created now, the aim of cli project is to help more people to setup the project more easily.

Right now if sprite in the same layer, there is no checking for them to figure out which one should be on top.
There should be a dynamic checking and sort sprite on the fly, sprite should on top of other sprites if this sprite Y axis number is bigger than others.

For example, if you continuously make screen moving to one direction, it will reach the point that dynamic hexagon creation is slower than the moving speed.

In the end, the screen will be empty.

• mouse controller

• keyboard controller

Terrain render Hexagon feature is almost done
Now we need to create more art resources to test Terrain's flush api.

I will put more details in https://loms.space

requirements:
value should be totally random.

https://github.com/qiao/PathFinding.js

Pixijs does not have layer system, that makes our mouse component render on top of other sprite become impossible. Pixi-display library have some bug that sprite will lose interaction so we have to implement by ourselves.

When running a test that tests source code using PIXI, it says ReferenceError: PIXI is not defined.

If you import pixi.js in the source code, then the test says ReferenceError: window is not defined. This is because pixijs depends on window object, and mocha environment doesn't seem to provide this global variable.

We need a better setup for the test, and some examples to show how we can test code with pixi.js

When user click Quit button, nwjs client will be close.

requirements:

• 1. a system icon on the top left corner during the game (not in MainMenu)
• 2. when user click system icon, a popup dialog would show and have a "quit game" button
• 3. click "quit game" button and game window will be closed

We need to create a in-game mouse component that when player moving mouse to the edge of the nw.js client, the mouse icon would change and still stay inside.

example:
When player move mouse to the left edge of screen, the mouse icon change into '>', and map will begin to moving to left.

NW.js client should set window size by user's screen resolution automatically.

requirements

• low coupling with other class
• able to play multi-sound in a same time
• stop and continue API feature

example

1. play the step sound when character is walking
2. play music when entering a specific scene

#52 mentioned in this RP.

Class UIText should have a feature that it could show outline when mouse move over it

In Controller, the event keyup is trigger twice every time I press the keyboard.

Game should be running in background, the game logic should not be blocked.

Right now class Terrain only have one container, and the position x & y are being set directly.

I am afraid of stack overflow because the map is unlimited and the number will not be accurate somehow.

So the solution could be:

1. add setTransform api in class ElementCore, and specialize class Terrain's api setTransform.
2. setTransform receives vector as param, and class LayerAgent's api moveLayerTo does not set position directly anymore.
3. Terrain's container position does not change anymore, and more container will be inside Terrain's container dynamically .
4. each container will render a new branch of Hexagon on the fly when layer is moving to certain coordinates

Currently the Actor class only can access inside stageAgent, which is not useful at all.

Actor should be export to outside and user could hold instance, so the development will be more easier.

Right now, the sprite can only handle one animation, it's clearly not going to work with character sprite.

• implement api
• use JSON file to manage language content
• easy to extend
• auto check language setting in native system (nice to have)

• save into local file
• load local file
• load from network

requirements

• unit test for up, down, left, right edge case
• use mouse component texture in asset folder

• walk

• stand

• attack

• battle form

• ultimate

• cast

• dying

• near death

• left version

at Loader.add (Loader.js:334)
at LOMSRenderer.addActor (lomsRenderer.js:15)
at MainMenu.render (mainMenu.js:29)

Found a good front end framework to help developer implement GUI interface.

Right now all the error is not show in the client side. We need a hint bar to show the error message to make us debugging easier.
Could start with errorUtil.js, add an error handling function and replace all the native console.error.
Add markup in index.html to show the error, should be easy enough at least for now.

Similar blocks of code found in 2 locations. Consider refactoring.

https://codeclimate.com/github/SkyHarp/LegendOfMountainSea/LOMS/src/module/store.js#issue_5a90ab0ca810f60001000089

Task:

Player needs to find HouYi to solve this crisis

winGUI variable scope should be not inside project.
See here:
https://github.com/SkyHarp/LegendOfMountainSea/blob/master/LOMS/src/view/mainMenu.js#L58

Suggest
Create class "window" in src/control folder, warp winGUI inside.

Need to detecting time elapsed since last frame before render

• It is up to player.

• The first time player will stay in a country which is not belong to player.

• Player needs to use all the resource to find people (NPC) who is willing to follow player and build a country or take current country from the king.

Environment

• Version: 0.0.1
• Environment name and version (e.g. node.js 6.4): 9.2.0
• Operating System and version (windows or macOS): at least windows

Maybe a PIXI.Bounds object is a better solution for implementing feature #57
And also this might needs feature #49