The title was designed to meet a professional aesthetic. I would appreciate any specific feedback you have on improving its quality.
I can understand your situation here, I apologize for the misunderstanding. But to be honest, you make your topic sound like apple, with exaggerated marketing. Why it’s the best? Does it work in mobile? Is it customizable?
Theres no doubt that AI can’t do full-scale projects by itself, it needs human touch. Even the training of those AI needs to be supervised. Now I don’t know how high the potential of AI can we harness, but It will definitely be used as an assisting tool, rather than something that acts in itself. Just like how AIs are being used in the medical field to visualize neurons and other things I can’t comprehend.
As I have said before, I feel as if your product is exaggerated. Now I don’t mean to attack but to be honest, I can’t stand people promoting their products to be the best of the best without supporting benchmarks, by benchmark I mean anything that can be measured in products
I see how my presentation may have come off as exaggerated or lacking measurable support, which wasn’t my intention. I built the color wheel after noticing a gap in existing solutions: many games, like Dress to Impress, offer limited color options through static lists.
That said, I agree my research could have gone deeper. Moving forward, I’ll focus on providing clearer benchmarks and platform support details to better validate the value of tools like this.
For clarity, the module is modular, works on mobile, and yields until the user selects a color or cancels, returning either the color or nil for easy integration. What are some suggestions you have to further improve my research process in the future?
The point is that on the dev forum specifically, that isn’t how things are done. Social media is fair game but the dev forum is meant to showcase resources, ask questions, and converse with other devs about Roblox development, not gain a following and what not.
I’m glad you understood. Nobody in this post said that your work is bad, it’s just that you were exaggerating your work and were trying to market it.
I also was very rude, for which I’m sorry. But I hope you understood your actions and you don’t do these things in the future.
Thanks for your feedback! To clarify, my goal wasn’t to promote myself or gain a following, but to share a tool I thought might genuinely help other developers. That said, I see now how the way I framed it might’ve come across differently, especially given the expectations of the dev forum
Specifically for this design, I think its engaging to see the product in use: to be provided a preview place and succinct text. I hate text walls and I see them constantly. I never thought this style was bad.
This is fine, it’s mostly the title in my opinion. Showing off your creation is 100% okay, especially using videos / images if you don’t want to type a bunch of text. Obviously detailing your post is a plus but I don’t think you’d get the same amount of backlash had the title been what you have now from the beginning. Yes there is some things I would change for example maybe not hyping up the product with text like:
But for me the main thing was the title. It’s okay to try and explain why your creation is useful, just don’t over do it here.
I am a bit sad to see that the resource has only been clicked on once. I know this is the consequence of clickbaity titles.
I also know that people may not actually need a color wheel. I just hope someone uses it. So this resource wasn’t a waste.
This is my preferred order of information:
- The reader can quickly digest and understand the resource and what it’s for, in other words, a brief overview
- Features & The main idea/focus
- Use cases (optional)
- The example usage with code
- Documentation & Tutorials (optional)
- Other metrics such as, platform compability, performance, etc…
I’m not against making your resource stand out like using symbols and adjectives. Unrelated but personally, I don’t care if my resource doesn’t get as much attention. My ideology is freedom of knowledge, that is why all of my work is under the MIT license (unless stated otherwise), so I don’t care if someone steals, or get inspired from my work because let’s be honest here, we all are guilty of it. I’m happy as long my resource can provide a hand to others
Thats a good style. How do you think visuals like videos should be used? I normally create a youtuibe video explaining the entire post at the top but I didnt this time
I would just use them for the sole purpose of examples and tutorials. I feel like text should suffice explaining, but thats just me
Yea i agree with that im plannin on doing this for future posts. Do u have any other advice
“its all so meticolously crafted and redefines how we color things and its so perfect” - chat gpt
bold statement buddy
print("Hello World!")
Well according to him, it’s his style of “marketing” and “engagement”.
Jesus christ, you don’t need to be so harsh. He at least did a job, I know damn well my ass ain’t asking chatgpt to make all of this - would you? Do you feel like a hero being rude to people on the DevForum? He provided us with something, and it works so why should we care?
I still don’t know what the clickbait title was
Guys starting to think this is the reincarnation of chaseroony with the AIposting
This reminds me of ColorPane but very barebones ngl, this is basically just studio’s built-in color picker, but even then that’s better than this dude
Thanks for the feedback regarding gods color. To clarify, God’s color is an asset for game developers to give their players.
Gods color is not designed to replace roblox’s default color editor. in fact, it cannot be compared to Robloxs default color editor in any way because they are entirely different. My color wheel is given to players in video games for color selection while the default editor is for developers to edit their creations. The functionality mentioned [having a editor very similar to roblox’s] provides a great deal of detail and suitable for most applications. Many games that prompt users for color selection typically do not offer this level of detail.
Additionally, Gods color is extremely easy to use, increasing its accessibility for developers. Simply require the module located inside of the GUI
Iocal GodsColor = --add here
local module = require(GodsColor.Prompt)
Then initiate the prompt function
local result = module.prompt()
The result is the color they selected. If they cancel the prompt it will return false. You can easily implement gods color wheel in your scripts with this accessibility.
I hope I was able to clear this misconception and that you find use in my asset: God’s color.
this response feels ai generated, especially this