All you need to do is explain it thoroughly.Īlso, with regards to what you and u/TehFluffer mentioned regarding Google searches and views, go ahead and use Google now. Unlike guides for combat, factions, or ones for beginners to explain mechanics, the boss fights for raids don't really require you to "experiment" too much since, by then, you already have something that works. ![]() ![]() Destiny 2) where I practically list down viable boss fight strategies, loadouts, and even make note of timers. The only exception I make would be when I do raid guides (ie. I let people read and explore/experiment on their own. There should always be a balance between providing enough information to nudge someone along, versus having to hold their hand too much. But, outside of anything that was "too confusing," I didn't feel that was necessary. A random Redditor wanted me to go more in-depth to explain each mechanic more than I already had. I remember something being mentioned when I did a guide for Total War: Three Kingdoms. Going beyond that would be "holding someone's hand" too much, and I find that counter-productive for certain types of guides. I find it best to do a general explanation of concepts followed by what I use from the early-game to mid-game experience which, in many cases, would still be viable during the endgame. For instance, I could just list down each statistic for a unit, but that's not really going to help out any newcomer (or veteran player) unless they like number-crunching a lot. I don't try to bombard a reader with too much information or too many numbers. ![]() I usually try to keep guides around or below 1,000 words.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |