|*KoG*| King of Gores
━━━━━ Chat ━━━━━ / general_chatroom
General discussions or talks about KoG servers and KoG community can be made here. English only.
Between 11/18/2023 12:00AM and 11/19/2023 12:00AM
1
We are happy to announce that @Krumplee joined our tester team
Cheers
Rey
6
How do you solve things in real life?
Changing the system seems to be too difficult for you. But not even being honest with the community is really the best I played the game almost every day for 7 years, made YouTube videos and donated money. After a short break I come back and see this. Pretty sure if I had used my old name I would have been migrated within 1 week. Everythig is said friends 1 How do you solve things in real life? Changing the system seems to be too difficult for you. But not even being honest with the community is really the best I played the game almost every day for 7 years, made YouTube videos and donated money. After a short break I come back and see this. Pretty sure if I had used my old name I would have been migrated within 1 week. Everythig is said friends just wanted to share my opinion
just wanted to share my opinion 
3
2
2
2
2
1
Or was that a bit of a lie? oopsi
1
1
How do you solve things in real life? Changing the system seems to be too difficult for you. But not even being honest with the community is really the best I played the game almost every day for 7 years, made YouTube videos and donated money. After a short break I come back and see this. Pretty sure if I had used my old name I would have been migrated within 1 week. Everythig is said friends 
1
but that's also understandable with arguments like that but that's also understandable with arguments like that 
1
1
+-----------------+-----------------+
| COUNT(FinishID) | YEAR(Timestamp) |
+-----------------+-----------------+
| 40.424 | 2015 |
| 73.521 | 2016 |
| 99.627 | 2017 |
| 108.497 | 2018 |
| 119.444 | 2019 |
| 246.700 | 2020 |
| 462.378 | 2021 |
| 675.906 | 2022 |
| 897.206 | 2023 |
+-----------------+-----------------+ 
2
2 1 1
1
1
1 2 2
2
2
2
3 1 1
1
1
1
1
1
1
1
1 1
1 1
1
4
1
I think I'll have something better set up in 2-3 sprints
1 I think I'll have something better set up in 2-3 sprints 1 1
1
1
3 1
2 3 3 1
3
1
but that's also understandable with arguments like that but that's also understandable with arguments like that 
1
Providing constructive criticism to an open source project is a valuable contribution, as it helps improve the quality of the software. Here are some tips on how to give constructive criticism effectively:
Understand the Project:
Familiarize yourself with the project's goals, objectives, and guidelines. This will help you provide feedback that aligns with the project's vision.
Be Respectful:
Approach your criticism with a positive and respectful tone. Remember that the contributors are volunteers who dedicate their time and effort to the project.
Be Specific:
Clearly identify the issue or area that you believe needs improvement. Provide specific details, such as code snippets, error messages, or examples to illustrate your point.
Offer Solutions:
Instead of just pointing out problems, suggest possible solutions or improvements. This shows that you are not just criticizing but are actively contributing to finding solutions.
Follow Project Guidelines:
Ensure that your feedback aligns with the project's guidelines and coding conventions. If the project has a specific process for submitting feedback or issues, follow it.
Check for Duplicates:
Before submitting an issue or feedback, check if someone else has already reported a similar problem. If so, you can add your comments or provide additional information to the existing issue.
Use a Positive Tone:
Frame your criticism in a positive light. Instead of saying, "This code is wrong," you could say, "I noticed an opportunity for improvement in this code, and here are some suggestions."
Provide Context:
Explain the context of your feedback. For example, describe the impact the issue has on the project or its users. This helps the maintainers understand the importance of your feedback.
Be Open to Discussion:
Be open to a conversation about your feedback. Project maintainers and contributors may have questions or seek clarification. Engage in a constructive discussion to further refine your ideas.
Acknowledge Positives:
If there are positive aspects of the project, acknowledge them. It's important to balance your feedback by recognizing the things that are working well. 1 1 
2
1
TEAMRANKS LEADERBOARD 
