amaccann / phaser3-plugins Goto Github PK

• KISS etc, and merge duplicate webpack / build configs

• Drag select
• Health bar
• Formation movement (showing formations of grouped units)
• Migrate over the navmesh plugin
• Customisable fog of war
• Selection utility, to flag Sprites as selected?
• Building / construction widget
• "Spell" casting
• Central "brain" that controls GameObject movement, AI, etc. Following a rough "mediator" pattern
• ???

• Add the ability to configure rotation to the GameObject, if desired.

• Set up the monorepo package
• Wire up a basic suite of plugin => scene => sprite logic to get started on.

• Add the health bar graphics to the shared InterfaceSCene instead of the bespoke one currently used in the plugin.

• A plugin that gives a GameObject a brain, that controls movement, and any actions that it can be given to perform (attacking, spells, whatever)
• This might be a big one, in theory

• If the scene can be zoomed, then makes sense that the health-bars maintain a certain size, not to lose readability if the user zooms out too far.
• So, like the drag-select, render to a separate scene...

• Basic set-up stuff

I tried to import the phaser3-drag-select module, and can't get it to work. Just using

import DragSelectPlugin from '@pixelburp/phaser3-drag-select';
console.log(DragSelectPlugin);

logs DragSelectPlugin as undefined. I also tried referencing the dist/phaser3-drag-select-plugin.js file directly and using require instead and all of them fail. Is there something special you are doing when distributing the code which would break a standard webpack workflow?

• Given a grouping of sprites, and a destination location
  • Calculate possible formations, depending on cursor movement (so click and hold to change the shape)
  • Lock the calculations based on potential grids (useful for tile based movement

• Support Array values in tinting, to allow more granularity in the shading of the bars

• See subject

• animate the increase or decrease of the values

• A very old plugin but one worth migrating: https://www.npmjs.com/package/phaser-navmesh-generation
• Lots of dependencies that'll need updating, as well as the overall change to how Plugins, Scenes and Tilemaps work between Phaser 2 & Phaser 3

• Rather than watch, explicitly tell plugin to start watching. Then
• use once event tracking to watch the drag and up events, sending back the results
• otherwise there'll be conflicts with various mouse down events
• might be worth doing same for drag select

• Add some how tos and documentation for this

• Some baseline plugin that gives nominated Game Objects some automated motion.
• Given an Array of waypoints - or a mixture of waypoints and "Target" sprites - move to each.
• This will be agnostic to actions; so if a waypoint is a Sprite, "stop" at the Sprite and do nothing. Another plugin will handle behaviour thereof.
• Allow some configuration for ☝️ this case, as you won't want to move right up to the Sprite.

• With drag-select and formation-generator, both use functionally identical scenes to display the various UI widgets
• rather than have multiple scenes per plugin, it'd be useful to have a single shared scene.
• So the first plugin started would generate the scene, while any subsequent plugins would tap into that scene.

• As per subject, support netlify so on change to master, we build out those demos to netlify

• track multiple properties in a sprite
• stack each on top of each other.
• useful for shields, that sort of thing

• Things like forEach, the webpack configs should be moved to their own package
• Make this package private