#Thread Errors Issue

1 messages · Page 1 of 1 (latest)

frigid tendon
#

I'm making a dialogue system for my 2D game. I got these weird errors that are confusing and don't help me much. They appeared after I turned the variable for dialogue from a single string to a list of multiple strings

#

@young patrol here

#

okay so

#

do you prefer me to stream or to just send the code here?

main cedar
#

!cod

lofty heraldBOT
# main cedar !cod
<:error:1413114584763596884> Command not found

There's no command called cod.

main cedar
#

!code

lofty heraldBOT
frigid tendon
#

by the way, the editor is glitching out

#

wtf is happening

#

i restarted the editor multiple times

#

how does that have anything to do with the code

#

this is Interactable.cs


public class Interactable : MonoBehaviour
{
    public string[] dialogueLines;

    public void Interact()
    {
        DialogueManager.Instance.ShowDialogue(dialogueLines, 0);
    }

    public void StopInteraction()
    {
        DialogueManager.Instance.HideDialogue();
    }
}```
#

I'm pretty sure it's not my code's fault that the text editor is glitcht. the text disappears then reappears, even after multiple restarts

#

I'm desperate

young patrol
#

this looks like something going wrong in the drawing inspector process

#

what version of unity are you using ?

#

try testing this code in a blank project and see if the same thing happens, narrow it down to see if its your project or editor

frigid tendon
young patrol
#

this is partially why I don't use the beta versions

main cedar
#

that isn't a beta version

young patrol
#

6.2 is not preview/beta ?

main cedar
#

it's the current version

#

the f means it's a full release

young patrol
#

ohh but its not LTS ?

main cedar
#

alpha/beta versions are denoted by a/b in that position

frigid tendon
#

should I use a LTS one? idek what it mean

main cedar
#

6.3 is currently "beta" because there aren't any full releases, but once there are, there will be full 6.3 versions and beta 6.3 versions (and alpha 6.3 versions)

young patrol
#

either way I'd stick to LTS

frigid tendon
young patrol
#

"Supported" is very misleading

main cedar
frigid tendon
#

i also have this other one which is LTS, but i used that 2 years ago, not for this project

young patrol
#

cause its "supported" until 6.3 comes out, then its no longer updated

frigid tendon
#

i'm creating an empty 2d project with the same 6000.2.6f1 version

young patrol
#

production ready you wanna stick with LTS versions

frigid tendon
#

i'll just paste in the code and the game objects and see if the error occurs again

frigid tendon
#

i did use unity a few years ago

#

but always did very basic things

#

never completed a project. i'm still a beginner and not expert at all

young patrol
#

I personally would . especially if this is project you plan on releasing

frigid tendon
young patrol
#

downgrading a project is painful (mainly fixing the UPM / manifest for packages) , if you can help it just export all your current assets with a UnityPackage file so you can just plop that in the LTS project

frigid tendon
#

i haven't added many things, switching now wouldn't be a pain

young patrol
#

ya usually you can just drag and drop the old files in new project, but easier to make a .unitypackage file

frigid tendon
#

pasted in the assets

#

same issue

#

this is frustrating

young patrol
#

now I would try the LTS version and see what happens..knowing unity and how they release the "latest" I'm willing to bet that Unity version is busted

#

the "latest" you really never know what you're going to get, like any other software you fix one thing you bust 3 others some times lol

frigid tendon
#

I will try that later/tomorrow, pretty tired now

#

thank you, I'll reach out again

young patrol
young patrol