I make 2d struct array to hold event infos works fine but whenever ı add new element in arrays this error occur but when I restart game everthing get fixed is it normal ?
and is there anyone who know how can I change element 0,1 etc names to something more meaningful. I know ı can add string name but this time I have to write all of them by one by. for expemle they can get their struct name and order number like atk 1, atk 2, it would be awesome.
// @kurtdekker - cheap and cheerful way to name
// array elements in a Unity Editor Inspector array
[System.Serializable]
public class Thang
{
public string Name;
public int Age;
}
and declare a collection thereof:
public Thang[] MyThangs;
And off you go!
I couldn’t believe it when I saw that posted a month or two ago. Wow. Cheesy-easy!
That complaint about not wanting to type it in… I would never hand-type everything in either. I’d make a little editor script to inject your presets of editable names from your whatever, enum, database, filestore, whatever
Or write an Editor Script, either way. But writing custom drawers when this suffices. Meh.
Admittedly I didn’t realise that the labels in your screenshot had updated to reflect the fields contents. That’s a really weird thing to be embedded in the list drawer. I wonder what the exact conditions for qualifying for it are. Just a member called ‘Name’?
OP is in a newer version of Unity that’s using the UI Elements ListView visual element, however, so this feature may not carry over.
Really wish Unity would add some attributes to make modifying the drawers of some visual elements a lot easier, such as Odin Inspector’s [ListDrawerSettings] attribute that lets you modify their (far better) collection drawer.
It’s a pretty deep topic, honestly. Custom inspectors and property drawers aren’t super newbie friendly, though Unity has tried to make the documentation more comprehensive on them.
I concur with this. Doesn’t seem to matter what the string variable is actually named.
After brief experiments, the rules I can infer are:
if the first field (in code-appearing order) is a string, and it is non-null and non-empty, the editor picks it up as a label.
if subsequent fields are strings, doesn’t matter.
if the first field isn’t a string, labels come out as Element 0, etc.
Neato.
The approach above is still NOT how I would label stuff! If you did, then you are on the hook for finding it by string as well in code, which is just a disaster waiting to happen, keeping those strings in sync.
This super-basic data authoring use case is purpose-built for ScriptableObjects: just use the actual filename of the ScriptableObject itself as the primary key.
The benefit of that is if you put all the ScriptableObject instances in a folder, the operating system prohibits you from having duplicate primary keys.
With clever dynamic loading via Resources.LoadAll() (or Addressables if you insist), you never even drag any of them into anywhere. You just edit them, add them, and the code can discover them all at runtime. It is glorious.
