Incremental UI Pack for Sale!🔥
Animated and Scaled✅
30 USD/10k R$ + Tax💸
Shop Frame
Codes Frame
Main HUD
and More....
📩Dm xxruu007xx on discord to purchase
Tags: #roblox#robloxui#uipack#robloxdev#forsale
Incremental UI Pack for Sale!🔥
Animated and Scaled✅
30 USD/10k R$ + Tax💸
Shop Frame
Codes Frame
Main HUD
and More....
📩Dm xxruu007xx on discord to purchase
Tags: #roblox#robloxui#uipack#robloxdev#forsale
🚀 Missile & Rocket Pack 💥
📦 6 Unique Missile / Rocket Models
🎨 Highly Customizable (Easily tweak colors, textures)
📸 6 High-Quality Renders (One for each model included)
💰 Available for only R$2.5K+TAX!
Contact on discord: rudrag (Karuki)
BECOME A SCRIPTER!
If there's one thing I had to say that's the most important on roblox it's probably scripting.
"What about AI?"
You still need the logic, and intermediate scripting knowledge to use it, and to fine tune it.
You also save alot of $$$ ;)
On the AI spectrum, the opposite ends seem to be
< (People who oppose AI entirely and type out their code by hand) ------------------ (People who are on the hype train and blindly trust AI to do all their coding)
I'm somewhere in the middle. Here's my current stance on AI and coding (for long-term projects): If you cannot code and are prompting AI to code for you and are blindly accepting its changes without understanding the code, you are accepting short term reward for long-term detriment.
At some point, the AI will start failing to understand its own code and your code base will be all over the place.
If you can code and you are coding alongside AI, and are double checking its code, making sure its structure won't cause future problems, good practices, exploit prevention, learning with it, etc.. I think it will make you an OP scripter. To do all this requires you to already be able to code to some degree.
Someone who understands the code and also uses AI to speed up development will have a much easier time fixing bugs, as they have a high level understanding of everything.
If a bug occurs that AI has a hard time fixing, the person who can understand the code can probably narrow it down to script X, function Y. The person who blindly trusts it will just be begging it to fix it for a long time.
The way I currently use AI is I write a lot of the starting codebase myself. I think about the structure, type definitions, functions I want, etc.
And then, I start working alongside it, prompting it to make functions, subsystems, etc. I aim to make sure that I understand the codebase at a high level.