Skip to content
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

Fix: THIS TIME CL works #14

Merged
merged 1 commit into from
Jul 12, 2023
Merged

Fix: THIS TIME CL works #14

merged 1 commit into from
Jul 12, 2023

Conversation

Furrior
Copy link

@Furrior Furrior commented Jul 12, 2023

What Does This PR Do

Why It's Good For The Game

Images of changes

Testing

Changelog

🆑
fix: Проебал одну /
/:cl:

@Furrior Furrior merged commit b00467c into master Jul 12, 2023
@Furrior Furrior deleted the tickledfix3 branch July 12, 2023 23:47
Furrior added a commit that referenced this pull request Jul 14, 2023
<!-- Write **BELOW** The Headers and **ABOVE** The comments else it may
not be viewable. -->
<!-- You can view Contributing.MD for a detailed description of the pull
request process. -->

## What Does This PR Do
<!-- Include a small to medium description of what your PR changes. -->
<!-- Document all changes, as not doing this may delay reviews or even
discourage maintainers from merging your PR! -->
<!-- If your PR fixes an issue, add "Fixes #1234" somewhere in the PR
description. This will automatically close the bug upon PR submission.
-->

## Why It's Good For The Game
<!-- Add a short description of why you think these changes would
benefit the game. If you can't justify it in words, it might not be
worth adding. -->

## Images of changes
<!-- If you did not make a map or sprite edit, you may delete this
section. You may include a gif or mp4 of your feature if you want. -->

## Testing
<!-- How did you test the PR, if at all? -->

## Changelog
:cl:
fix: Проебал одну /
/:cl:

<!-- Both :cl:'s are required for the changelog to work! You can put
your name to the right of the first :cl: if you want to overwrite your
GitHub username as author ingame. -->
<!-- You can use multiple of the same prefix (they're only used for the
icon ingame) and delete the unneeded ones. Despite some of the tags,
changelogs should generally represent how a player might be affected by
the changes rather than a summary of the PR's contents. -->
<!-- If a PR has no impact on players (i.e. a code refactor that does
not change functionality) then the entire Changelog heading and contents
can be removed. -->
Furrior added a commit that referenced this pull request Jul 19, 2023
<!-- Write **BELOW** The Headers and **ABOVE** The comments else it may
not be viewable. -->
<!-- You can view Contributing.MD for a detailed description of the pull
request process. -->

## What Does This PR Do
<!-- Include a small to medium description of what your PR changes. -->
<!-- Document all changes, as not doing this may delay reviews or even
discourage maintainers from merging your PR! -->
<!-- If your PR fixes an issue, add "Fixes #1234" somewhere in the PR
description. This will automatically close the bug upon PR submission.
-->

## Why It's Good For The Game
<!-- Add a short description of why you think these changes would
benefit the game. If you can't justify it in words, it might not be
worth adding. -->

## Images of changes
<!-- If you did not make a map or sprite edit, you may delete this
section. You may include a gif or mp4 of your feature if you want. -->

## Testing
<!-- How did you test the PR, if at all? -->

## Changelog
:cl:
fix: Проебал одну /
/:cl:

<!-- Both :cl:'s are required for the changelog to work! You can put
your name to the right of the first :cl: if you want to overwrite your
GitHub username as author ingame. -->
<!-- You can use multiple of the same prefix (they're only used for the
icon ingame) and delete the unneeded ones. Despite some of the tags,
changelogs should generally represent how a player might be affected by
the changes rather than a summary of the PR's contents. -->
<!-- If a PR has no impact on players (i.e. a code refactor that does
not change functionality) then the entire Changelog heading and contents
can be removed. -->
Furrior added a commit that referenced this pull request Jul 28, 2023
<!-- Write **BELOW** The Headers and **ABOVE** The comments else it may
not be viewable. -->
<!-- You can view Contributing.MD for a detailed description of the pull
request process. -->

## What Does This PR Do
<!-- Include a small to medium description of what your PR changes. -->
<!-- Document all changes, as not doing this may delay reviews or even
discourage maintainers from merging your PR! -->
<!-- If your PR fixes an issue, add "Fixes #1234" somewhere in the PR
description. This will automatically close the bug upon PR submission.
-->

## Why It's Good For The Game
<!-- Add a short description of why you think these changes would
benefit the game. If you can't justify it in words, it might not be
worth adding. -->

## Images of changes
<!-- If you did not make a map or sprite edit, you may delete this
section. You may include a gif or mp4 of your feature if you want. -->

## Testing
<!-- How did you test the PR, if at all? -->

## Changelog
:cl:
fix: Проебал одну /
/:cl:

<!-- Both :cl:'s are required for the changelog to work! You can put
your name to the right of the first :cl: if you want to overwrite your
GitHub username as author ingame. -->
<!-- You can use multiple of the same prefix (they're only used for the
icon ingame) and delete the unneeded ones. Despite some of the tags,
changelogs should generally represent how a player might be affected by
the changes rather than a summary of the PR's contents. -->
<!-- If a PR has no impact on players (i.e. a code refactor that does
not change functionality) then the entire Changelog heading and contents
can be removed. -->
Furrior added a commit that referenced this pull request Jul 31, 2023
<!-- Write **BELOW** The Headers and **ABOVE** The comments else it may
not be viewable. -->
<!-- You can view Contributing.MD for a detailed description of the pull
request process. -->

## What Does This PR Do
<!-- Include a small to medium description of what your PR changes. -->
<!-- Document all changes, as not doing this may delay reviews or even
discourage maintainers from merging your PR! -->
<!-- If your PR fixes an issue, add "Fixes #1234" somewhere in the PR
description. This will automatically close the bug upon PR submission.
-->

