Bucket Volume: Or, imperial vs metric.

[TheGreyGhost 808]

2 hours ago, hanetzer said:

Honestly I don't think mb would be useful to keep around, or perhaps keep it equal to a bucket ounce/whatever

so folks doing chem mods which use liquids which never become blocks (or came from blocks) can stay metric.

I agree, they can define their derived units of measure to be whatever they want (in terms of conversion from the smallest possible unit i.e. atom or bucket ounce etc ), and display it to the user however they want.  I don't think that needs to be standardised between mods?  

I think the proposed 1296 ounces (81 * 16) seems a reasonable tradeoff between granularity (from a user's point of view) and the maximum blocks in an int (i.e. 2^31 / 1296 ~ 1.6 million)

 

nugget    16 oz
ingot    144 oz
block    1296 oz
pane    81 oz

1296 seems to be a good number if you just throw away the milliBuckets name and replace it with something non-metric.  For folks raised in metric countries, milliBuckets != 1/1000 is extremely confusing.

 

An alternative thought - perhaps you want even divisibility by each "voxel" in a block, i.e. 16x16x16 = 4096,  x 81 = 331776 atoms per block

 

ounce = 256 atoms

nugget = 16 oz =  4096 atoms 
ingot = 144 oz =  36864 atoms
block = 1296 oz =  331776 atoms

 

voxel = 81 atoms
single line = 16 voxels = 1296 atoms
pane = 16 lines = 20736 atoms

block = 16 panes = 331776 atoms

 

That give you a maximum of ~6400 blocks in a single 31 bit int.  That seems like plenty?

 

 

 

 

 

[Draco18s 2323]

1 hour ago, TheGreyGhost said:

i.e. 16x16x16 = 4096,  x 81 = 331776 atoms per block

This is too big of a number. Quick, what's 1/9th of it?

[TheGreyGhost 808]

Well the idea is that users won't know anything about atoms.  It's for the coders only.

The user will know about

ounces, nuggets, ingots, and blocks, or voxels, lines, panes, and blocks. 

 

Or some arbitrary measure such as grams, kilograms, tons, or just an inexact decimal representation such as 0.153 blocks.  They'll have no idea how many atoms are behind the scenes.  

 

Edited June 23 by TheGreyGhost

[DavidM 177]

Honestly I would say having so many units would be confusing to new players (and some old players).

I don't see how remembering ounces, nuggets, voxels and the conversions between them is easier than "144mb an ingot, 1000mb a bucket".

Without a unified measurement (mB), some modders may start to favor certain units over the others, or invent their own units based on atoms, causing more confusion in the system.

Edited June 23 by DavidM

[TheGreyGhost 808]

4 minutes ago, DavidM said:

Honestly I would say having so many units would be confusing to new players (and some old players).

I don't see how remembering ounces, nuggets, voxels and the conversions between them is easier than "144mb an ingot, 1000mb a bucket".

Without a unified measurement (mB), some modders may start to favor certain units over the others, or invent their own units based on atoms, causing more confusion in the system.

that's the problem - i.e. an ingot is approximately 111.1111111 mB.  Your system of units has to be consistent.

 

The bottom line is that you have to make tradeoffs for the user, i.e. you either use a decimal representation that is inexact, or you define exact units which will be unwieldy numbers.  The whole metric vs imperial argument eg 15.363 kg vs 30 lb 3 oz.

 

One set of exact units works fine with "nice" numbers if you are dealing in whole amounts of nuggets (i.e. 9-based)

A different set of exact units is more "natural" if you want slabs (or 16-based such as 16x16x16 voxels)

 

When you mix the two together (for example you want to melt nuggets into panes) then you will always have residual bits left over that become messy.

 

If I were implementing a user interface for this, it would for sure be an inexact decimal representation (with an exact count behind the scenes).  For any practical use that I can think of, the user would not care if an ingot is shown as 111 mB instead of 111.11111 mB.

 

[Alpvax 34]

Bear in mind that more players use metric systems than imperial (according to minecraft server statistics, and the fact that there are few countries which still use the imperial system).

It is far easier for users to understand that half a bucket is 500mb, than it is for them to see 648 "atoms" (If that is the approach, I would prefer to use something like "voxellites" which has no real-world bearing than "atoms" which could cause huge confusion for users of chemical mods).

And to the next argument that you would just display it as "3 1/2 buckets" or 3 1/1296 buckets", that is hugely unnatural for me (and presumably many others).

 

I'm not sure what the issue with 144mb/ingot is. Why does a melted compound have to fit in the same space as a solid one? It doesn't in real life.

And as far as cauldrons, I think it's fair enough to just lose 1mb in a cauldron. Who cares about 1/1000 of a bucket of an infinite resource? And for those mods which have finite supplies of water, they usually add their own mechanisms for collecting/storing it, so the cauldron issue is moot.

[TheGreyGhost 808]

Howdy

9 hours ago, Alpvax said:

Bear in mind that more players use metric systems than imperial (according to minecraft server statistics, and the fact that there are few countries which still use the imperial system).

It is far easier for users to understand that half a bucket is 500mb, than it is for them to see 648 "atoms" (If that is the approach, I would prefer to use something like "voxellites" which has no real-world bearing than "atoms" which could cause huge confusion for users of chemical mods).

And to the next argument that you would just display it as "3 1/2 buckets" or 3 1/1296 buckets", that is hugely unnatural for me (and presumably many others).

 

That's for sure... the long slow death of the imperial system can't come fast enough for me.  

Just to be clear - I'm not proposing that the users will ever know about the "atoms" or "voxellites" or "grains" or whatever, that's just an internal representation.  The amount of fluid is stored using an int, i.e. 

final int FLUID_AMOUNT_ONE_VOXELLITE = 1;
final int FLUID_AMOUNT_ONE_NUGGET = 4096
final int FLUID_AMOUNT_ONE_NUGGET = 4096
final int FLUID_AMOUNT_ONE_BLOCK = 4096*81;
//etc

addFluidVoxellites(int voxellites) {
  this.fluidAmount += voxellites;
}

addFluidNuggets(int nuggets) {
  this.fluidAmount += FLUID_AMOUNT_ONE_NUGGET * nuggets;
}

addFluidMilliBlocks(float milliBlocks) {
  this.fluidAmount += (int)FLUID_AMOUNT_ONE_BLOCK * milliBlocks;
}

 

 

9 hours ago, Alpvax said:

I'm not sure what the issue with 144mb/ingot is. Why does a melted compound have to fit in the same space as a solid one? It doesn't in real life.

 

THe round trip is the problem.  In real life, you get conservation of mass i.e. if you melt the compound then freeze it, you get the same mass as before.

if your ingot is 144/1000 of a bucket, then converting ingots to buckets and back again gains you several extra ingots.

If you define a bucket as 1296 "millibuckets", then every metric-system-based user thinks you've taken leave of your senses

 

Cheers

  TGG

 

[Alpvax 34]

13 hours ago, TheGreyGhost said:

THe round trip is the problem.  In real life, you get conservation of mass i.e. if you melt the compound then freeze it, you get the same mass as before.

if your ingot is 144/1000 of a bucket, then converting ingots to buckets and back again gains you several extra ingots.

I don't see how that is true at all. Why does 1 block have to fit in 1 bucket? If we just accept that 1 block is 1296mb, everything works.

I don't see why we have to add the restriction that 1 bucket is 1 (solid) block. We can just accept that melting it makes it less dense, therefore bigger.

[TheGreyGhost 808]

9 hours ago, Alpvax said:

I don't see how that is true at all. Why does 1 block have to fit in 1 bucket? If we just accept that 1 block is 1296mb, everything works.

I don't see why we have to add the restriction that 1 bucket is 1 (solid) block. We can just accept that melting it makes it less dense, therefore bigger.

Howdy

The problem is that you're breaking the minecraft conventions to do that, for an arbitrary coding implementation reason.

Minecraft convention is:

9 nuggets per ingot

9 ingots per block

1 block = 1 bucket (think lava or water being filled into a bucket and back again).

 

This magic number 1296 (16*81) is only important behind the scenes, as a coding implementation, the user doesn't need to know about it at all.  The whole millibuckets question is actually a bit of a red herring, because there are really two parts to this

1) what's the internal representation of a fluid (the "atoms" or "voxellites" or whatever)

