Arrays

[Kreerio]

You should add arrays like scratch lists so people can read info from a array to do stuff like enemy spawns or a fnf charting system!

[DoomTas3r]

Blocks from Scratch and what they could look like in Block Coding:
add (thing) to my_list as append (variant) to my_array
delete (1) of my_list as remove (0) of my_array or unchanged
delete all of my_list as clear my_array or unchanged
insert (thing) at (1) of my_list as unchanged
replace item (1) of my_list with (thing) as set (0) of my_array to (variant)

my_list as unchanged or removed
item (1) of my_list as (0) of my_array
length of my_list as unchanged or size of my_array
my_list contains (thing)? as (variant) is in my_array

This block wasn't as simple:
item # of (thing) in my_list as index of (variant) in my_array or -1

Other useful GDScript functions:
append_array(array: Array)
assign(array: Array)
duplicate(deep: bool)
reverse()
shuffle()
slice(begin: int, end: int, step: int, deep: bool)
sort() (Unstable sorting algorithm)

Scratch doesn't use lists as unique arguments and instead converts them to generic values (["thing", "thing"] becomes "thing thing"). In GDScript, arrays can be passed as arguments to functions (my_other_array.assign(my_array)), but functions that take or return arrays seem to be limited, which is why my_list as a block could be removed in favor of dropdowns.

Getting an element from an array typically involves an index that can be out of bounds. In Scratch item (-1) of my_list would return an empty value, but in GDScript my_array[-1] would be caught and return an error. For Block Coding, which would be preferable?

In my opinion, the error should be kept since an empty value would have to be handled anyway, and so that users wouldn't get unexpected values or expect default values in other languages, especially manual memory languages like C.

Also, I think that 1 dimensional arrays would be the baseline, considering typed arrays such as Array[int] when propagating its type int to (0) of my_array.

[Kreerio]

exactly what i was thinking!

[manuq]

Interesting discussion. My main question would be what's the application, why would you need the array handling. You mention "enemy spawns or a fnf charting system". I don't know what is the latter, but for spawining we have high level blocks in the SimpleSpawner node. Then you can configure the node properties in the Inspector and add a BlockCode as child to use the high level blocks like "start spawning" or "stop spawning". This is also what you would do regularly in Godot, create a spawner node, unlike in Scratch were everything has to happen programmatically.

[Kreerio]

you would need this for other things also fnf charting system needs arrays to work its so you dont have to chart mannually

[DoomTas3r]

I think an fnf charting system generally translates to recording input for playback. In fnf's case, recording would happen in a chart editor, then played back to challenge the player to keep up (but it looks like most people use generic variables since they have indexing like lists).

As for other Scratch examples, lists are used for inventories, decks of cards, storing path coordinates, and keeping chat logs. For a card game, drawing cards, discarding, picking, shuffling, and sorting could be represented by append(), remove_at(), my_array[], shuffle(), and sort(). Also, dictionaries aren't in Scratch, but they could be used for inventories as well.