Skip to content

fix spark mana transfer check - #130

Open
LooseEthics wants to merge 1 commit into
GTNewHorizons:masterfrom
LooseEthics:spark-transfer-bounding
Open

fix spark mana transfer check#130
LooseEthics wants to merge 1 commit into
GTNewHorizons:masterfrom
LooseEthics:spark-transfer-bounding

Conversation

@LooseEthics

Copy link
Copy Markdown

EntitySpark update function has a check that only allows outgoing transfers if the total mana available for transfer is greater than the square of the number of transfers.
This feels arbitrary to the point it makes me think it's some sort of a typo. Also it makes it difficult to completely empty an object of mana.
The new logic only checks if there is any available mana to allow transfer. If the amount of mana available is less than the number of transfers, some targets get 1 point until the source runs out, the rest get nothing.

@combusterf combusterf left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This introduces a new bug where free mana is generated when mana is between 1 and transfers-1

If you want to fix that, you also need to be careful that dispersion and balancing still works as intended.

@LooseEthics

Copy link
Copy Markdown
Author

I think I see the problem. Will fix when I'm at my desktop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants