[snufalufugus]

Any time you're producing something out of two stackable ingredients, the MakeAllInterface doesn't have a make all option.

• It's not always a MakeAllInterface, so the name is inaccurate
• There is no way to get the selectable quantities to get the best option to select (there is `MakeAllInterface.getSelectableItems()` but not a `MakeAllInterface.getSelectableQuantities()`)

pls resolve

 

[wet rag]

Support

 

[mmaaikel]

Create a method for it then

 

[snufalufugus]

Create a method for it then

u

 

[cloud]

Any time you're producing something out of two stackable ingredients, the MakeAllInterface doesn't have a make all option.

• It's not always a MakeAllInterface, so the name is inaccurate
• There is no way to get the selectable quantities to get the best option to select (there is `MakeAllInterface.getSelectableItems()` but not a `MakeAllInterface.getSelectableQuantities()`)

pls resolve

MakeAllInterface is what Jagex refers to it as.

 

[wet rag]

MakeAllInterface is what Jagex refers to it as.

The update did a lot more than interface update, i.e there used to only be X, but now they added an ALL option

 

[cloud]

The update did a lot more than interface update, i.e there used to only be X, but now they added an ALL option

I'm referring specifically to the recently renovated, common interface that they have called the Make All Interface in several release notes.
 
Which is what the API is designed and expected to handle.
 
Furthermore @Snufalufugus, regarding a getSelectableQuantities() method, how do you propose that be handled considering there can be the X option along with All (All can be handled by returning a 0, but regarding the X option I don't see a good integer return value for indicating it's there)

 

[dark sage]

Furthermore @Snufalufugus, regarding a getSelectableQuantities() method, how do you propose that be handled considering there can be the X option along with All (All can be handled by returning a 0, but regarding the X option I don't see a good integer return value for indicating it's there)

would -1 be a valid option to use for the Make X option?

 

[cloud]

would -1 be a valid option to use for the Make X option?

Possibly, what does everyone else think?

 

[snufalufugus]

I'm referring specifically to the recently renovated, common interface that they have called the Make All Interface in several release notes.
 
Which is what the API is designed and expected to handle.
 
Furthermore @Snufalufugus, regarding a getSelectableQuantities() method, how do you propose that be handled considering there can be the X option along with All (All can be handled by returning a 0, but regarding the X option I don't see a good integer return value for indicating it's there)

You could just return it as an array of strings, and authors could use .equals() since you only use it to know what's there. Or -1 for X.

 

[cloud]

You could just return it as an array of strings, and authors could use .equals() since you only use it to know what's there. Or -1 for X.

Which would the rest of you prefer?

 

[mmaaikel]

-1 sounds oke

 

[wet rag]

-1 sounds oke

support

 

[snufalufugus]

@Cloud @Party got votes gonig - its pretty decisive for the -1 option

 

[party]

When would you ever want to use the MakeX option rather than the MakeAll option?

 

[dark sage]

When would you ever want to use the MakeX option rather than the MakeAll option?

When make all is not available

 

[wet rag]

When make all is not available

where is that?

 

[party]

When make all is not available

Do you know of any interfaces where there's a Make-X but no Make-All option?

 

[dark sage]

*EDIT* don't know of any that have the MakeX when MakeAll is not available. Altho there are some without MakeAll option

 

[wet rag]

When fletching items that are stackable. Arrows, darts, etc.

There is no interface for darts or bolts, arrows has a MakeAllInterface