This is a good article. Click here for more information.

Kyoto Animation arson attack

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found.

Kyoto Animation arson attack
260px
Kyoto Animation's Studio 1 after the arson attack
Lua error in Module:Infobox_mapframe at line 185: attempt to index field 'wikibase' (a nil value).
Lua error in Module:Infobox_mapframe at line 185: attempt to index field 'wikibase' (a nil value).
Lua error in Module:Infobox_mapframe at line 185: attempt to index field 'wikibase' (a nil value).
Lua error in Module:Infobox_mapframe at line 185: attempt to index field 'wikibase' (a nil value).
Native name 京都アニメーション放火殺人事件
Location 15-1 Inaba, Momoyama-chō, Fushimi, Kyoto, Kyoto Prefecture, Japan
Coordinates Lua error in package.lua at line 80: module 'strict' not found.
Date 18 July 2019 (2019-07-18)
10:31 a.m. JST (UTC+09:00)
Target Kyoto Animation Studio 1
Attack type
Arson, mass murder
Weapon Gasoline (40 L), lighter
Deaths 36
Injured 34 (including the perpetrator)
Perpetrator Shinji Aoba (青葉真司)[1]
Motive Revenge tied to imagined plagiarism; mental illness
Verdict Death
Convictions Murder (36 counts)

Attempted murder (33 counts)

Arson

The Kyoto Animation arson attack (Japanese: 京都アニメーション放火殺人事件 Hepburn: Kyōto Animēshon hōka satsujin jiken?, Kyoto Animation arson murder incident) occurred at Kyoto Animation's Studio 1 building in the Fushimi ward of Kyoto, Kyoto Prefecture, Japan, on the morning of 18 July 2019. The arson killed 36 people, injured an additional 34 (including the suspect), and destroyed most of the materials and computers in Studio 1. It is one of the deadliest massacres in Japan since the end of World War II, the deadliest building fire in Japan since the 2001 Myojo 56 building fire, and the first massacre ever to have occurred at a studio associated with an entertainment company, and the animation industry.

The suspect, who did not work for the studio, entered the front door carrying about 40 litres (8.8 imp gal; 11 US gal) of gasoline, then doused the area and several employees before igniting it. After setting himself on fire while lighting the fuel, the suspect attempted to flee, but was apprehended by police about 100 metres (330 ft) from the building. Witnesses stated they heard him accusing the studio of plagiarism. After awaiting his recovery from life-threatening burns for more than ten months, the police arrested 42-year-old Shinji Aoba on suspicion of murder and other offenses on 27 May 2020.[2] He was formally indicted on 16 December 2020. Aoba eventually pled guilty to the charges on 5 September 2023, and was sentenced to death on 25 January 2024.[3]

