Update doc modpack (1.2.2)
This commit is contained in:
parent
ed63c32f07
commit
2606c264b9
|
@ -41,7 +41,7 @@ this mod is capable of and how these use cases could be implemented.
|
|||
|
||||
### Simple use case: Minetest basics
|
||||
Let's say you want to write in free form short help texts about the basic
|
||||
concepts of Minetest or your subgame. First you could define a category
|
||||
concepts of Minetest or your game. First you could define a category
|
||||
called “Basics”, the data for each of its entry is just a free form text.
|
||||
The template function simply creates a formspec where this free form
|
||||
text is displayed.
|
||||
|
@ -233,7 +233,7 @@ The help starts with this default order:
|
|||
|
||||
This function can be called at any time, but it recommended to only call
|
||||
this function once for the entire server session and to only call it
|
||||
from subgame mods, to avoid contradictions. If this function is called a
|
||||
from game mods, to avoid contradictions. If this function is called a
|
||||
second time by any mod, a warning is written into the log.
|
||||
|
||||
#### Parameters
|
||||
|
|
|
@ -4,7 +4,7 @@ can access help pages about various things and the modder can add those pages.
|
|||
The mod itself does not provide any help texts, just the framework.
|
||||
It is the heart of the Help modpack, on which the other Help mods depend.
|
||||
|
||||
Current version: 1.1.0
|
||||
Current version: 1.1.1
|
||||
|
||||
## For players
|
||||
### Accessing the help
|
||||
|
@ -37,9 +37,9 @@ stored in the world directory in the file `doc.mt`. You can safely reset
|
|||
the viewed/revealed state of all players by deleting this file. Players
|
||||
then need to start over revealing all entries.
|
||||
|
||||
## For modders and subgame authors
|
||||
## For modders and game authors
|
||||
This mod helps you in creating extensive and flexible help entries for your
|
||||
mods or subgame. You can write about basically anything in the presentation
|
||||
mods or game. You can write about basically anything in the presentation
|
||||
you prefer.
|
||||
|
||||
To get started, read `API.md` in the directory of this mod.
|
||||
|
|
|
@ -689,7 +689,7 @@ do
|
|||
doc.data.players[name] = {}
|
||||
doc.data.players[name].stored_data = players_stored_data
|
||||
end
|
||||
minetest.debug("[doc] doc.mt successfully read.")
|
||||
minetest.log("action", "[doc] doc.mt successfully read.")
|
||||
end
|
||||
end
|
||||
end
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
# Lookup Tool [`doc_identifier`]
|
||||
Version: 1.2.1
|
||||
Version: 1.2.2
|
||||
|
||||
## Description
|
||||
The lookup tool is an useful little helper which can be used to quickly learn
|
||||
|
|
|
@ -36,7 +36,7 @@ doc_identifier.identify = function(itemstack, user, pointed_thing)
|
|||
mod = string.sub(param,1,colon-1)
|
||||
end
|
||||
end
|
||||
message = S("Error: This node, item or object is undefined. This is always an error.\nThis can happen for the following reasons:\n• The mod which is required for it is not enabled\n• The author of the subgame or a mod has made a mistake")
|
||||
message = S("Error: This node, item or object is undefined. This is always an error.\nThis can happen for the following reasons:\n• The mod which is required for it is not enabled\n• The author of the game or a mod has made a mistake")
|
||||
message = message .. "\n\n"
|
||||
|
||||
if mod ~= nil then
|
||||
|
@ -190,19 +190,19 @@ minetest.register_tool("doc_identifier:identifier_liquid", {
|
|||
on_secondary_use = doc_identifier.solid_mode,
|
||||
})
|
||||
|
||||
-- TODO: These crafting recipes are temporary. Add a different way to obtain the lookup tool
|
||||
--- TODO: These crafting recipes are temporary. Add a different way to obtain the lookup tool
|
||||
minetest.register_craft({
|
||||
output = "doc_identifier:identifier_solid",
|
||||
recipe = { {"group:stick", "group:stick" },
|
||||
{"", "group:stick"},
|
||||
{"group:stick", ""} }
|
||||
})
|
||||
|
||||
if minetest.get_modpath("mcl_core") ~= nil then
|
||||
minetest.register_craft({
|
||||
output = "doc_identifier:identifier_solid",
|
||||
recipe = { {"mcl_core:stick", "mcl_core:stick" },
|
||||
{"", "mcl_core:stick"},
|
||||
{"mcl_core:stick", ""} }
|
||||
})
|
||||
|
||||
minetest.register_craft({
|
||||
output = "doc_identifier:identifier_solid",
|
||||
recipe = { { "mcl_core:glass" },
|
||||
{ "mcl_core:stick" } }
|
||||
{ "group:stick" } }
|
||||
})
|
||||
end
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
Error: This node, item or object is undefined. This is always an error.\nThis can happen for the following reasons:\n• The mod which is required for it is not enabled\n• The author of the subgame or a mod has made a mistake = Fehler: Dieser Node, Gegenstand oder dieses Objekt ist nicht definiert.\nDas ist immer ein Fehler.\nDies kann aus folgenden Gründen passieren:\n• Die Mod, die dafür benötigt wird, ist nicht aktiv\n• Der Subgame-Autor oder ein Mod-Autor machte einen Fehler
|
||||
Error: This node, item or object is undefined. This is always an error.\nThis can happen for the following reasons:\n• The mod which is required for it is not enabled\n• The author of the game or a mod has made a mistake = Fehler: Dieser Node, Gegenstand oder dieses Objekt ist nicht definiert.\nDas ist immer ein Fehler.\nDies kann aus folgenden Gründen passieren:\n• Die Mod, die dafür benötigt wird, ist nicht aktiv\n• Der Spiel-Autor oder ein Mod-Autor machte einen Fehler
|
||||
It appears to originate from the mod “%s”, which is enabled. = Es scheint von der Mod »%s« zu stammen. Sie ist aktiv.
|
||||
It appears to originate from the mod “%s”, which is not enabled! = Es scheint von der Mod »%s« zu stammen. Sie ist nicht aktiv!
|
||||
Its identifier is “%s”. = Der Identifkator ist »%s«.
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
Error: This node, item or object is undefined. This is always an error.\\nThis can happen for the following reasons:\\n• The mod which is required for it is not enabled\\n• The author of the subgame or a mod has made a mistake =
|
||||
Error: This node, item or object is undefined. This is always an error.\\nThis can happen for the following reasons:\\n• The mod which is required for it is not enabled\\n• The author of the game or a mod has made a mistake =
|
||||
It appears to originate from the mod “%s”, which is enabled. =
|
||||
It appears to originate from the mod “%s”, which is not enabled! =
|
||||
Its identifier is “%s”. =
|
||||
|
|
Binary file not shown.
Before Width: | Height: | Size: 284 B After Width: | Height: | Size: 429 B |
Binary file not shown.
Before Width: | Height: | Size: 287 B After Width: | Height: | Size: 414 B |
|
@ -179,7 +179,7 @@ explicitly).
|
|||
|
||||
### Hand and air
|
||||
The mod adds some default help texts for the hand and the air which are
|
||||
written in a way that they probably are true for most subgames out of the
|
||||
written in a way that they probably are true for most games out of the
|
||||
box, but especially the hand help text is kept intentionally vague.
|
||||
If you want to change these help texts or the entry names or other
|
||||
attributes, just add `_doc_items_*` fields to the item definition, either
|
||||
|
@ -271,7 +271,7 @@ entry then.
|
|||
|
||||
#### Background
|
||||
Normally, the core factoids are written in a very general-purpose style, so this function might
|
||||
not be needed at all. But it might be useful for subgames and mods which radically break with
|
||||
not be needed at all. But it might be useful for games and mods which radically break with
|
||||
some of the underlying core assumptions in Minetest. For example, if your mod completely changes
|
||||
the digging system, the help texts provided by `doc_items` are probably incorrect, so you can
|
||||
disable `node_mining` and register a custom factoid as a replacement.
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
# Item Help [`doc_items`] (Version 1.1.1)
|
||||
# Item Help [`doc_items`] (Version 1.1.2)
|
||||
## Description
|
||||
Automatically generated help texts of blocks, tools, weapons, crafting
|
||||
items and other items.
|
||||
|
|
Loading…
Reference in New Issue
Block a user