22) was a consequence of a discussion that arised of the fact that paratroopers in 3.19 ( and in 3.17 too ) can't take cities with just workers, planes, missiles, ships, missionaries, corp execs or GP that the paratrooper can see, after a drop ( that is, the paratrooper can only take a city that has not any unit, land military or not, that it can see ... so a sub can stop the city taking or not depending of being detected or not). Given this abnormal behaviour, there were only two solutions to make the behaviour consistent : make the cities takeable after drop if they don't have any land military or forbit the city taking after drop. Comparing with other similar situations in game ( like when a knight tries to take a city with only a worker there after having attacked ( the drop is considered a attack action in code ) ), jdog decided to simply forbid the city taking, believing that it was both more consistent with the rest of the game and more in agreement with the spirit of the original programmer.
Not that I fully agree with him![]()
I wholeheartedly disagree with this interpretation of spirit. Why does it take until BTS 3.19 for the programmer's spirit of a paratrooper's abilities to be redefined in a way that mitigates their usefulness in an obvious and often used way? It'd be like editing Star Wars so that Solo shot second.