You should: Sign up > Write articles > tell people about your articles > Monetize them > Earn money  > learn/do/earn more

2020 China floods

From Wikiafripedia, the free afripedia (encyclopedia)
Jump to navigation Jump to search

2020 China Floods
DateEarly June 2020[1] – present
LocationHunan, Jiangxi, Guangxi, Guizhou, Sichuan, Hubei, Chongqing, Anhui, Zhejiang, Fujian, and Yunnan [2][3][4][1]
Deaths>141 dead or missing (as of 13 July 2020)[5][3]
Property damage$3.6 billion USD (as of 2 July 2020)[6]

Floods have severely impacted large tracts of southern China since June due to heavy rains caused by the regional rainy season, primarily around the Yangtze basin and its tributaries, with rains expected to hit central and eastern China during July,[1] described as the worst since at least 1998.[7]

According to the Ministry of Emergency Management, by the end of June flooding had displaced 744,000 people across 26 provinces with 81 people missing or dead.[2] In early July, the South China Morning Post reported that about 20 million residents had been affected and at least 121 people were dead or missing.[8] As of 13 July, floods have affected 37.89 million people in 27 provinces, autonomous regions and municipalities, 141 people are dead or missing, and 28,000 houses have collapsed.[5] The Ministry of Water Resources said that a total of 443 rivers nationwide have been flooded, with 33 of them swelling to the highest levels ever recorded.[9] According to statistics from the National Cultural Heritage Administration (NCHA), 76 key national cultural relics and 187 provincial cultural heritage sites have suffered damage of varying degrees.[10]

Affected regions included Guangxi, Guizhou, Sichuan, Hubei, as well as Chongqing.[2][4][11] The regions include the upper and middle river basin of the Yangtze and its tributaries. With more rain floods started to extend to lower regions of the Yangtze basin such as Anhui, Jiangxi, and Zhejiang.[1] In addition, Hunan, Fujian, and Yunnan were affected.

Causes of floods[edit source | edit]

Natural causes[edit source | edit]

El Niño has resulted in the abnormal weather in many parts of China. Hu Xiao from the China Meteorological Administration (CMA) indicated that the rains were caused by increased vapors arising from the Indian and Pacific oceans.[6]

Artificial causes[edit source | edit]

In 1915, Dongting Lake was 5,000-square-kilometre (1,900 sq mi).[12] In 2000, it was only 2,625-square-kilometre (1,014 sq mi).[12] In the 1950s, Poyang Lake was 4,350-square-kilometre (1,680 sq mi).[12] In 2000, it was only 3,750-square-kilometre (1,450 sq mi).[12] Hubei was once known as "The Province of Thousands of Lakes" (千湖之省).[12] In the late 1950s, there were 1,066 lakes in Hubei.[12] By the early 1980s, only 309 were left.[12][13] With the rapid increase of population in China, in order to increase grain production and housing area, a large number of lake beaches had been transformed into farmland and homestead.[12] The serious shrinkage and disappearance of lakes in the middle and lower reaches of the Yangtze River is an important reason for the aggravation of flood disasters.[13][14][15]

Three Gorges Dam[edit source | edit]

Multiple dams in the Yangtze river basin control floodwaters; the biggest and most important of these is the Three Gorges Dam with its catchment area of about 1,000,000-square-kilometre (390,000 sq mi). It was constructed not only for power generation but also for flood control. By the end of June, the dam had started to release floodwaters.[16] While the CMA indicated flood discharge started on 29 June, satellite images suggest that floodgates were opened already five days earlier.[17] Yichang, a city below the dam, experienced extensive flooding, raising questions about the effectiveness of the flood control by the dam.[18] There were fears that Wuhan could be flooded.[4] According to the company that manages the dam, the dam had been "effectively reducing the speed and extent of water level rises on the middle and lower reaches of the Yangtze".[19] Critics, however, suggest that the dam is "not doing what it is designed for" and unable to deal with severe events.[19]

There is extensive media coverage questioning the safety of Three Gorges Dam, especially from the media of Pan-Green Coalition in Taiwan.[20] Reports foreseeing a collapse of the dam emerged almost every summer in Taiwan Media. [21] Rebuking these reports, Global Times said that the Three Gorges Dam was safe for heavy rain and "not at risk of collapse", [22] some overseas media hyped the "distortion" of the Three Gorges Dam. [23]

Flooding by province[edit source | edit]

Anhui[edit source | edit]

Zhenhai Bridge in April 2013
After flooding

