Skip to content

Implement new difficulty setting - SuperEasy, for AI bots to use. #4255

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

Chewbakka-Wakka
Copy link

Granted that SuperEasy setting exists in Cam.

Would be useful as this allows for greater separation of the difficulty settings in various increments.

Whereby any AI bot on SuperEasy can be configured as "rookie friendly".

Using the original bunny icon from years back as the png represntation of SuperEasy

powermodifier is set too.

@past-due
Copy link
Member

To avoid breaking mods, there are a couple of general principles that are important to keep in mind:

  1. Renaming image files should be avoided unless there’s a sufficient reason (as this breaks mods that override them).
  2. When modifying enums you should generally avoid changing the values or order of existing entries. (In this case, the new item in frend.h should be added to the end of the enum.)

@Chewbakka-Wakka
Copy link
Author

In this case I have two reasons for renaming those image files:

  • Makes the image name clearer as to the intended use case for it. (some images look similar but used for other features)
  • Browsing the image directory tree has many images contained inside, this keeps those images of the same purpose grouped together for easier finding and clarity.

Yes noted on enums, though in this context it makes sense when going top to bottom that the order of hardness is sequential. It would look a bit odd to have INSANE followed by SUPEREASY, just reading the file alone.

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