#A Thingy

1 messages · Page 1 of 1 (latest)

lament summit
#

Would you like the ores the player is currently holding onto to be saved when the player leaves and rejoins?

lament summit
# open jolt yea

yikes, alright, you want the easy way, or the hard way?
Hard way saves chips and cloud data, easy way is easier but uses alot of cloud data

open jolt
#

The Hard Way

lament summit
# open jolt The Hard Way

Have a string variable and configure it and enable Cloud, this means the data saves even when you leave/rejoin

Decide the max number of ores a player can pickup at a time, lets say its 9999 (this would be the max amount you can EVER pickup, you can set your own custom limits later)

9 max ore lets you store 512 different types of ores with one variable
99 max ore lets you store 256 different types of ores with one variable
999 max ore lets you store 128 different types of ores with one variable
9999 max ore lets you store 64 different types of ores with one variable
99999 max ore lets you store 32 different types of ores with one variable

Now that we've decided your limits, lets store the ores!

Define each of your ores an index, lets say you have the ores Coal, Copper, Iron, Gold, Emerald, Diamond
Coal = 0
Copper = 1
Iron = 2
Gold = 3
Emerald = 4
Diamond = 5

All these indices do is tell your circuits "This is where this ore goes in the "Backpack", this defines its order"

Now that you have defined these, you can follow the image below:

#

Now, whenever you sell, you need to go through the every amount of ore the player has, sell the ore for that value, and then set the amount of that ore to 0000

#

closer look

The String Substring with the "0000" inside it should have as many 0's as the number of digits in the max ore number of digits

open jolt
lament summit
# open jolt I think I got this, but where do I put the list of ores and how much it gives?

Me personally?

  1. I'd use an Event Definition, rename it "Ore Settings", and I'd add 2 inputs, a List<String> for Ore Names and a List<Int> for Ore Prices
  2. When the local player joins, I'd send the event Ore Settings to local

This way you can set the ore prices and names however you want, and they will update when you rejoin (or re-execute the event), making them super cheap to take from as they are "baked" into the event

open jolt
#

Sorry the pictures positions are switched, idk why it did that

lament summit
lament summit
open jolt
#

So I need to add 512 Zeros in the Local Or In Backpack?

open jolt
#

That's A lot, Okay.

lament summit
#

its how much you have of each ore, by default should be 512 0's

open jolt
#

I'm gonna be making it so there are around 32-64 Different Ores

#

And max backpack will be around 10-15

#

I haven't decided it all yet so its mostly all estamates

lament summit
#

I'd go with 64

#

roughly 10,000 ore is ALOT

sand lance
#

Can anyone help me?

open jolt
#

What do you mean 10K ores, I am very confused. I mean 64 different types of ores. (Sorry I'm slow on some things I might seem very dumb)

graceful quiver
lament summit
#

my math is prob wrong lol

graceful quiver
sand lance
open jolt
#

@grave yew