## Why It's Good For The Game
<!-- Add a short description of why you think these changes would
benefit the game. If you can't justify it in words, it might not be
worth adding. -->

## Images of changes
<!-- If you did not make a map or sprite edit, you may delete this
section. You may include a gif or mp4 of your feature if you want. -->

## Testing
<!-- How did you test the PR, if at all? -->

## Changelog
:cl:
fix: Проебал одну /
/:cl:

<!-- Both :cl:'s are required for the changelog to work! You can put
your name to the right of the first :cl: if you want to overwrite your
GitHub username as author ingame. -->
<!-- You can use multiple of the same prefix (they're only used for the
icon ingame) and delete the unneeded ones. Despite some of the tags,
changelogs should generally represent how a player might be affected by
the changes rather than a summary of the PR's contents. -->
<!-- If a PR has no impact on players (i.e. a code refactor that does
not change functionality) then the entire Changelog heading and contents
can be removed. -->
Furrior added a commit that referenced this pull request Sep 20, 2023
<!-- Write **BELOW** The Headers and **ABOVE** The comments else it may
not be viewable. -->
<!-- You can view Contributing.MD for a detailed description of the pull
request process. -->

## What Does This PR Do
<!-- Include a small to medium description of what your PR changes. -->
<!-- Document all changes, as not doing this may delay reviews or even
discourage maintainers from merging your PR! -->
<!-- If your PR fixes an issue, add "Fixes #1234" somewhere in the PR
description. This will automatically close the bug upon PR submission.
-->

## Why It's Good For The Game
<!-- Add a short description of why you think these changes would
benefit the game. If you can't justify it in words, it might not be
worth adding. -->

## Images of changes
<!-- If you did not make a map or sprite edit, you may delete this
section. You may include a gif or mp4 of your feature if you want. -->

## Testing
<!-- How did you test the PR, if at all? -->

## Changelog
:cl:
fix: Проебал одну /
/:cl:

<!-- Both :cl:'s are required for the changelog to work! You can put
your name to the right of the first :cl: if you want to overwrite your
GitHub username as author ingame. -->
<!-- You can use multiple of the same prefix (they're only used for the
icon ingame) and delete the unneeded ones. Despite some of the tags,
changelogs should generally represent how a player might be affected by
the changes rather than a summary of the PR's contents. -->
<!-- If a PR has no impact on players (i.e. a code refactor that does
not change functionality) then the entire Changelog heading and contents
can be removed. -->
Furrior added a commit that referenced this pull request Sep 21, 2023
<!-- Write **BELOW** The Headers and **ABOVE** The comments else it may
not be viewable. -->
<!-- You can view Contributing.MD for a detailed description of the pull
request process. -->

## What Does This PR Do
<!-- Include a small to medium description of what your PR changes. -->
<!-- Document all changes, as not doing this may delay reviews or even
discourage maintainers from merging your PR! -->
<!-- If your PR fixes an issue, add "Fixes #1234" somewhere in the PR
description. This will automatically close the bug upon PR submission.
-->

## Why It's Good For The Game
<!-- Add a short description of why you think these changes would
benefit the game. If you can't justify it in words, it might not be
worth adding. -->

## Images of changes
<!-- If you did not make a map or sprite edit, you may delete this
section. You may include a gif or mp4 of your feature if you want. -->

## Testing
<!-- How did you test the PR, if at all? -->

## Changelog
:cl:
fix: Проебал одну /
/:cl:

<!-- Both :cl:'s are required for the changelog to work! You can put
your name to the right of the first :cl: if you want to overwrite your
GitHub username as author ingame. -->
<!-- You can use multiple of the same prefix (they're only used for the
icon ingame) and delete the unneeded ones. Despite some of the tags,
changelogs should generally represent how a player might be affected by
the changes rather than a summary of the PR's contents. -->
<!-- If a PR has no impact on players (i.e. a code refactor that does
not change functionality) then the entire Changelog heading and contents
can be removed. -->
Furrior added a commit that referenced this pull request Oct 22, 2023
<!-- Write **BELOW** The Headers and **ABOVE** The comments else it may
not be viewable. -->
<!-- You can view Contributing.MD for a detailed description of the pull
request process. -->

## What Does This PR Do
<!-- Include a small to medium description of what your PR changes. -->
<!-- Document all changes, as not doing this may delay reviews or even
discourage maintainers from merging your PR! -->
<!-- If your PR fixes an issue, add "Fixes #1234" somewhere in the PR
description. This will automatically close the bug upon PR submission.
-->

## Why It's Good For The Game
<!-- Add a short description of why you think these changes would
benefit the game. If you can't justify it in words, it might not be
worth adding. -->

## Images of changes
<!-- If you did not make a map or sprite edit, you may delete this
section. You may include a gif or mp4 of your feature if you want. -->

## Testing
<!-- How did you test the PR, if at all? -->

## Changelog
:cl:
fix: Проебал одну /
/:cl:

<!-- Both :cl:'s are required for the changelog to work! You can put
your name to the right of the first :cl: if you want to overwrite your
GitHub username as author ingame. -->
<!-- You can use multiple of the same prefix (they're only used for the
icon ingame) and delete the unneeded ones. Despite some of the tags,
changelogs should generally represent how a player might be affected by
the changes rather than a summary of the PR's contents. -->
<!-- If a PR has no impact on players (i.e. a code refactor that does
not change functionality) then the entire Changelog heading and contents
can be removed. -->
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.

1 participant