added support for loading textures directly out of texture packs
This commit is contained in:
@@ -305,9 +305,11 @@ Less Useful Options
|
||||
|
||||
.. cmdoption:: --textures-path <path>
|
||||
|
||||
Use this option to specify an alternate terrain.png to use for textures when
|
||||
rendering a world. ``path`` specifies the **containing directory** of
|
||||
terrain.png.
|
||||
Use this option to specify an alternate terrain.png (and other
|
||||
textures) to when rendering a world. ``path`` specifies the
|
||||
**containing directory** of terrain.png. Alternately, ``path`` can
|
||||
specify a zip file containing the textures, such as a texture
|
||||
pack.
|
||||
|
||||
The Overviewer will look for terrain.png in the following places in this
|
||||
order: path specified by this option, the program's directory, the
|
||||
|
||||
@@ -90,9 +90,13 @@ You have several options:
|
||||
file in the same directory as overviewer.py or overviewer.exe. For
|
||||
installations, you will need to specify the path... see the next bullet.
|
||||
|
||||
* You can put a terrain.png file anywhere you want and point to its location
|
||||
with the :option:`--textures-path` option. This should point to the directory containing
|
||||
the terrain.png, not to the file itself.
|
||||
* You can put a terrain.png file anywhere you want and point to its
|
||||
location with the :option:`--textures-path` option. This should
|
||||
point to the directory containing the terrain.png, not to the file
|
||||
itself.
|
||||
|
||||
* Alternately, you can download any texture pack ZIP you like and
|
||||
point to this directly with :option:`--textures-path`.
|
||||
|
||||
Note: the :option:`--check-terrain` option is useful for debugging terrain.png issues.
|
||||
For example::
|
||||
|
||||
Reference in New Issue
Block a user