• Nibodhika@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    6
    ·
    1 day ago

    For prototyping you usually use any assets you have lying around, using AI for that is not cutting corners it’s more expensive and labor intensive but gives you a better feel for what you’re trying to build. Usually prototypes are done with either plain colors or just assets you downloaded from random sources or have from previous games, it’s just to get an idea whether the gameplay is fun enough to build the entire thing.

      • Nibodhika@lemmy.world
        link
        fedilink
        English
        arrow-up
        8
        arrow-down
        5
        ·
        1 day ago

        Tell me you’ve never worked on a game without telling me you’ve never worked on a game.

        Sometimes (and by that I mean 99% of the times) you just don’t have the funds or time to make assets for a prototype, you need a fast iteration cycle to nail the core mechanics. You need to learn as soon as possible if the game works or not, and while doable with Mario and Pikachu sprites it’s much better if you can get a feeling for the atmosphere as well to see if it matches. This is the first hours of game development, after the initial GDD and before you even consider the full scope of the game.

        But I don’t expect someone who sees in black and white to be able to understand the many scales of grey there are in this. Using assets without copyright for them is also wrong, yet that’s a daily occurrence in prototyping, because you’re not going to spend time and money building assets for an idea to check if it’s worth investing time and money into, that defeats the purpose.

        • rockerface🇺🇦@lemmy.cafe
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          4
          ·
          1 day ago

          Using assets without copyright for them is also wrong

          Yeah, okay, we’re done with this discussion. Pro AI and pro copyright? I pity whatever projects you were allowed to contribute to.

          • Nibodhika@lemmy.world
            link
            fedilink
            English
            arrow-up
            4
            arrow-down
            2
            ·
            1 day ago

            I’m not pro AI, I’m fairly against it in most uses, but I do recognize it has some applications, and trying to close your eyes to it and day it’s all bad is just not productive to any sort of serious discussion about it.

            As for copyright, yes, I’m in favor that some form of copyright should exist, although companies abuse that right and that shouldn’t be allowed.

              • Nibodhika@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                ·
                14 hours ago

                Well, first of all the majority of the discussion was around assets which are not what most people have in mind when they talk about software development. But also LLMs work great for their intended purpose of auto completion, even a local model running on your own machine is miles ahead of the snippet libraries we used to use until recently. Also they can spot errors in your code much better than you yourself can, as they’re essentially impartial and looking for patterns that have previously been reported as causing issues statistically, while you are biased towards the mistakes you usually make.

                I wouldn’t trust anything it outputs any more than what I would trust something written by an 8 year old on heavy doses of stimulant drugs, but in reduced scope and limited capacity they’re quite useful, and can help in some tricky situations like memory corruption or threading issues.

                That being said I strongly support that vibe code is not trustworthy and anyone who does that is essentially gambling with that code.