On 27 June, a 3-hour heavy rainfall of 118-millimetre (4.6 in) was recorded in Hefei Economic and Technological Development Zone, of which 94-millimetre (3.7 in) was recorded during 1.5 h from 17:30 p.m. to 19:00 p.m., which was rare for many years.[24] Some road sections and communities were submerged.[24]

On 6 July, Lecheng Bridge [zh], a Qing dynasty stone arch bridge and provincial cultural relics protection unit in Sanxi Town of Jingde County, was damaged.[25] On 7 July, some houses along the Shuiyang River in Xuanzhou District of Xuancheng were submerged.[26]

On 7 July, several reservoirs in She County filled over capacity and reached record levels, requiring large releases of water to alleviate the dangerously high storage of water.[27] Homes in She County were inundated. The first day of the National College Entrance Examination (Gaokao) was postponed due to hard rain.[28] On 7 July 2020, Zhenhai Bridge, a large stone arch bridge in Tunxi District of Huangshan City and a "Major Historical and Cultural Site Protected at the National Level in Anhui", was destroyed by mountain torrents.[10][29][30]

On 9 July, Yaodu River (尧渡河) and Longquan River (龙泉河) in Dongzhi County exceeded the highest water level in history.[31]

All residents in Laozhou Township [zh] and Xuba Township [zh] of Tongling along the Yangtze River were ordered to evacuate on July 11.[32][33]

On 14 July, an emergency was issued by the Office of Anhui Provincial Flood Control and Drought Relief, which ordered all residents living in the central island of the Yangtze River or along the Yangtze River in Anqing, Chizhou, Tongling, Wuhu and Maanshan to evacuate.[34]

On 18 July, the Huai River Commission of the Ministry of Water Resources raised the flood-control response from Level III to Level II.[10][35]

On 19 July, the Government of Quanjiao County blasted several gaps in Chu River Levee to release floods.[36]

At 8:32 a.m. on 20 July, the Government of Nan County opened sluice gates at Wangjia Dam (王家坝) on the Huai River because water there was building up to too high a level.[37] The last flood discharge was 13 years ago.[10][37]

At 10:24 a.m. on July 21, the water level at Zhongmiao Station (中庙站) of Chaohu reached 13.36-metre (43.8 ft), which is the once-in-a-century water level of Chaohu.[38]

Chongqing[edit source | edit]

At 20:00 p.m. on 22 June, the "Qijiang Wucha Hydrological Station" (綦江五岔水文站) in Jiasi Town [zh] recorded a water level of 205.85 metres (675.4 ft), which was 5.34 metres (17.5 ft) higher than the guaranteed water level (200.51 metres (657.8 ft)). The Qijiang Wucha Hydrological Station reached 205.85 metres (675.4 ft), topping the previous record of 205.55 metres (674.4 ft) in 1998 China floods.[39] On 22 June, parts of Qijiang District's Wenlong Subdistrict [zh] were submerged, with some roads underwater.[40] 13,874 residents in Qijiang District along the Qi River were ordered to evacuate on 22 June.[40]

On 15 July, hundreds of homes in Miaoba Town [zh] of Chengkou County were evacuated due to catastrophic rain and floods.[41]

At 15:00 p.m. on 17 July, floods burst a bridge in Baojia Town [zh] of Pengshui Miao and Tujia Autonomous County, a man fell into the river and disappeared.[42]

Fujian[edit source | edit]

On 9th July, a rainstorm occurred in Nanping, causing floods, landslides and other disasters, many roads were destroyed and crops were flooded.[43] Wuyishan City had serious waterlogging, and the local government issued a rainstorm red warning signal, and Wuyishan Scenic Spot had been closed.[44]

From 11 to 14 June, a torrential rainfall hit Youyang Tujia and Miao Autonomous County and Shizhu Tujia Autonomous County. On June 14, Huaxia Minzu School (华夏民族小学) was inundated.[45] On 22 June, homes in Youyang Tujia and Miao Autonomous County were also inundated.[46]

Guangdong[edit source | edit]

On 22 May, the largest one hour rainfall in 2020 in China is Huangpu Bridge of Guangzhou, 168-millimetre (6.6 in).[47] Line 13 of Guangzhou Metro was shut down due to the water flowed back into the tunnel.[48]

At 11:00 a.m. on 8 June, roads and farmland in Lianxin Village of Linjiang Town [zh] in Heyuan were engulfed by floods.[49] The Yonghan Levee (永汉堤) on the Dong River collapsed, releasing an 3-metre (9.8 ft) to 5-metre (16 ft) wall of water.[50] Flood surrounded Hekou Village of Yonghan Town [zh] in Longmen County, making it an island.[50] Roads and highways were severely damaged or destroyed in Longmen County.[51]

