Multiple messages such as the following:

Waiting for connection from debug service on Chrome... lib/building_button.dart:74:8: Error: The method 'BuildingButton.onTapDown' has fewer positional arguments than those of overridden method 'ButtonComponent.onTapDown'. bool onTapDown() { ^ /C:/tools/flutter-sdk/flutter/.pub-cache/hosted/pub.dartlang.org/flame-1.0.0/lib/src/components/input/button_component.dart:56:8: Context: This is the overridden method ('onTapDown'). bool onTapDown(TapDownInfo info) { ^ lib/heeve_game.dart:141:11: Error: Couldn't find constructor 'RotateEffect'. RotateEffect( ^^^^^^^^^^^^ lib/heeve_game.dart:151:61: Error: The getter 'viewportOnly' isn't defined for the class 'EventPosition'.

• 'EventPosition' is from 'package:flame/src/gestures/events.dart' ('/C:/tools/flutter-sdk/flutter/.pub-cache/hosted/pub.dartlang.org/flame-1.0.0/lib/src/gestures/events.dart'). Try correcting the name to the name of an existing getter, or defining a getter or field named 'viewportOnly'. .where((t) => t.containsPoint(details.eventPosition.viewportOnly)) ^^^^^^^^^^^^

Description

Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change. If this is a breaking change, specify explicitly which APIs have been changed

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

• [ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
• [ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors and are passing (See Contributor Guide).
• [ ] My PR does not decrease the code coverage, or I have a very special case and explained on the PR description why this PR decreases the coverage.
• [ ] I updated/added relevant documentation (doc comments with ///) and updated/added examples in doc/examples.
• [ ] I have formatted my code with ./scripts/format.sh and the Flame analyzer (./scripts/analyze.sh) does not report any problems.
• [ ] I read and followed the Flame Style Guide.
• [ ] I have added a description of the change under [next] in CHANGELOG.md.
• [ ] I removed the Draft status, by clicking on the Ready for review button in this PR.
• [ ] I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require Flame users to manually update their apps to accommodate your change?

• [ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md).
• [ ] No, this is not a breaking change.

Related Issues

Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR.

Proposes a different currency.

Nivurium, an ore native to the Heeve home planet is consumed by both Humans and Heeves.

This PR adds a new atlas file with the following sprites:

• ore-1
• ore-2
• depleted-1
• depleted-2

(1, 2) are just variations of the same thing.

Description

It will be quite heavy to rebalance the tree on every tick now, but maybe we wont have that many components in total to lost fps on it.

https://user-images.githubusercontent.com/744771/143593935-8efc20b4-1df7-4e5b-a4d0-b51e05972875.mp4

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

• [ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
• [ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors and are passing (See Contributor Guide).
• [ ] My PR does not decrease the code coverage, or I have a very special case and explained on the PR description why this PR decreases the coverage.
• [ ] I updated/added relevant documentation (doc comments with ///) and updated/added examples in doc/examples.
• [ ] I have formatted my code with ./scripts/format.sh and the Flame analyzer (./scripts/analyze.sh) does not report any problems.
• [ ] I read and followed the Flame Style Guide.
• [ ] I have added a description of the change under [next] in CHANGELOG.md.
• [ ] I removed the Draft status, by clicking on the Ready for review button in this PR.
• [ ] I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require Flame users to manually update their apps to accommodate your change?

• [ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md).
• [ ] No, this is not a breaking change.

Related Issues

Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR.

Description

A lot of random stuff done in this PR, the currency at the moment is butterflies but it can of course be changed later. :)

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

• [x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
• [x] My PR includes unit or integration tests for all changed/updated/fixed behaviors and are passing (See Contributor Guide).
• [x] My PR does not decrease the code coverage, or I have a very special case and explained on the PR description why this PR decreases the coverage.
• [x] I updated/added relevant documentation (doc comments with ///) and updated/added examples in doc/examples.
• [x] I have formatted my code with ./scripts/format.sh and the Flame analyzer (./scripts/analyze.sh) does not report any problems.
• [x] I read and followed the Flame Style Guide.
• [x] I have added a description of the change under [next] in CHANGELOG.md.
• [x] I removed the Draft status, by clicking on the Ready for review button in this PR.
• [x] I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require Flame users to manually update their apps to accommodate your change?

• [x] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md).
• [ ] No, this is not a breaking change.

Related Issues

Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR.

Fixed several bugs and allow for several units to be selected and control, one at a time or as a group. I used the "selector" as an indicator of selected unit (calling it highlight). And I brought back the cartesian selection rectangle from spydon as per discussed.

https://user-images.githubusercontent.com/882703/141913797-6fe5eba8-b6be-4400-9f14-0465d2e9ec8c.mp4