Skip to content

Add everpuzzle to newsletter 7 #69

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Mar 2, 2020
Merged

Add everpuzzle to newsletter 7 #69

merged 5 commits into from
Mar 2, 2020

Conversation

Skytrias
Copy link
Contributor

@Skytrias Skytrias commented Mar 1, 2020

Tried to keep it smaller


Part of #64 ("Newsletter 7: Coordination/Tracking")

@AlexEne
Copy link
Member

AlexEne commented Mar 1, 2020

Thanks for this, I approved it but I think the sentence needs some tweaking:

Back then the project was using Amethyst with ECS, which wasn't nice to write game logic in.

@Skytrias
Copy link
Contributor Author

Skytrias commented Mar 1, 2020

Back then the project was using Amethyst with ECS, which wasn't nice to write game logic in.

sure, i somehow have to explain the move away from amethyst in the nicest way, any suggestion?
it was mainly because of compile times, game logic not translating too well in ECS systems, quirks like gamepad support etc.

@AngelOnFira
Copy link
Member

AngelOnFira commented Mar 1, 2020

@Skytrias I think it's important to be critical of Amethyst if you have reason to be. You used it, and have knowledge of ways it didn't work. However, saying it bluntly doesn't really fit the newsletter I think. It would do better as a part of a devblog post instead. Maybe it could say this instead?

Everpuzzle aims to become a similar game like Tetris Attack and expand on its concepts. The project was recently rewritten with minimal dependencies to achieve small compile times and gain more control over the underlying engine architecture. In the past Everpuzzle was using Amethyst with ECS, however there were some issues that made development difficult.

@AlexEne
Copy link
Member

AlexEne commented Mar 1, 2020

Saying that you changed from amethyst to your own ECS system is probably fine. E.g.

Switched from Amethyst to my own entity management system that allows me to...

@Skytrias
Copy link
Contributor Author

Skytrias commented Mar 1, 2020

Saying that you changed from amethyst to your own ECS system is probably fine. E.g.

Switched from Amethyst to my own entity management system that allows me to...

thing is im just using plain enums now instead of ecs, so is that really my own entity management?

@Skytrias
Copy link
Contributor Author

Skytrias commented Mar 1, 2020

Everpuzzle aims to become a similar game like Tetris Attack and expand on its concepts. The project was recently rewritten with minimal dependencies to achieve small compile times and gain more control over the underlying engine architecture. In the past Everpuzzle was using Amethyst with ECS, however there were some issues that made development difficult.

that sounds better!

@ozkriff
Copy link
Member

ozkriff commented Mar 2, 2020

Fixed a few markdown issues and resolved merge conflicts.

@ozkriff
Copy link
Member

ozkriff commented Mar 2, 2020

⏲️ Merging in a few hours if there're no objections.

@ozkriff ozkriff merged commit 104e552 into rust-gamedev:source Mar 2, 2020
@ozkriff
Copy link
Member

ozkriff commented Mar 2, 2020

Merged! Thanks for the PR!

@ozkriff ozkriff mentioned this pull request Mar 2, 2020
58 tasks
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.

5 participants