The craft-clash from dog-face-development

Create an executable installer

From Auto-Anouncements created by willtheorangeguy: Dog-Face-Development/Auto-Anouncements#16

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#9

Create an .exe or an executable installer for the project and each version. Also, create a setup.py and requirements.txt file for each project with program dependencies and information.

Use PyInstaller or cx_Freeze.

Add Sentry

Add Sentry integration.

Help:

https://sentry.io/docs/

Create Translations

Using tools like Lingohub, POEditor, create translations of the project in popular languages. They could also be released for public help in translation!

Starting Languages:

English
Dutch
Spanish

Create a PULL REQUEST template

From Auto-Anouncements created by willtheorangeguy: Dog-Face-Development/Auto-Anouncements#19

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#6

Create an PULL REQUEST TEMPLATE.md file to make the project more welcoming.

Ideas:

Github Docs

Add DataDog

Add DataDog integrations.

Help:

https://docs.datadoghq.com/getting_started/application

Update README

From Auto-Anouncements created by willtheorangeguy: Dog-Face-Development/Auto-Anouncements#22

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#3

Create a proper README.md, using bookmarked templates.

Should have many areas of key program information.

Ideas:

Create wiki pages

From Auto-Anouncements created by willtheorangeguy: Dog-Face-Development/Auto-Anouncements#7

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#18

Go in-depth on documentation and programming style through the wiki pages.

Ensure code follows the Code Style Guide

From Auto-Anouncements created by willtheorangeguy: Dog-Face-Development/Auto-Anouncements#24

Update all previous code and put guidelines in place to ensure all code follows the Code Style Guide.

This includes formatting, code coverage and running tests.

Add time duration to upgrades

Add a time duration to upgrades such as walls and other defenses (2-6 hours, depending on upgrade). Much like how Clash of Clans has this.

Travis CI Integration

A lot of projects are using Travis CI integration and it is a good practice that we should adopt too.

We could add Circle CI if we really wanted to, but in @willtheorangeguy experience, it's not the best.

We just need to take a look at the Travis CI docs and add the requirements.txt and .travis.yml files.

Add more foodstuffs

Add more foodstuffs and in-game tools and consumables.

Screens automatically open

Describe the Bug

The About and Options screens automatically open when the application runs. Maybe the function is being called too soon?

Fix scrollbars on EULA window.

We need to add scroll bars to the EULA and License windows.

Add NewRelic

Add NewRelic integration.

Help:

https://docs.newrelic.com/docs/infrastructure/host-integrations/installation/new-relic-guided-install-overview

Play Button does not work

Describe the Bug

The play button does not work when clicked.

Update icon sets

From Auto-Anouncements created by willtheorangeguy: Dog-Face-Development/Auto-Anouncements#23

Update the icon sets to the latest version. Also ensure that icon licenses are included with the project.

Add more mobs

Add the following mobs:

Goats
Bears

Create a website

From Auto-Anouncements created by willtheorangeguy: Dog-Face-Development/Auto-Anouncements#8

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#17

Create a dynamic, responsive website that makes the program more welcoming, and provides the information of the README.md and screenshots in a more dynamic and engaging way.

Add LICENSE preface to the top of each code document

From Auto-Anouncements created by willtheorangeguy: Dog-Face-Development/Auto-Anouncements#9

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#16

Add a license preface to the top of each code document. This can be from a personal license, or like something that the GNU GPL v3 has:

        How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

    <one line to give the program's name and a brief idea of what it does.>
    Copyright (C) <year>  <name of author>

    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program.  If not, see <https://www.gnu.org/licenses/>.

Also add information on how to contact you by electronic and paper mail.

  If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:

    <program>  Copyright (C) <year>  <name of author>
    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License.  Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".

  You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
<https://www.gnu.org/licenses/>.

  The GNU General Public License does not permit incorporating your program
into proprietary programs.  If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library.  If this is what you want to do, use the GNU Lesser General
Public License instead of this License.  But first, please read
<https://www.gnu.org/licenses/why-not-lgpl.html>.

Exit button doesn't work.

When I click on the Exit button the program freezes for a while and then re-opens. Sometimes the program gets permanently frozen when I click the Exit button so I have to kill the program.

This is very frustrating, any help?

Add LambdaTest

Add LambdaTest integrations.

Help:

https://www.lambdatest.com/support/docs/

Add legal documents to project

From Auto-Anouncements created by willtheorangeguy: Dog-Face-Development/Auto-Anouncements#11

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#14

After legal documents have been created, at and edit each one to/for this project.

The following need to be completed:

Universal License
Universal EULA
Universal Terms and Conditions
Univeral Priacy Policy

Switch HUD

Rather than an inventory / hot bar, maybe more like a deck of cards (Clash Royale ref.). Or when battling a more of Boom Beach interface in which there are cards that you select and attack with.