Guizhou[edit source | edit]

From 07:00 a.m. on 11 June to 07:00 a.m. on 12 June, a torrential rain of 264.6 millimetres (10.42 in) fell in Bifeng Town [zh] of Zhen'an County, with the maximum hourly rainfall of 163.3 millimetres (6.43 in), breaking the historical record of Guizhou in one hour.[52] It is also China's largest one hour rainfall, after Guangzhou of 168 millimetres (6.6 in) on May 22.[52] Throughout the county, 8 people were killed and 5 were missing.[52]

At 7:00 a.m. on 14 June, a total of 438,000 people in 51 counties of 8 cities in Guizhou were affected, 10 people died, 14 people were missing, 21,000 people were forced to evacuate; nearly 100 houses collapsed and more than 8,000 houses were badly damaged; 175,000 hectares (1,750 km2) of crops were affected, including 28,000 hectares (280 km2) will have no harvest; and the direct economic loss was 880 million yuan.[52]

From 23 to 24 June, the torrential rainfall hit Rongjiang County, resulting in a direct economic loss of 92.1025 million yuan due to rural roads in the county sustained major damage.[53]

At 7:05 a.m. on 8th July, at least six people were killed when a landslide occurred in Shiban village (石板村) of Songtao Miao Autonomous County.[54]

On 12th July, portions of National Highway G212 in Meijiuhe Town [zh] of Renhuai was closed due to mountain flood.[55] Loushanguan Scenic Spot (娄山关景区) was also closed.[55]

Hubei[edit source | edit]

As of 13 July in Hubei province, at least 14 people were dead, and five others were missing.[5] Over nine million people were affected.[5]

At 7:00 p.m. on 5th July, the water level of Baiyanghe Reservoir rose to 84.62-metre (277.6 ft).[56] At 12:00 p.m. on 6th July, the dam slipped and deformed, and 29,000 people were evacuated.[56]

At 4 a.m. on 8th July, a landslide caused by heavy rainfall in Yuanshan village of Dahe Town [zh] in Huangmei County, killing 8 people.[57]

At 13:00 p.m. on 11 July, the water level of Chang Lake at Jingzhou reached 33.49-metre (109.9 ft), topping the previous record of 33.46-metre (109.8 ft) in 2016.[58]

On 17 July, in Enshi City, the streets and cars were covered in water.[59] All roads were closed in and out of the city.[59]

Hunan[edit source | edit]

On 8th July, Madian Reservoir (马店水库) of Yueyang County received 303-millimetre (11.9 in) of rainfall in total, representing the highest accumulated rainfall since 1952.[60]

On 8th July, in northwestern Hunan's Zhangjiajie, a man netting fish was swept away by the flood.[61]

Hunan Hydrological and Water Resources Survey Center issued an orange flood warning at 12:20 p.m. on 11 July.[62] At 2:00 p.m. on 11 July, Orange Isle was closed.[63]

Jiangxi[edit source | edit]

Jiangxi experienced major floods in July 2020, primarily along the Poyang Lake and its tributaries in Jiujiang, Shangrao, and Pingxiang.

At 0:00 a.m. on 12 July, the water level at Xingzi station of Poyang Lake reached 22.53 metres (73.9 ft), exceeding the record of 22.52 metres (73.9 ft) in 1998 China floods.[64]

Residents were forced to evacuate Jiangzhou Town [zh] and Sanjiao Township [zh] of Jiujiang on 12 July as the flooded river began to overtake homes.[65][66]

On 11 July, Rao River rose to an all-time high of 22.65-metre (74.3 ft), crossing the danger mark and surpassing the previous record of 22.43-metre (73.6 ft) set in 1998.[67][68] Parks, homes, and businesses in Poyang County were overtaken by the Rao River, leaving parts of the county accessible only by boat.[69] The 73123 Army of the Eastern Theater Command Ground Force [zh] rushed to Poyang County to fight flood.[70]

On the afternoon of 8 July, Qinghua Rainbow Bridge was devastated by flood.[71] In the early morning of 9 July, the highest water level of Sandu Hydrological Station in Wuyuan County reached 62.74-metre (205.8 ft), exceeding the warning water level by 4.74-metre (15.6 ft).[71]

Sichuan[edit source | edit]

On 17 June, heavy rain triggered mudslides and flooding that leaves 2 people missing in Danba County. [72]

