Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
The title was weird. That's why I came to this post. Then, saw something :laugh:. Additional Information : You can use GitHub issues always for filling a bug report or feature-request. If you ...
Answer
#3: Post edited
- The title was weird. That's why I came to this post. Then, saw something :laugh:.
- **Additional Information :**
1. You can use [GitHub issue](https://github.com/codidact/qpixel/issues) always for filing a report or, feature-request.2. If you think that your feature-request needs discussion to public (not all features are helpful. And, Codidact is open-source. We build everything for user's better performance) than, you should ask it in Codidact Meta.3. If you have faced an issue. And, it's been a long day you are facing that than, you have to post it in CD meta.4. If you have faced "tiny" issue than, leave a message in Discord. So, that developer can solve that problem as soon as possible.
- The title was weird. That's why I came to this post. Then, saw something :laugh:.
- **Additional Information :**
- 1. You can use [GitHub issues](https://github.com/codidact/qpixel/issues) always for filling a bug report or feature-request.
- 2. If you think that your feature-request needs a discussion to public (not all features are helpful. And, Codidact is open-source. We build everything for user's better performance), then you should ask it in Codidact Meta.
- 3. If you have faced an issue. And, it's have been a long day you are facing that, then you have to post it in Codidact Meta.
- 4. If you have faced a "tiny" issue, then leave a message in Discord. So, developers can solve the problem as soon as possible.
#2: Post edited
- The title was weird. That's why I came to this post. Then, saw something :laugh:.
- **Additional Information :**
- 1. You can use [GitHub issue](https://github.com/codidact/qpixel/issues) always for filing a report or, feature-request.
- 2. If you think that your feature-request needs discussion to public (not all features are helpful. And, Codidact is open-source. We build everything for user's better performance) than, you should ask it in Codidact Meta.
- 3. If you have faced an issue. And, it's been a long day you are facing that than, you have to post it in CD meta.
4. If you have faced tiny issue than, leave a message in Discord. So, that developer can solve that problem as soon as possible.
- The title was weird. That's why I came to this post. Then, saw something :laugh:.
- **Additional Information :**
- 1. You can use [GitHub issue](https://github.com/codidact/qpixel/issues) always for filing a report or, feature-request.
- 2. If you think that your feature-request needs discussion to public (not all features are helpful. And, Codidact is open-source. We build everything for user's better performance) than, you should ask it in Codidact Meta.
- 3. If you have faced an issue. And, it's been a long day you are facing that than, you have to post it in CD meta.
- 4. If you have faced "tiny" issue than, leave a message in Discord. So, that developer can solve that problem as soon as possible.
#1: Initial revision
The title was weird. That's why I came to this post. Then, saw something :laugh:. **Additional Information :** 1. You can use [GitHub issue](https://github.com/codidact/qpixel/issues) always for filing a report or, feature-request. 2. If you think that your feature-request needs discussion to public (not all features are helpful. And, Codidact is open-source. We build everything for user's better performance) than, you should ask it in Codidact Meta. 3. If you have faced an issue. And, it's been a long day you are facing that than, you have to post it in CD meta. 4. If you have faced tiny issue than, leave a message in Discord. So, that developer can solve that problem as soon as possible.