mo-shoba / cubeflyer Goto Github PK
View Code? Open in Web Editor NEWLicense: MIT License
License: MIT License
The game is fun with the current configuration of greetings and gravity, and it may have a local high score if this was implemented by teams in day 1. It would be nicer if this could all be in a service running somewhere that would allow the configuration to be updated without having to change the game code, or for high scores to be persisted.
A lot of software does this - it has certain values set from a configuration service that can be tweaked without redeploying the application based on data gathered from users of the application. For example, in a game if a lot of users are failing to defeat a certain boss, the game can be tweaked through configuration to make the boss easier to beat.
As a software engineering team, you have been tasked with:
How this is created is up to the team. It can be a local Python/Flask web app that stores the scores in memory, it can use a database to store the scores and configuration, use a cloud-based gaming service, or even a cloud-based serverless application. It depends on the skill level of the team, though the recommendation is to start as simple as possible.
The game is fun with the current configuration of greetings and gravity, and it may have a local high score if this was implemented by teams in day 1. It would be nicer if this could all be in a service running somewhere that would allow the configuration to be updated without having to change the game code, or for high scores to be persisted.
A lot of software does this - it has certain values set from a configuration service that can be tweaked without redeploying the application based on data gathered from users of the application. For example, in a game if a lot of users are failing to defeat a certain boss, the game can be tweaked through configuration to make the boss easier to beat.
As a software engineering team, you have been tasked with:
How this is created is up to the team. It can be a local Python/Flask web app that stores the scores in memory, it can use a database to store the scores and configuration, use a cloud-based gaming service, or even a cloud-based serverless application. It depends on the skill level of the team, though the recommendation is to start as simple as possible.
There are a number of greetings in the Constants
file. Lets add a few more to introduce some extra variety to the game.
Add some way to track the High Score over a session that keeps track of how high a player has scored in the hud file and displays the maximum score that anyone has achieved during that play.
Not sure if this is a bug report or a feature request.
To Reproduce
Expected behavior
The game should obviously end and give you time to realize before you restart
Add some way to track the High Score over a session that keeps track of how high a player has scored in the hud file and displays the maximum score that anyone has achieved during that play.
One of the most needed parts of open source projects is documentation. Many developers will want to work on code, but few want to work on docs. This is a shame, as docs are the most important part of an open source project for a new person to start using it. You can have the most perfect library, but it is useless if no-one knows how to use it.
The CubeFlyer project is lacking in good documentation.
As a documentation team, you have been tasked with actually creating documentation. This includes:
This documentation should all be in markdown. To add documentation for features being added by other teams, you will need to collaborate with those teams to generate the documentation in tandem. This will be good learning for the other teams to help cement the idea that documentation is a continuous process that includes everyone.
To help you learn markdown syntax, you should work through the Communicate using Markdown lab on GitHub skills.
VS Code has great support for markdown built in, and its markdown functionality can be improved using a number of extensions. You can learn more in the markdown in VS Code documentation.
Add some way to track the High Score over a session that keeps track of how high a player has scored in the hud file and displays the maximum score that anyone has achieved during that play.
The game is fun with the current configuration of greetings and gravity, and it may have a local high score if this was implemented by teams in day 1. It would be nicer if this could all be in a service running somewhere that would allow the configuration to be updated without having to change the game code, or for high scores to be persisted.
A lot of software does this - it has certain values set from a configuration service that can be tweaked without redeploying the application based on data gathered from users of the application. For example, in a game if a lot of users are failing to defeat a certain boss, the game can be tweaked through configuration to make the boss easier to beat.
As a software engineering team, you have been tasked with:
How this is created is up to the team. It can be a local Python/Flask web app that stores the scores in memory, it can use a database to store the scores and configuration, use a cloud-based gaming service, or even a cloud-based serverless application. It depends on the skill level of the team, though the recommendation is to start as simple as possible.
Add some way to track the High Score over a session that keeps track of how high a player has scored in the hud file and displays the maximum score that anyone has achieved during that play.
The CubeFlyer game has graphics that are somewhat basic - it is a cube flying through blocks. This can be improved, so those attendees with an art or design background can help make both the UI and the game graphics better.
An a user interface team, you have been tasked with:
There are a number of greetings in the Constants
file. Lets add a few more to introduce some extra variety to the game.
One of the most needed parts of open source projects is documentation. Many developers will want to work on code, but few want to work on docs. This is a shame, as docs are the most important part of an open source project for a new person to start using it. You can have the most perfect library, but it is useless if no-one knows how to use it.
The CubeFlyer project is lacking in good documentation.
As a documentation team, you have been tasked with actually creating documentation. This includes:
This documentation should all be in markdown. To add documentation for features being added by other teams, you will need to collaborate with those teams to generate the documentation in tandem. This will be good learning for the other teams to help cement the idea that documentation is a continuous process that includes everyone.
To help you learn markdown syntax, you should work through the Communicate using Markdown lab on GitHub skills.
VS Code has great support for markdown built in, and its markdown functionality can be improved using a number of extensions. You can learn more in the markdown in VS Code documentation.
Add the ability to score in the game. The hud file already supports displaying the score but there isn't any way to actually score anything yet.
Let's find a way to earn points and track that!
Some ideas:
The CubeFlyer game has graphics that are somewhat basic - it is a cube flying through blocks. This can be improved, so those attendees with an art or design background can help make both the UI and the game graphics better.
An a user interface team, you have been tasked with:
The CubeFlyer game has graphics that are somewhat basic - it is a cube flying through blocks. This can be improved, so those attendees with an art or design background can help make both the UI and the game graphics better.
An a user interface team, you have been tasked with:
The game is fun with the current configuration of greetings and gravity, and it may have a local high score if this was implemented by teams in day 1. It would be nicer if this could all be in a service running somewhere that would allow the configuration to be updated without having to change the game code, or for high scores to be persisted.
A lot of software does this - it has certain values set from a configuration service that can be tweaked without redeploying the application based on data gathered from users of the application. For example, in a game if a lot of users are failing to defeat a certain boss, the game can be tweaked through configuration to make the boss easier to beat.
As a software engineering team, you have been tasked with:
How this is created is up to the team. It can be a local Python/Flask web app that stores the scores in memory, it can use a database to store the scores and configuration, use a cloud-based gaming service, or even a cloud-based serverless application. It depends on the skill level of the team, though the recommendation is to start as simple as possible.
Add the ability to score in the game. The hud file already supports displaying the score but there isn't any way to actually score anything yet.
Let's find a way to earn points and track that!
Some ideas:
Add the ability to score in the game. The hud file already supports displaying the score but there isn't any way to actually score anything yet.
Let's find a way to earn points and track that!
Some ideas:
One of the most needed parts of open source projects is documentation. Many developers will want to work on code, but few want to work on docs. This is a shame, as docs are the most important part of an open source project for a new person to start using it. You can have the most perfect library, but it is useless if no-one knows how to use it.
The CubeFlyer project is lacking in good documentation.
As a documentation team, you have been tasked with actually creating documentation. This includes:
This documentation should all be in markdown. To add documentation for features being added by other teams, you will need to collaborate with those teams to generate the documentation in tandem. This will be good learning for the other teams to help cement the idea that documentation is a continuous process that includes everyone.
To help you learn markdown syntax, you should work through the Communicate using Markdown lab on GitHub skills.
VS Code has great support for markdown built in, and its markdown functionality can be improved using a number of extensions. You can learn more in the markdown in VS Code documentation.
There are a number of greetings in the Constants
file. Lets add a few more to introduce some extra variety to the game.
The game is fun with the current configuration of greetings and gravity, and it may have a local high score if this was implemented by teams in day 1. It would be nicer if this could all be in a service running somewhere that would allow the configuration to be updated without having to change the game code, or for high scores to be persisted.
A lot of software does this - it has certain values set from a configuration service that can be tweaked without redeploying the application based on data gathered from users of the application. For example, in a game if a lot of users are failing to defeat a certain boss, the game can be tweaked through configuration to make the boss easier to beat.
As a software engineering team, you have been tasked with:
How this is created is up to the team. It can be a local Python/Flask web app that stores the scores in memory, it can use a database to store the scores and configuration, use a cloud-based gaming service, or even a cloud-based serverless application. It depends on the skill level of the team, though the recommendation is to start as simple as possible.
One of the most needed parts of open source projects is documentation. Many developers will want to work on code, but few want to work on docs. This is a shame, as docs are the most important part of an open source project for a new person to start using it. You can have the most perfect library, but it is useless if no-one knows how to use it.
The CubeFlyer project is lacking in good documentation.
As a documentation team, you have been tasked with actually creating documentation. This includes:
This documentation should all be in markdown. To add documentation for features being added by other teams, you will need to collaborate with those teams to generate the documentation in tandem. This will be good learning for the other teams to help cement the idea that documentation is a continuous process that includes everyone.
To help you learn markdown syntax, you should work through the Communicate using Markdown lab on GitHub skills.
VS Code has great support for markdown built in, and its markdown functionality can be improved using a number of extensions. You can learn more in the markdown in VS Code documentation.
Add some way to track the High Score over a session that keeps track of how high a player has scored in the hud file and displays the maximum score that anyone has achieved during that play.
Not sure if this is a bug report or a feature request.
To Reproduce
Expected behavior
The game should obviously end and give you time to realize before you restart
One of the most needed parts of open source projects is documentation. Many developers will want to work on code, but few want to work on docs. This is a shame, as docs are the most important part of an open source project for a new person to start using it. You can have the most perfect library, but it is useless if no-one knows how to use it.
The CubeFlyer project is lacking in good documentation.
As a documentation team, you have been tasked with actually creating documentation. This includes:
This documentation should all be in markdown. To add documentation for features being added by other teams, you will need to collaborate with those teams to generate the documentation in tandem. This will be good learning for the other teams to help cement the idea that documentation is a continuous process that includes everyone.
To help you learn markdown syntax, you should work through the Communicate using Markdown lab on GitHub skills.
VS Code has great support for markdown built in, and its markdown functionality can be improved using a number of extensions. You can learn more in the markdown in VS Code documentation.
There are a number of greetings in the Constants
file. Lets add a few more to introduce some extra variety to the game.
Add some way to track the High Score over a session that keeps track of how high a player has scored in the hud file and displays the maximum score that anyone has achieved during that play.
The CubeFlyer game has graphics that are somewhat basic - it is a cube flying through blocks. This can be improved, so those attendees with an art or design background can help make both the UI and the game graphics better.
An a user interface team, you have been tasked with:
Not sure if this is a bug report or a feature request.
To Reproduce
Expected behavior
The game should obviously end and give you time to realize before you restart
The game is fun with the current configuration of greetings and gravity, and it may have a local high score if this was implemented by teams in day 1. It would be nicer if this could all be in a service running somewhere that would allow the configuration to be updated without having to change the game code, or for high scores to be persisted.
A lot of software does this - it has certain values set from a configuration service that can be tweaked without redeploying the application based on data gathered from users of the application. For example, in a game if a lot of users are failing to defeat a certain boss, the game can be tweaked through configuration to make the boss easier to beat.
As a software engineering team, you have been tasked with:
How this is created is up to the team. It can be a local Python/Flask web app that stores the scores in memory, it can use a database to store the scores and configuration, use a cloud-based gaming service, or even a cloud-based serverless application. It depends on the skill level of the team, though the recommendation is to start as simple as possible.
Add the ability to score in the game. The hud file already supports displaying the score but there isn't any way to actually score anything yet.
Let's find a way to earn points and track that!
Some ideas:
There are a number of greetings in the Constants
file. Lets add a few more to introduce some extra variety to the game.
Add the ability to score in the game. The hud file already supports displaying the score but there isn't any way to actually score anything yet.
Let's find a way to earn points and track that!
Some ideas:
One of the most needed parts of open source projects is documentation. Many developers will want to work on code, but few want to work on docs. This is a shame, as docs are the most important part of an open source project for a new person to start using it. You can have the most perfect library, but it is useless if no-one knows how to use it.
The CubeFlyer project is lacking in good documentation.
As a documentation team, you have been tasked with actually creating documentation. This includes:
This documentation should all be in markdown. To add documentation for features being added by other teams, you will need to collaborate with those teams to generate the documentation in tandem. This will be good learning for the other teams to help cement the idea that documentation is a continuous process that includes everyone.
To help you learn markdown syntax, you should work through the Communicate using Markdown lab on GitHub skills.
VS Code has great support for markdown built in, and its markdown functionality can be improved using a number of extensions. You can learn more in the markdown in VS Code documentation.
Not sure if this is a bug report or a feature request.
To Reproduce
Expected behavior
The game should obviously end and give you time to realize before you restart
Add the ability to score in the game. The hud file already supports displaying the score but there isn't any way to actually score anything yet.
Let's find a way to earn points and track that!
Some ideas:
Not sure if this is a bug report or a feature request.
To Reproduce
Expected behavior
The game should obviously end and give you time to realize before you restart
The CubeFlyer game has graphics that are somewhat basic - it is a cube flying through blocks. This can be improved, so those attendees with an art or design background can help make both the UI and the game graphics better.
An a user interface team, you have been tasked with:
The CubeFlyer game has graphics that are somewhat basic - it is a cube flying through blocks. This can be improved, so those attendees with an art or design background can help make both the UI and the game graphics better.
An a user interface team, you have been tasked with:
There are a number of greetings in the Constants
file. Lets add a few more to introduce some extra variety to the game.
Not sure if this is a bug report or a feature request.
To Reproduce
Expected behavior
The game should obviously end and give you time to realize before you restart
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.