From 18 pm 26 June to 1 am on 27 June, a sudden rainstorm occurred in northern Mianning County.[73] National Highway 248 collapsed in the county seat Gaoyang Subdistrict [zh], causing two passing vehicles to fall into river. Only five of the ten passengers were rescued, two died and three were missing.[74] As of 23:00 on 30 June, 14 people were killed and 8 people were missing in Gaoyang Subdistrict and Yihai Town [zh]. As of 1st July, 500 hectares (5.0 km2) of crops were affected, 280 hectares (2.8 km2) were damaged and 70 hectares (0.70 km2) will have no harvest, more than 280 houses collapsed or badly damaged and 2,300 houses partially damaged.[73][74]

On 6th July, 4 people were missing from the debris flow caused by floods in Zhailong Town [zh] of Xiaojin County.[75]

On 16 July, in Tongchuan District of Dazhou, 7 people went swimming in the river and 2 people were washed away by floods.[76]

Yunnan[edit source | edit]

From the evening of 29 to 30 June, a heavy rainstorm occurred in Zhenxiong County, Yiliang County, Weixin County and Yanjin County. The level of Baishui River [zh], a tributary of the Yangtze River, had risen 8 metres (26 ft), causing serious floods in towns and townships along the river.[77] As of 21:00 on 30 June, 3,871.54 hectares (38.7154 km2) of crops such as corn, potatoes and tobacco were affected, 3,745.09 hectares (37.4509 km2) were damaged and 84.68 hectares (0.8468 km2) will have no harvest, and more than 90 houses collapsed, 59 houses badly damaged and 90 houses partially damaged.[78]

Zhejiang[edit source | edit]

Flood Discharging at Xin'an River Dam

On 29 May, Chunan County suffered the strongest plum rain in history. On 8th July, the level of Qiandao Lake reached its highest level in history.[79] At 9:00 a.m. on 8 July, Xin'an River Hydropower Station began to discharge flood.[80] This is the first time since the completion of the hydropower station that all 9 gates have been fully opened for flood discharge.[80]

Government actions[edit source | edit]

The Chinese government allocated about 309 million yuan (44.2 million U.S. dollars) for disaster relief in flood-hit regions.[5] On 10 July and 12 July, State Council premier Li Keqiang and Party general secretary Xi Jinping called for all-out efforts in rescue and relief operations in flooded areas across China and stressed that ensuring people's lives and safety is a top priority successively.[81][5][82]

On the evening of 12 July, more than 7,000 officers and soldiers of the 71st Group Army and the 72nd Group Army went to Jiujiang and Tongling to participate in flood fighting and emergency rescue tasks.[83][84][85] On the morning of 14 July, more than 3,700 officers and soldiers from the 73rd Group Army rushed to Yugan County to fight against floods and deal with emergencies.[83][84][85] On 14 July, according to the order of the Central Military Commission, more than 16,000 officers and soldiers were sent to Jiujiang, Shangrao and other areas of Jiangxi to fight floods.[83][84][85] At 23:00 on 19 July, the officials of the Central Theater Command arrived in Wuhan, capital of central China's Hubei province, to command flood fighting and disaster relief.[86]

See also[edit source | edit]

References[edit source | edit]

  1. 1.0 1.1 1.2 1.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  2. 2.0 2.1 2.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  3. 3.0 3.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  4. 4.0 4.1 4.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  5. 5.0 5.1 5.2 5.3 5.4 5.5 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  6. 6.0 6.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  7. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  8. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  9. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  10. 10.0 10.1 10.2 10.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  11. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  12. 12.0 12.1 12.2 12.3 12.4 12.5 12.6 12.7 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  13. 13.0 13.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  14. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  15. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  16. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  17. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  18. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  19. 19.0 19.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  20. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  21. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  22. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  23. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  24. 24.0 24.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  25. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  26. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  27. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  28. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  29. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  30. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  31. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  32. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  33. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  34. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  35. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  36. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  37. 37.0 37.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  38. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  39. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  40. 40.0 40.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  41. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  42. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  43. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  44. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  45. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  46. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  47. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  48. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  49. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  50. 50.0 50.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  51. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  52. 52.0 52.1 52.2 52.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  53. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  54. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  55. 55.0 55.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  56. 56.0 56.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  57. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  58. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  59. 59.0 59.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  60. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  61. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  62. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  63. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  64. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  65. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  66. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  67. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  68. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  69. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  70. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  71. 71.0 71.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  72. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  73. 73.0 73.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  74. 74.0 74.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  75. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  76. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  77. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  78. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  79. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  80. 80.0 80.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  81. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  82. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  83. 83.0 83.1 83.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  84. 84.0 84.1 84.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  85. 85.0 85.1 85.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  86. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).

External links[edit source | edit]