In addition to condolences and messages of support from national and international leaders, fans and businesses raised over ¥3.3 billion (US$FXConvert/Wordify error: cannot parse value "Expression error: Unrecognized punctuation character "[".") in Japan and over US$2.3 million internationally to help the studio and its employees recover. A special measure was passed by the National Diet to allow for donations to the studio to be tax-exempt.[4] As a result of the incident, some works and collaborations by the studio were delayed, and several events were suspended or cancelled.

Background

File:Kyoto Animation Studio 1a.jpg
Studio 1 prior to the arson attack, May 2015

Kyoto Animation is one of Japan's most acclaimed anime studios, known for titles such as The Melancholy of Haruhi Suzumiya, K-On! and Clannad.[5] It has several different locations in Kyoto: Studio 1 (in Fushimi ward); Studio 2 (the head office), and Studio 5. Their merchandise development division is in Uji, one train station away from Studio 1. The building was used mainly by the animation production staff, and was constructed in 2007.[6][7][8]

In the year leading up to the attack, Kyoto Animation had received over 200 death threats.[9] Company president Hideaki Hatta said they did not know if the threats were related to the incident, as they were sent anonymously,[10] but he had informed police and lawyers of them. After the National Police Agency was informed of these threats in October 2018, officers temporarily patrolled the head office at the time.[9]

Incident

The fire began with an explosion[11] at around 10:31 a.m.[12][13] (01:31 UTC) when the perpetrator walked into Studio 1 and set the building on fire with 40 litres (8.8 imp gal; 11 US gal) of gasoline.[5][14] The perpetrator bought the gasoline 10 km (6.2 mi) away from the building, and it was believed that he walked to the building with the gasoline being carried on a platform trolley.[15] The police believed that the gasoline dispersed on site mixed with the air, causing the explosion at the start.[16] The perpetrator is reported to have been shouting "Die!" (死ね!) as he carried out the attack. He also poured gasoline over some individuals before setting them alight—setting himself on fire in the process—causing them to run out into the street in flames.[5][17][18]

As the fire grew by the entrance, staff members were trapped inside the building. Twenty bodies were found on the stairs from the third floor to the roof, evidently indicating that the victims were attempting to escape.[19] Tomoaki Nishino, associate professor at Disaster Prevention Research Institute of Kyoto University, estimated that the second and third floors were almost filled with smoke within 30 seconds of the explosion.[20] The perpetrator fled the scene but was chased by two Kyoto Animation employees and soon collapsed on the street, where he was apprehended by police.[21][4] Multiple unused knives were found lying by the scene.[22]

The fire was under control at 3:19 p.m. (06:19 UTC), and extinguished at 6:20 a.m. on the next day (21:20 UTC).[12] Once the rescue efforts had ended, it was confirmed that all people in the studio had been accounted for.[23] The building did not have fire sprinklers or indoor fire hydrants due to its classification as a small office building,[24] but had no deficiencies in fire safety compliance during its last inspection on 17 October 2018.[12] Initial reports claimed the studio's entrance required employee pass-cards, but the door was left unlocked as the studio was expecting visitors.[25][26] However, this was inaccurate: there was no security system in place and the door was always left unlocked during business hours.[27][28]

The arson attack destroyed most of Kyoto Animation's materials and computers in Studio 1,[29][30] though a small portion of keyframes were on exhibition in Tokushima and hence spared destruction.[31] On 29 July, Kyoto Animation reported that it successfully recovered some digitized original drawings from a server that survived the fire.[32]

The attack is reported to be one of the deadliest massacres in Japan's history since the end of World War II[33] and the deadliest building fire in the country since the Myojo 56 building fire in 2001.[34][35] It was considered "suicidal terrorism" by one criminology professor at Rissho University, as the attack was reportedly intended to be a suicide mission by the suspect.[36]

Victims

Seventy people were inside Studio 1 at the time of the fire.[19] Initially it was reported that 34 people had been killed before two more later died at a hospital.[lower-alpha 1] Some victims were difficult to identify, according to the Kyoto police, because they had been burned beyond recognition.[44] Autopsy results released on 22 July 2019 revealed that a majority of victims had succumbed to burns (rather than carbon monoxide poisoning) due to the quick-spreading fire.[45][46] DNA testing was done to aid in identifications, which lasted up to a week after the attack.[47] It was reported that two-thirds of the victims (at least 20) were women, as the studio was known for hiring female animators.[48] The president of Kyoto Animation asked the media through the police not to release the names of the victims out of respect for their families, stating that "releasing their names does nothing to serve the public good."[49] On 25 July, Kyoto police said they had identified all 34 victims and had started to return the bodies of the victims to their relatives.

Meanwhile, discussions were ongoing with Kyoto Animation on if, when, and how to reveal the identities of the deceased.[50] Some of the families released their own findings early to the media regarding the status of their loved ones. The family of color designer Naomi Ishida confirmed her death on 24 July.[51] Animator, scriptwriter, and director Yasuhiro Takemoto was confirmed dead by his family through DNA testing on 26 July.[52][53] The first post-fire death occurred on 27 July which brought the number of deceased to 35.[42] On 2 August, Kyoto police released the names of ten victims (including the people already mentioned) whose funerals had finished and relatives' consents obtained, and it was confirmed on the same day that animation directors Yoshiji Kigami and Futoshi Nishiya were among the dead.[54][55] The remaining 25 victims were officially revealed on 27 August as the social impact of the case became a factor.[56][57] On 4 October 2019, it was announced that one woman died from septic shock, bringing the death toll to 36.[lower-alpha 2]

It was initially reported that 36 people were injured, but this figure dropped to 34 after two people later died at the hospital.[lower-alpha 2] By 18 September it was reported that all thirty-four (34) people injured in the attack were no longer in life-threatening condition. Some still remained in the intensive care unit (ICU) with severe burns.[lower-alpha 2] According to the South Korean Ministry of Foreign Affairs, one of the injured victims was a South Korean woman.[lower-alpha 2] Those who were reported safe include animation director Naoko Yamada, who directed K-On!, A Silent Voice and Liz and the Blue Bird.[lower-alpha 2]

Perpetrator

Shinji Aoba
Born (1978-05-16) May 16, 1978 (age 46)
Urawa, Saitama, Japan
Occupation Unemployed[64]
Criminal penalty Death
Criminal status Incarcerated
Conviction(s) Murder, attempted murder, arson, trespass, breach of the arms-control law[64]

Shinji Aoba (青葉 真司 Aoba Shinji?), was identified as the suspect by police.[65][66] He was born on May 16, 1978, in Urawa, Saitama, Japan.[67] He was 41 years old at the time of the attack.

According to locals, a man resembling Aoba was spotted near Studio 1 days before the incident.[68][69][70] He was also reported to have visited several places of interest related to Sound! Euphonium around the city in days prior to the attack.[70][15] Immediately following the attack, Aoba fled the scene after being chased by employees of the studio but was apprehended by the Kyoto Prefectural Police near Rokujizō Station of Keihan Electric Railway, about 100 metres (330 ft) from the studio;[71] Aoba was then taken to a hospital with severe burns to the legs, chest, and face.[25][23]

During his transport to the hospital, Aoba admitted to having started the fire,[72] possibly for revenge,[73] accusing the studio of "ripping off" or "plagiarising" (パクリやがって pakuri yagatte?) his novels.[lower-alpha 3] In spite of this, Hatta had initially stated that there is no record of anyone submitting work to their annual writing contest under Aoba's name.[78] Subsequently, Kyoto Animation revealed that they had received a draft novel from Aoba; however, it did not pass the first-stage assessment and was forgotten, and its contents were confirmed to have no similarities to any of their published works.[79][80] It was later revealed that Aoba believed that a scene about buying discounted meat in the fifth episode of Tsurune was similar to one in the novel he submitted.[81][64]

Scenes from Kyoto Animation works that Aoba claims were "plagiarized"[82]
Free! Tsurune K-On!
KyoAni works A school banner reading "Swimming club advances to regional tournament" is blown in the wind, and a banner for the judo club can be seen below. When a character puts meat in their shopping cart, another character finds meat at a 20% discount. A character says to a junior "I repeated a grade."
Aoba's novel There are scenes where banners appear. There is a scene where the heroine buys deli dishes at a 50% discount. There is a scene in which a high school boy is told by his homeroom teacher, "If you continue like this, you'll repeat the grade."

Due to serious burns sustained during the incident, Aoba was transferred to a university hospital in Osaka for further treatment, where he received necessary skin graft surgery.[66][83] On 5 September 2019, it was reported that his injuries were no longer considered life-threatening,[84] but he was still being treated in an ICU and required respiratory assistance from a ventilator.[85] Aoba regained speech on 18 September and began rehabilitation by 8 October, being able to sit up on a wheelchair and hold short conversations. The police obtained a warrant for his arrest, but were required to await confirmation from doctors that Aoba could withstand confinement.[86][87]

On 14 November 2019, he was moved to another hospital in Kyoto for final rehabilitation.[88] He recovered from most of his injuries and acknowledged responsibility for the attack. He expressed feelings of remorse and gratitude towards the hospital staff, who he said treated him better than anyone had ever done in his life.[89] On the other hand, he told police that he lit the fire because Kyoto Animation had stolen his novel, and that he expected to get the death penalty.[90] Most of Aoba's burned skin was replaced with experimental artificial skin as the victims were prioritized to receive donor human skin first.[91][92] The use of artificial skin on such extensive burns is the first case in Japan.[91][92]

By January 2020, Aoba remained hospitalized, and was unable to stand or eat unassisted.[93] On 27 May 2020, Aoba was judged to have sufficiently recovered from his burn injuries, and he was formally arrested on suspicion of murder and other charges.[94][95] He was indicted on 16 December 2020 on murder and other charges.[96][97]

Aoba had a prior criminal history and was known to suffer from mental illness. In 2012, he robbed a convenience store with a knife in Ibaraki Prefecture and was subsequently jailed for three-and-a-half years.[98][99] It was speculated after the attack that Aoba's mental illness would reduce his maximum penalty for the attack from a death sentence to life imprisonment.[100]

On 12 May 2023, the Kyoto District Court announced that Aoba would stand trial in September 2023 and that a verdict would be announced in January 2024.[101] Aoba pleaded guilty to the charges on 5 September,[1] and on 7 December 2023, the prosecutors announced they would be seeking the death penalty for Aoba.[102] On 25 January 2024, the court announced that Aoba had been sentenced to death.[103][104][105] The day after, Aoba filed an appeal against the death sentence.[106] Aoba told a local press that he "accepted the death sentence", but he went ahead with the appeal as he wanted to "speak out".[107]

Aftermath

One month after the arson attack, the victims began to return to work at the other Kyoto Animation studio.[108][109] As of October 2019, while the number of Kyoto Animation employees decreased from 176 to 137, 27 of the surviving 33 victims returned to work with several having decided to take extended breaks to cope with the stress and anxiety brought by the attack.[109][110][111]

The company issued an official statement, requesting respect for the victims and their family members, and also stating that all future statements will be either through the police or their lawyers.[112] The demolition process of the building was completed on 28 April 2020, with no further plans for the site revealed.[113] In an earlier interview, Kyoto Animation's president Hideaki Hatta stated that he was considering replacing the building with a green public park and a memorial monument.[78][114] However, residents in the neighbourhood did not wish for a memorial to be built, claiming visitors paying their respects would "destroy the peaceful lifestyle [of local residents]".[115]

Due to recovery efforts, Kyoto Animation suspended the 11th Kyoto Animation Awards, an annual award to discover new stories.[116]

In November 2019, the studio decided to continue training programmes for aspiring animators, in which trainees would be trained in movies, sketching and animations. Upon graduating from the programme, outstanding trainees could be recruited by the studio after being examined further.[117]

Impact on productions

In response to the attack, a publicity event for the upcoming 2020 film Free! was cancelled. Kyoto Animation's Sound! Euphonium collaboration with Keihan Main Line was delayed, as was episode 4 of BEM.[118] The third episode of David Production's Fire Force, an anime series about firefighters and people dying from spontaneous combustion, was delayed for a week and released with the colours of the fires and narration modified.[119][120][121][122] Subsequent episodes of Fire Force were dealt with in a similar manner.[122] The studio decided to push on with premiering Violet Evergarden: Eternity and the Auto Memory Doll on 3 August 2019 at Germany's AnimagiC convention as originally scheduled.[123] The Japanese theatrical screening dates were extended by an extra week[124] and honored the victims in the end credits.[125] Despite earlier news reports stating that the upcoming Violet Evergarden film would premiere as scheduled on 10 January 2020,[126] it was later announced to be delayed to 24 April 2020, but as a result of the COVID-19 pandemic, the premiere was again delayed to 18 September 2020.[127] An episode for Animation x Paralympic, originally due to be aired in August 2019, was eventually announced as cancelled on 28 February 2020, citing that they would be unable to complete it in time for the 2020 Paralympics.[128]

Measures to prevent recurrence

The Fire and Disaster Management Agency and the National Police Agency issued a notice on 25 July 2019, requiring gas stations to maintain sales records of people purchasing gasoline in refillable containers, which conform to fire safety regulations.[129] Each record is to contain the buyer's personal information such as name, address, the purpose of the purchase, and quantity purchased.[129] Although the notice had no legal backing, most buyers complied with this additional requirement voluntarily.[130] This measure was formalised with the relevant regulations revised and coming into force on 1 February 2020 to make the sales records mandatory.[130][131] Post incident, the Kyoto Municipal Fire Department formulated guidelines for evacuation in the event of arson or terrorism and encouraged the installation of evacuation ladders.[132]

As a result of the attack, police in Japan became more vigilant with death threats directed at other companies (especially Khara,[133] Square Enix,[134] Animate,[135] and Clannad developer company Key,[136] who received later threats referencing the Kyoto Animation attack).

Memorial

A tribute video was published, one year after the attack, on 18 July 2020.[137] The company had considered holding a memorial ceremony, but in light of the COVID-19 pandemic in Japan, decided against it.[138] Similarly, at 10:30 am JST on 18 July 2021, Kyoto Animation's YouTube channel streamed a 13-minute video to "provide a place for everyone to share their thoughts and feelings".[139] In the video were messages and tributes from the studio, from staff members, and from the families of some of the deceased. The company requested that fans not visit the former site of Studio 1 on the anniversary of the incident to respect the wishes of local residents.[138]

Reactions

File:Kyoto animation arson attack 2 20190721.jpg
The entrance to the studio after the arson attack. Bouquets and beverages are placed in memorial.
File:The floral tributes at Rokujizo Station 2019-08-10(1) sa.jpg
Flowers that have been installed in the field near Rokujizō Station

Kyoto Animation accepted direct donations through a local bank account to help the victims of the attack from 23 July 2019 to 27 December 2019.[140][141][142] Eventually, the bank account had accumulated approximately ¥3.3 billion (US$FXConvert/Wordify error: cannot parse value "Expression error: Unrecognized punctuation character "[".").[143] The donations included separate ¥10 million donations from the Japanese musician Yoshiki and game developer Key.[144][145][146] It was estimated that the company would require as much as ¥10 billion to cover the cost of supporting the victims and affected families and company-related business operating recovery expenses.[147] As of November 2019, the company has begun the process of distributing the funds raised to the victims, with each victim receiving an appropriate amount after factoring various considerations such as severity of injuries, whether the victim is a sole breadwinner, etc.[148]

Domestic

Prime Minister Shinzo Abe expressed his condolences and stated that he was "speechless" at the scale of the incident.[lower-alpha 4] A first in Japanese corporate history, a measure was passed in the National Diet to allow for donations to the studio to be tax-exempt.[4] The Chinese, French, Philippine, and Belgian embassies in Japan provided their own words of condolence.[lower-alpha 4]

Numerous people and organisations related to the industry expressed concern and support, such as anime directors Makoto Shinkai and Tatsuki [ja], K-On! voice actress Aki Toyosaki, The Melancholy of Haruhi Suzumiya voice actresses Aya Hirano, Minori Chihara, and Yūko Gotō, Hyōka author Honobu Yonezawa, Clannad developer company Key, and media company Kadokawa Corporation.[lower-alpha 4] Animation studios such as Shaft, Sunrise, Bandai Namco Pictures, Toei Animation, Bones, Khara, Trigger, Walt Disney Japan, and Madhouse all offered their support as well.[lower-alpha 4]

Animate, a major Japanese retailer of anime, video games, and manga, took donations at all of their stores to support the victims,[167] and had raised over ¥330 million by 1 September.[168]

International

Several foreign dignitaries, including Tsai Ing-wen, António Guterres, and others, offered their own messages of support for the victims.[lower-alpha 4]

In the wake of the fire, a GoFundMe appeal was launched by American anime licensor Sentai Filmworks.[76] With a target of US$750,000, it surpassed the US$1 million donation mark within the first 24 hours.[169][170][171] It had received US$2.3 million at the end of the appeal.[172] As of 7 December 2019, Sentai had transferred all of the funds raised, except for credit card processing fees, to Kyoto Animation studio.[173]

Fans have also taken to Kyoto Animation's Japanese digital store to directly contribute by purchasing high-resolution downloadable images as they do not require staff to ship them.[174] American licensing companies Aniplex of America, Funimation and Crunchyroll, and Nickelodeon Animation Studio all offered their support.[149] Adult Swim's anime-oriented Toonami block started their 20 July broadcast asking viewers to donate to the GoFundMe set up by Sentai Filmworks.[175]

See also

Notes

  1. Many sources reported on the number of victims.[16][37][38][39][40][41][42][43]
  2. 2.0 2.1 2.2 2.3 2.4 Reports on the number and identity of the injured and dead from many sources.[12][58][59][37][42][48][60][61][43][62][63]
  3. Plagiarism reports from many sources.[21][34][74][75][76][77]
  4. 4.0 4.1 4.2 4.3 4.4 Condolences and support were expressed by many.[5][149][150][151][152][153][154][155][156][157][158][159][160][161][162][163][164][165][166]

References

  1. 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 4.2 Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 5.2 5.3 Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. 12.0 12.1 12.2 12.3 Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. 19.0 19.1 Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. 21.0 21.1 Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. 23.0 23.1 Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.0 25.1 Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. 34.0 34.1 Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. 37.0 37.1 Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. 42.0 42.1 42.2 Lua error in package.lua at line 80: module 'strict' not found.
  43. 43.0 43.1 Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. 48.0 48.1 Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. 64.0 64.1 64.2 Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. 66.0 66.1 Lua error in package.lua at line 80: module 'strict' not found.
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. 70.0 70.1 Lua error in package.lua at line 80: module 'strict' not found.
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Lua error in package.lua at line 80: module 'strict' not found.
  76. 76.0 76.1 Lua error in package.lua at line 80: module 'strict' not found.
  77. Lua error in package.lua at line 80: module 'strict' not found.
  78. 78.0 78.1 Lua error in package.lua at line 80: module 'strict' not found.
  79. Lua error in package.lua at line 80: module 'strict' not found.
  80. Lua error in package.lua at line 80: module 'strict' not found.
  81. Lua error in package.lua at line 80: module 'strict' not found.
  82. Lua error in package.lua at line 80: module 'strict' not found.
  83. Lua error in package.lua at line 80: module 'strict' not found.
  84. Lua error in package.lua at line 80: module 'strict' not found.
  85. Lua error in package.lua at line 80: module 'strict' not found.
  86. Lua error in package.lua at line 80: module 'strict' not found.
  87. Lua error in package.lua at line 80: module 'strict' not found.
  88. Lua error in package.lua at line 80: module 'strict' not found.
  89. Lua error in package.lua at line 80: module 'strict' not found.
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. 91.0 91.1 Lua error in package.lua at line 80: module 'strict' not found.
  92. 92.0 92.1 Lua error in package.lua at line 80: module 'strict' not found.
  93. Lua error in package.lua at line 80: module 'strict' not found.
  94. Lua error in package.lua at line 80: module 'strict' not found.
  95. Lua error in package.lua at line 80: module 'strict' not found.
  96. Lua error in package.lua at line 80: module 'strict' not found.
  97. Lua error in package.lua at line 80: module 'strict' not found.
  98. Lua error in package.lua at line 80: module 'strict' not found.
  99. Lua error in package.lua at line 80: module 'strict' not found.
  100. Lua error in package.lua at line 80: module 'strict' not found.
  101. Lua error in package.lua at line 80: module 'strict' not found.
  102. Lua error in package.lua at line 80: module 'strict' not found.
  103. Lua error in package.lua at line 80: module 'strict' not found.
  104. Lua error in package.lua at line 80: module 'strict' not found.
  105. Lua error in package.lua at line 80: module 'strict' not found.
  106. Lua error in package.lua at line 80: module 'strict' not found.
  107. Lua error in package.lua at line 80: module 'strict' not found.
  108. Lua error in package.lua at line 80: module 'strict' not found.
  109. 109.0 109.1 Lua error in package.lua at line 80: module 'strict' not found.
  110. Lua error in package.lua at line 80: module 'strict' not found.
  111. Lua error in package.lua at line 80: module 'strict' not found.
  112. Lua error in package.lua at line 80: module 'strict' not found.
  113. Lua error in package.lua at line 80: module 'strict' not found.
  114. Lua error in package.lua at line 80: module 'strict' not found.
  115. Lua error in package.lua at line 80: module 'strict' not found.
  116. Lua error in package.lua at line 80: module 'strict' not found.
  117. Lua error in package.lua at line 80: module 'strict' not found.
  118. Lua error in package.lua at line 80: module 'strict' not found.
  119. Lua error in package.lua at line 80: module 'strict' not found.
  120. Lua error in package.lua at line 80: module 'strict' not found.
  121. Lua error in package.lua at line 80: module 'strict' not found.
  122. 122.0 122.1 Lua error in package.lua at line 80: module 'strict' not found.
  123. Lua error in package.lua at line 80: module 'strict' not found.
  124. Lua error in package.lua at line 80: module 'strict' not found.
  125. Lua error in package.lua at line 80: module 'strict' not found.
  126. Lua error in package.lua at line 80: module 'strict' not found.
  127. Lua error in package.lua at line 80: module 'strict' not found.
  128. Lua error in package.lua at line 80: module 'strict' not found.
  129. 129.0 129.1 Lua error in package.lua at line 80: module 'strict' not found.
  130. 130.0 130.1 Lua error in package.lua at line 80: module 'strict' not found.
  131. Lua error in package.lua at line 80: module 'strict' not found.
  132. Lua error in package.lua at line 80: module 'strict' not found.
  133. Lua error in package.lua at line 80: module 'strict' not found.
  134. Lua error in package.lua at line 80: module 'strict' not found.
  135. Lua error in package.lua at line 80: module 'strict' not found.
  136. Lua error in package.lua at line 80: module 'strict' not found.
  137. Lua error in package.lua at line 80: module 'strict' not found.
  138. 138.0 138.1 Lua error in package.lua at line 80: module 'strict' not found.
  139. Lua error in package.lua at line 80: module 'strict' not found.
  140. Lua error in package.lua at line 80: module 'strict' not found.
  141. Lua error in package.lua at line 80: module 'strict' not found.
  142. Lua error in package.lua at line 80: module 'strict' not found.
  143. Lua error in package.lua at line 80: module 'strict' not found.
  144. Lua error in package.lua at line 80: module 'strict' not found.
  145. Lua error in package.lua at line 80: module 'strict' not found.
  146. Lua error in package.lua at line 80: module 'strict' not found.
  147. Lua error in package.lua at line 80: module 'strict' not found.
  148. Lua error in package.lua at line 80: module 'strict' not found.
  149. 149.0 149.1 Lua error in package.lua at line 80: module 'strict' not found.
  150. Lua error in package.lua at line 80: module 'strict' not found.
  151. Lua error in package.lua at line 80: module 'strict' not found.
  152. Lua error in package.lua at line 80: module 'strict' not found.
  153. Lua error in package.lua at line 80: module 'strict' not found.
  154. Lua error in package.lua at line 80: module 'strict' not found.
  155. Lua error in package.lua at line 80: module 'strict' not found.
  156. Lua error in package.lua at line 80: module 'strict' not found.
  157. Lua error in package.lua at line 80: module 'strict' not found.
  158. Lua error in package.lua at line 80: module 'strict' not found.
  159. Lua error in package.lua at line 80: module 'strict' not found.
  160. Lua error in package.lua at line 80: module 'strict' not found.
  161. Lua error in package.lua at line 80: module 'strict' not found.
  162. Lua error in package.lua at line 80: module 'strict' not found.
  163. Lua error in package.lua at line 80: module 'strict' not found.
  164. Lua error in package.lua at line 80: module 'strict' not found.
  165. Lua error in package.lua at line 80: module 'strict' not found.
  166. Lua error in package.lua at line 80: module 'strict' not found.
  167. Lua error in package.lua at line 80: module 'strict' not found.
  168. Lua error in package.lua at line 80: module 'strict' not found.
  169. Lua error in package.lua at line 80: module 'strict' not found.
  170. Lua error in package.lua at line 80: module 'strict' not found.
  171. Lua error in package.lua at line 80: module 'strict' not found.
  172. Lua error in package.lua at line 80: module 'strict' not found.
  173. Lua error in package.lua at line 80: module 'strict' not found.
  174. Lua error in package.lua at line 80: module 'strict' not found.
  175. Lua error in package.lua at line 80: module 'strict' not found.

External links

  • Media related to Lua error in package.lua at line 80: module 'strict' not found. at Wikimedia Commons