Client on Monogame

[kreghek]

Gameplay/technical element	Comments	Results
Camera	The camera in the main screen must follow the player person.	[ x ] Use simple implementation on camera. It has transformation used in spriteBatch. Also the camera transformation used in the calculation of the mouse position in world.
Animation - Actor idle animation	Actors render from idle spriteset and sweep/float in one hex.	[ x ] It was made througt IActorStateEngine.
Animation - Actor move animation	Actors must move softly during 0.5 seconds. And they must do steps like sinus. And view model flips sprite based on move direction.	[ x ] It was made througt IActorStateEngine.
Screen statement	Screens is different state of the game.	[ x ] SceneManager with Scene as DrawableGameComponent.
Command queue	Commands need to be auto repeatable. Pay attension to moving animations	[ x ] CommnadLoopUpdater was introduced in the client.
Scheme Catalog	Currently scheme catalog set in environment variable. This will not works after build on client machine.	[ x ] There is new scheme locator to find schemes in the bin directory.
Mouse position	Currently we can select hex.	[ x ] The hex detection performs via the axial coordinate system.
Warnings in references	Core's projects referenced directly in the game. And Visual Studio shows warnings. We need to understand and fix this issue.	[ x ] It dessapeared after client porting to net5. This is not full and understable solution but the issue don't reproduce right now.
UI - menu screens	The majority of screens are menu or info panels (title, scores, settings). We need to get easy and performant way to build UI. Looks for layout, buttons, scrolls, input boxes.	[ x ] Just try to make simple controls by own hands. Now we have button class successfully used in game screens.
UI - main screen overlay	We must pay attention to interaction with HUD of main screen since it must ha not affect on underlying game object.	#1093 #1095
Transition between sectors	The player person transitions was full of problems in Unity client. So we need to prototype its to ensure it works fine in new client.	#1094
Walls/Actors overlap	The game is isometric. So game objects can overlap each other. The biggest difficult is a parts of a sinle composit object can be before and after actor in same time. For example, walls of cell.	#1110 #1111
Fog of War	We need to render only explored parts of sector.	[ x ] The sector view model renders observed game objects. The map view model renders observed nodes.
Command auto-selection	The user can clicks on differenct game objects - nodes to move, monsters to attack, chests to collect items and himself to heal.	[ x ] CommandInput responses for putting suitable command in the pool.
Commands - Attack		[ x ] The person can attack monsters. But with default (hand) hit.
Commands - Equip		#1126
Commands - Use things		#1127
Equipment visualization	Current equipment must show on actor	#1097 #1105 #1113
Monster visualization	Mosters different types must visualize differently. Currently we have two types of monsters: mono-sprite and humanoid. The view model must select correct type of visualization based on mnster scheme.	#1116
Shadows under game objects	Shadows (semi-transparent black rounds on the floor) show volume of objects. We should draw shadows under actors and, may be, under some static objects.	[ x ] All game objects is combination of graphics root and shadow sprite. When a actor moves the shadow moves under the actor and change its size depends on step progress.
Localization	Threr are 2 points of localization. The first thing is UI localization. I thing it will be based on resx. Second thing is localization of game objects (equipment, monsters, etc). This info stored in schemes themself.	#1106

[kreghek]

All features are made or described in a tasks. It means nothing was not forgoten. So this issue can be closed.