From inside the client you can run: - docwritebaseref and - docwritetodoref By passing "1" it'll write all idents, but that includes stuff like "_CAS_serverpass" and "__DEFAULT_SCOREBOARD", so only look into that list if you feel something was missed without it. - docwritetodoref 1 There's no real automation for incorporating these snippets, you will need to find the proper section to place them in and collect all the required properties. You may encounter html-like-entities, like "gt;" (not ">"!) in the autogenerated lists – the reference.xml would have "gt;=" as '''''' in plain. The established documentation does not adhere to any specific order of the properties; we would suggest to stick to one though and possibly fix the order if you see something not matching it. Here's a set of fictional fully expanded examples: Keep the value of that setting. A value between negative and positive infinity. -1001, -3.1415, -1, 2, 6.28, 2002, … Performs some work. This takes the potential and releases it's energy. 2nd law of thermodynamics applies. Output: 41 Example: echo the energy of 1kg of sugar is (workworkwork 123456 "sugar rush") For comparing established documentation and autogenerated I used this (on *nix): while read begriff; do zahl=$(grep -c "name=\"${begriff}\"" docs/reference.xml); if [ $zahl -eq 0 ]; then echo $begriff; fi; done < <(grep name= docs/autogenerated_base_reference.xml|sed 's/^.*name="\([^"]*\)".*$/\1/')