Small documentation issues
scorbett123 opened this issue ยท 12 comments
This issue is for people to list small documentation problems that they found so that they can all be fixed in one pr.
If you find a documentation issue please comment it here and I will add it to the todo list:
- Add an example of using a quantity in mine process
A quick read through Usage.md and a few things I remember
- You need to say
reset all
(notreset
) andreset <setting>
(not<setting> reset
) - To reenable
chatControl
andprefixControl
you should remove one or both lines, not the whole file - Further down the file and also in it's help text
#blacklist
seems like it affects anything but it's only forGetToBlockProcess
(could be seen as a bug/missing feature forMineFrocess
andBuilderProcess
as well) - We have about 200 settings not about 100
Documentation of#eta
should mention times being measured in ticks (or we change them to seconds)#axis
help says it sets goal to x=0 or z=0; x=z and x=-z and the restriction to y=axisHeight
are missing- Documentation of the return value of
ToolSet.materialCost
omits -1 for non-tools
Should be a javadoc link ({@link #buildSubstitutes}
)
Whilst doing this we should probably also edit some messages such as:
This line shouldn't exist
We should mention that Baritone doesn't support all formats or even list the supported formats here
There's so many people opening bug reports because Baritone outputs this message for .litematic and .nbt
"cannot" is one word
this comment is obsolete
Settings javadoc should describe the setting, not the default value (it is ok to use the default as an example though). These descriptions currently read as if the setting was a toggle between not using the feature and using it with that one specific value.
We should mention what kind of jumps Baritone can currently do.
This should be removed or turned into debug output
This should be "Paste"