Thats good what you did read manual now. Realizing the concept of being able to in fact figure a stuff out by reading the entire 130-page patch manual is a real major time-saving breakthrough. For that i'll present you with a real magic as a reward - The Search Function. Its usually called by the cheat code ctrl+f on many applications, but it could not always be a case, so better refer to manual of the program you're using to read. That magic function solve literally all of your worries expressed here, as you literally can search for a stuff you need at the certain moment even if it spanned over literally thousands
of pages in a really short time. Its a real life quality improve, that thing.
Note, that when somebody is claiming he did read the stuff he's asked to read, even if its whooping 130 (!!!) pages (and its with pictures included in count, omg), others have to see this claim as, well, what he did read it. No matter the pages span between mentions is. Thats why i asked him to RTFM, and not went into pointing of various pages that could be of interest of him (as with so horrible vaguely described problem as he did it will just be a silly guessing game). Cos all the possibilities would be covered this way at once instead.
On the other hand, its generally good to read manual even if to prevent wasting of every else's time by asking to write answers on a subjects already covered there (and if one wouldnt read it - how would he know if they're do covered there or not). It will really help user on a matters what he should have reasons to suspect
and whats have something to do
with something and whats not. Also it would save a possible need to write misleading information irresponsibly safeguarded with disclaimers like "I believe"
or "As far as I know"
, as you would be able to provide an outright correct answer instead if needed. Thats not even mentioning the manual in question contains quite enough useful reading on a game stuff to improve a newbie's knowledge about game he supposedly into, beside more "technical" information.
A user wanting to use a simple (and great) feature should be able to write an actual problem he encountered, and not turn it into silly guessing game (where townltu and you volunteered to participate). Very ideally he better shouldnt try to pull a non-existent "quotes" out of something and claim them being from the manual he supposedly did read. Also it helps to not try to "bite" ones who helping him with stuff in their own time. It would greatly improve his chances on a success, thats it.
And ofc all the above isnt anything close to a developer-level understanding of the program
, nobody expect or demand it. Its only about most basic thing, say ability to read
, or ability to do some simply things
that you are asked to do if its needed to solve your own problem.