2) what do we do with the currently-accepted user convention of "millibuckets"

 

personally I think the best answers are:

1) 4096*81 = 331776 units per block (i,.e. final int FLUID_AMOUNT_ONE_BLOCK = 4096*81;) which allows exact representation of all the standard objects that we're interested in (and hence gives conservation of mass with no round-trip-gain-or-lose-mass problems);

2) leave milliBuckets as 1/1000 of a bucket, and present it to the user in an (inexact) metric format eg "one nugget = approximately 111 mB"

 

-TGG

[laz2727 0]

I would rather not have fluid units as a float. That just sounds like trouble.

[Alpvax 34]

16 hours ago, TheGreyGhost said:

1 block = 1 bucket (think lava or water being filled into a bucket and back again).

I don't agree with that logic.

Yes, 1 bucket of a fluid is 1 block of the fluid (although it actually doesn't quite reach the top, so you could argue that is not true), but there is nothing saying 1 solid block is equivalent to 1 bucket of that material melted down.

Liquid doesn't have ingots or nuggets, so those solid conversions do not need to apply to them.

If we keep it as 1 block of a solid becomes a bucket-and-a-bit, all it means is that you don't fit an even number of blocks into your tanks. But I don't see why that is an issue, because once you have converted it to a fluid, whatever you're using it for (machines?) probably doesn't care about the solid amount.

If you want to transfer exact amounts, use the blocks. They are probably easier to transport anyway (there is a vanilla mechanic for it, and you can usually carry 64 per inventory slot as opposed to the 1 in a bucket).