wow, this is turning into a really good turorial jik!
Just read through it, didn't actually try to implement it atm so I can't comment on any troubles that might arrise but I'll just post any comments I have regarding the text.
[list type=decimal]
[*]page 4 - "I have found that using NOTEPAD++ of great help." either add 'is' or remove 'that', latter being the better option
[*]page 4 - "A python lists starts with a '[" I would say "A python lists starts with a (square) backet, a '['" same again in the next sentence, just to help ppl get used to the lingo. A few sentences down the word 'parentheses' is used so this makes sence.
[*]page 5 - "Now let us give "new_icon" a bit of a different look. Let’s change it to “city”. This mesh is currently not used and it will stand out better in our mod." this sentence is in there twice in a slightly different shape, check the previous paragraph.
[*]page 7 - bit about commenting. For those very new to programming, maybe explain that placing a hash before a sentence means that the compiler/game/whatever-you-want-to-call-it regards it as if it's not there, so you can use that to write notes.
[*]page 7 - paragraph starting with "If everything.." - "Using a code
editor line" 'line' should be 'like'
[*]page 7 -next paragraph - "In-game, travelling to the town now will trigger a combat the town menu." nice try
remove the 'a combat'
[*]page 9 - top - you list the knows_common list twice, maybe a bit redundants? Reformatting the paragraph seems like the better option.
[*]page 9 - section 3.2 - "The list of which troops can be upgraded into what is contained at the bottom of module_troops. Please scroll down to the bottom now." Not a really nice sentence imo. "The list for upgrading troops is contained at the bottom of module_troops. This defines which troops can be upgraded, including what they can upgrade into, when the experience conditions are met." or something similar
[*]page 9 - upgrade2(troops - "2 is currently" should be "Two is currently"
[*]page 9 - upgrade thingie. I noticed a slight inconistancy here. At the start of the page you say that in-game any novice_fighter can upgrade into a regular_fighter upon reaching level 11 and then later you add an extra entry to the file so this can actually happen. Since there currently isn't a troop upgrade in the game yet, the first bit is wrong. Rewrite to something like "We want to make it so that any novice_fighters in our party, etc etc." Makes more sense to me.
[*]page 10 - section 3.4 - I know you have commented on this being outdated but the bit about adding the troops to your party will still work as stated. However it says "notice how you are able to upgrade the new troops to "regular fighters"" But since you added the troop tree for 'novice_fighter' instead of 'new_troop', that won't work.
[*]page 10 - Marnid - "We used to be able to find him at entry point 4 in the Happy Boar inn" This is just my opinion but I think this is a bit redundant. A lot of new players who've never played old versions of MNB have no idea what the Happy Boar or Zendar even is.
[*]page 10 - Geoffrey - "If he were to be a joining character like Marnid, it would be best to add him to the list of NPCs right after npc16" I would change this to "If we were creating him to be a heroe that can join your party, like Marnid, it would be best [...]. However, we'll be using him as an 'actor' in the quest we are going to be creating so he's fine where he is." This is also consistant with the use of the word actor for Hareck later on in the page.
[*]page 11 - top- "In previous versions of M&B you could find Marnid in the tavern in Zendar" again, wtf is Zendar?
I would just say that in older MNB versions, heroes all spawned in set location whereas now this is random due to the flag being set to 0. If you want to keep this, at least remove the other reference, or vice versa.
[*]page 11 - Hareck - "His tuple is such:" this wants to be "His tuple looks like this:" or "His tuple is as follows:"
[*]page 12 - chests - "which we will cover in the files' respective documentation." Just a reminder, don't know if you're actually planning to do this, otherwise delete or reformat.
[*]page 13 - Part 5 - "In Parts 3 and 4, we have learned" at the beginning of part 4 "learned" is used, so choose either or. I'd go with 'learned'
[*]page 14 - item tuple - "Example of an item:" This seems to be a placeholder, replace with "Tuple of item practice_sword:"
[*]page 15 - underneath error msg - "This is a lesson that the order that the files are compiled may not be in the order that you worked on them." should read "This shows us that the order in which the files are compiled may not be the order in which you work on them."
[*]page 15 - section 5.4 - "we have organised the list by item types" you use 'I' before, so use it here as well.
[*]page 19 - deserters tuple - "Innocents tuple examination:". You're examining deserters, not innocents. One might argue the difference in a social context but for here I think we can safely assume it's an oversight
[*]page 19/20 - section 6.3a. This is obviously a new section and you haven't had time to change all the section nrs to match. I think this could use a bit more explanation. As you're well aware it's not an easy concept to understand, but nonetheless important and can make life a lot easier.
[*]page 20 - section 6.4 - "to which the before mentioned slots can be used." I would say "for which" or "of which"
[*]page 21 - second paragraph - "get the quest, we need the “actors”" replace comma with 'and' or -even better- replace the period at the end of the sentence to a comma and make it 'and', leaving off the of lastly since there is no firstly or secondly.
[*]page 21 - next sentence - "The old tutorial had you first start with the dialog" not really relevant. I'd reformat this paragraph and after the last sentence say. "We've already created the actors in the previous sections, so we'll now move on to creating the scene where you receive the quest and face the 'target' of the quest, and after that we'll edit the module_dialogs.py where it the troops, the templates and the quest will all come together.
[*]page 21 - next sentence - the 'notice the use of a slash' is pretty random here. Move it up to before the paragraph above so it fits in with the discussion of the tuple. Also, I had to look up what a carrage return is and I've done some programming before, so maybe you should elaborate on that one in layman's terms.
[*]page 21 - part 7 - I would rewrite the intro here somewhat to give it a more logical flow. "In this part of the tutorial we will be setting up the scene for our quest, which will involve going into the game and using the in-game edit mode. Like I said earlier, we'll also use this mode to give a new face to Constable Hareck. However, before we can do all that we have to finish building Mod Town. So far we've created it and placed it on the map, but there are a few more steps to take before we have a fully functioning town with scenes which we can edit inside the game.
[*]page 21 - tutorial thingie - "Open module_parties.py and scroll down" scrolling is sooo 2008
, use search function maybe?
[*]page 21 - paragraph below the code - lose all the 'haves'. 'I have copied' is 'I copied', etc. Replace the lastly with 'Then'. For the 1, 2, and 3, remove the 'may' in 2 and 3. Better yet, say "may not build or load, or may crash [...]"
[*]page 22 - "You will also notice that some of the specific definitions for the towns." Either this needs more text or the 'that' needs to be removed.
[*]page 22 - "We used the tavern from Uxkhal since a lot of it is complete and we can just add minor
items to make the scene look somewhat complete." Don't really like the sentence. "We're using the tavern from Uxkhal (town_7) which is already mostly complete so we'll only have to add a few things to it." Or something.
[*]page 22 - configuration thingie - "It also might be agood idea to have the screen resolution..." Missing a space and also, replace with "It's a good idea to change the screen resolution to a setting lower than that which you use for your computer." Tell it like you mean it.. none of this 'it might perhaps possibly' stuff!
[*]page 22 - face generator - first, replace 'face maker' with 'face generator' and then "Incase you lose it" needs a space.
[*]page 22 - in the tavern - "And you will notice that everyone that should be in the tavern are all on the same spot." that sentence doesn't really work. Either "You will also notice that everyone who should be in the tavern is occupying the same spot." or "...that all the visitors in the tavern have been placed in the same spot." or something in between. Couple sentences on: "While edit more is on," needs to be 'mode', of course.
[*]page 22 - entry points "They should be numbered starting at 16 and ending at 24". You've just told us to place entry points 0 and 9 so this doesn't make much sense unless you elaborate on that.
[*]page 23 - passage way - "Well, not really, but other scenes you create may need to jump to other scenes.". I'd say "Although you don't really need it for the purposes of this tutorial, it will make your scene more real to have a working door and you might also want to use it in other quests."
[*]page 23 - adding lights - you've used 'we' thoughout this part and now you switch to I and say 'I'll place'. Either change to we or just leave it out altogether 'place a red light..' etc.
[*]page 23 - tavernkeeper - "Well, since we need to also place our“actors”, we’ll make a tavern keeper as well." make it "Since tavernkeepers are unique NPCs, like merchants or heroes, we'll have to create him in the same way we created our other 'actors'."
[*]page 24 - top - "This will lead us to the next phase: Giving them dialog" make "This is because we haven't created any dialog for them yet, which is what we'll be doing in the next part."
[*]page 24 - part 8 - "When the criteria for a tuple is met, then the it will be executed." remove 'the'
[*]page 24 - negation flag - "That way, if you want" replace with "That's why, if you want". Also next sentence 'define' needs a 'd'
[*]page 26 - paragraph that starts with 'First note...' you say that it will say sir/wench based on gender but the code just has 'peasant' in it atm
[*]page 31 - section 1b 'store_faction_parameter' - 'store_' is not in bold
[*]page 31 - paragraph stat starts with 'Next we...' it says 'there uses' instead of 'their uses'
[*]page 32 - top of the page - "(including other else_try’s)" the apostrophe is wrong here, maybe reformat to (including other else_try blocks)
[*]page 32 - orange block of text - "both markers define" should be "defined" or preferably "are defined"
[*]page 32 - paragraph starting with 'Coming to...' - "With a complex and long list of “try”s" again I would replace with 'try blocks'
[*]page 32 - last paragraph -"I would interpret it as if this condition is true, or the next condition is true" for easier reading, maybe reformat to "I would interpret it as: "if this condition is true, or the next condition is true"" or place the last bit in bold
[*]page 33 - paragraph starting with 'The highlighted...' - "just add another try that test" missing an 's' on test
[*]page 34 - top - "midtown_begin to midtown_end." should be "modtown_" (yes I realize this is in the 'skip' bit, but you'll have to change it eventually anyway
)
[*]page 34 - paragraph starting with 'If you..' - "Therefore, (eq,"$geoffrey_duel",1)". You're not using a global var anymore but a slot
[*]page 35 - "This operation also outputs the identifier of the spawned party to reg(0) as defined in header_operations.py." Maybe this can be stated a bit more clearly. I know what you mean, but I think maybe "Because of the way the operation is defined in header_operations.py, the identifier of the spawned party is automatically assigned to reg(0) when the party is spawned"
[*]page 35 - "Let’s add 2 more lines. When done it your Geoffrey duel tuple should look like this:" remove 'it'
[*]page 35 - "Now come 8pm when the party “new_template” spawns" - fairly sure you did a check for 7pm and there's no delay...
[/list]
Well it turned into quite a list.. I guess I should've done this differently in retrospect, haha. Anyway, don't be alarmed by that, it doesn't mean you didn't do a good job. I've nitpicked most little grammar errors and typos and added some of my own opinions on stuff.
The tutorial is really shaping up well. I learned a good number of things just now reading through it and will certainly refer to it regularly when I forget how stuff was supposed to be done again.
Really, good work mate! Hope this helps you out towards the new version. I'm sure I've missed some bits this time but hopefully I'll pick them up on the next one.