[M2TW] Favourite Tutor

**Ishan** · November 09, 2013, 02:03 PM

For the year 2012, there are 2 TW modders nominated as favourite tutor, in the medieval 2 section. Modders who help solving problems of newbies or other modders in the mod workshop or any other thread where a modding problem is bothering someone. Vote for the one you like the most:

Gigantus

Known for his creating a world series gigantus is an active participant of mod workshop and well known for helping novice modders. In 2012 he wrote tutorials on:

Killing characters multiple ways: A simple tutorial that explains how to use the "kill_character" command to get rid of game characters in multiple ways.
Creating a World - Named Forts: Tutorials to get named forts in game.
Creating a World - Unpacking the Game
Creating a World - Editable Settlement Faction Symbols:

makanyane

A well known modder from the RTW & M2TW games. She has been a helping hand in the mod workshop for several years and is an active participant in the mod workshops, helping out novice modders whenever she can. In 2012 she wrote a tutorial on:

Vegetation editing: A tutorial on editing vegetation.db through which new vegetation models can be added on the battle map.

Extensive support in the IWTE Battle Map World editing thread: Helped modders in solving out their conundrums related to buildings and 3D objects on M2TW battle map. For example:

Click to Expand:

Originally Posted by makanyane

WARNING ABOUT 'BLOCKED' BREACH SETTING FOR WALLS

It seemed like a good idea at the time... but having looked at a settlement problem someone sent me recently (thank you

) I've realised that not only does the setting stop the ai attacking that wall section with artillery (useful) it also stops the ai using ladders/towers on that wall section too (distinctly not useful).

As background normal 'wall' main objects have an indicator setting of '96' in one column of the object table in .world - there was one example of a blocked breach wall (it could be destroyed but didn't let you in to settlement) in stone_fort_c which had the indicator '32' in that column instead, which we thought just stopped ai artillery attack, so I talked wilddog into including it as an option in the latest IWTE releases... unfortunately although the human player can bring up ladders, the ai apparently doesn't.

have tried using '64' as the indicator instead which seemed like next most logical one, with that setting the ai does bring ladders, but unfortunately it makes the object invisible and they don't climb the ladder
(see demo pic on stone_fort_c)

However there does seem to be a possibly more convoluted way of getting things to work involving one invisible wall with the '64' setting which the ai will attack with ladders, and a visible wall as a separate one group object without breach that humans can see, and which has the deployment block part - the invisible one needs to be slightly bigger than the visible version to keep the ai side functioning... (shown working in 2nd pic)

will try and do a better explanation after a bit more checking that there isn't some other problem with this

oh and for future reference - I think ai will only bring ladders up to one 'wall' section per deployment block - if you set up a custom battle with ai attacking vanilla city with lots of ladders that behaviour is apparent - not sure if there's anything in the battle ai which effects that, but should be born in mind if you're planning long sections of perimeter as one deployment block.

Originally Posted by Red_Devil

Thanks makanyane for all this information.