hollow citrus
Insight:
So, I'm making a cube fusion type game, basically a bunch of cubes, fuse them, make a bunch of items
while the script i have runs great now, editing each cube whenever i want to make a change will most likely make this game way harder to create.
problem:
How do i give each cube a easily editable script but aswell able to have different variables and tables.
jolly obsidian
Insight:
So, I'm making a cube fusion type game, basically a bunch of cubes, fus...
well you shouldnt spam scripts under parts
just have one main controller
that will keep track
hollow citrus
just have one main controller
How would this work
jolly obsidian
How would this work
have table per part
so you can just
easly keep track of properties
and loop to connects touched or whatever you need
hollow citrus
have table per part
like put the parts in the table?
jolly obsidian
ye
hollow citrus
ok 🤔
jolly obsidian
when spawning you can either tag them
or just
spawn then in same script
so you can add to table right away
hollow citrus
when spawning you can either tag them
Alright
mossy mango
hollow citrus
when spawning you can either tag them
now this i understand, and how to add the tags, but the problem i have is: how to make sure each tag has a different dictionary for the different fusions
green torrentBOT
** You are now Level 1! **
jolly obsidian
now this i understand, and how to add the tags, but the problem i have is: how t...
thats not how what you should use for
tag i meant collectionservice
so you can get all parts easly
then just have values[table] = {]
hollow citrus
then just have values[table] = {]
in which part, each cube?
or wait, realized i worded that message wrong:
How to make sure each tag cube has a different dictionary
hollow citrus
i was asking a question
but i used names because i continuously clone and aswell use names for a furnace
should i still change that to instances?
hollow citrus
dir[cube] = {}
was asking like if cube was the name
hollow citrus
dont use names for indexes
Ok
jolly obsidian
i dont get it
hollow citrus
i dont get it
:
what i have been doing to note if each cube was a specific type of cube was the name of it: "blue cube" or "green cube"
i clone each cube multiple times so that the players can continuously be able to make fusions
thought using names was a better idea due to the fact multiple cubes would be the same type
im pretty bad at explaining things though
vocal slate
U mean base stats?
Dunno
Personally i think that @jolly obsidian suggestion is alright
If u keep track of all cubes on a plane it will be a lot easier to operate on them
For example to detect if both cubes are touched, or maybe in range
To delete certain one
U can make your dictionary kinda clean
Local Cubes = {
["Blue"] = {...},
["Red"] = {...}
}
With that u can find one by their names. And also remember to keep index as an instance
Why to keep index as instance tho? Cuz u were confused
Imagine two cubes touch eachother, how u will find which one touched? Or which one with? U can take those ones who touched and simply take instance from it in a workspace
local TouchedCube = Cubes[touched]
should i make my dictionary like that? cause i was gonna:
["Blue"] = {
["Red"] = "Magenta"
}
Just now getting home
vocal slate
cant you just use for loops
Duh
vocal slate
cant you just use for loops
I just gave him a suggestion how he would male this
hollow citrus
```lua
Local Cubes = {
["Blue"] = {...},
["Red"] = {...}
}
```
With ...
should i be using a module script for this to add it to the modules dictionary?
and how should i go about adding each fusion to the single cubes dictionary inside the dictionary
vocal slate
should i be using a module script for this to add it to the modules dictionary?
...
huh
U can make it in different way
Every cube can hold a value that indicates their fusion multiplication
For example if we merge cubes with 2, so its indicator will be 4 obiviously. And for each multiplication u can apply some effects or boosts
Its my idea atleast
If u want to go with names then keep it in dictionary
hollow citrus
For example if we merge cubes with 2, so its indicator will be 4 obiviously. And...
so uh this probably comes with a lack of information on my side
its not those uhh merge 2048 games
cube fusion games u merge cubes to create diff things like swords and armor and healing stuff to fend against (cube combination, cubination, cube fusion)
certain cubes can only fuse with others
green torrentBOT
** You are now Level 2! **
vocal slate
so uh this probably comes with a lack of information on my side
its not those u...
Oh, u meant this kind of game
My bad
hollow citrus
yeah
vocal slate
hollow citrus
the sky spawns cube types
green red blue white
dirt rock ice
You have tools aswell, a furnace, a researcher, and a dictionary
you try to mix dirt with white cube, nothing will happen
you smelt dirt in a furnace, dirt will become an iron bar or gold bar
mix iron bar with white cube you get iron cube
but
you can also mix iron bar with a red cube to create a throwable cube
vocal slate
Ohh, so keep every fusions or craftings in a modules like a data to return
return {
}
and then i put the individual cubes in a tag using their instance?
vocal slate
Wdym in a tag using their instance
😭
Oh u meant in a dictionary that holds every cube, am i correct?
hollow citrus
```lua
Local Cubes = {
["Blue"] = {...},
["Red"] = {...}
}
```
With ...
you guys said earlier:
put each cube into a dictionary using their instance as the index
i think
vocal slate
You refer tag as a index
hollow citrus
ya cus i was planning on using the collection service since i recently re-learnt about it
does it like not work for this typa thing?
vocal slate
It works for every instance
In a workspace ofc
Well
I have to ask
When you fuze items, do they lay on the ground?
hollow citrus
When you fuze items, do they lay on the ground?
ya
vocal slate
So as i suggested you can put every one of them in a dictionary
Easier to track one of them
hollow citrus
Ok