DoDonPachi - Revision history

Brunoxsa at 01:13, 30 November 2025

2025-11-30T01:13:56Z

Brunoxsa: Reassigning direct links to the new bee item map pages.

2025-11-29T16:54:30Z

Reassigning direct links to the new bee item map pages.

S: /* Second Loop */

2025-11-28T05:44:43Z

Second Loop

Plasmo at 05:51, 10 August 2025

2025-08-10T05:51:09Z

JSAV2006STG(ABC): /* What causes the glitch? */

2025-08-10T05:44:14Z

What causes the glitch?

JSAV2006STG(ABC): /* Activating the glitch */

2025-08-10T05:43:52Z

Activating the glitch

JSAV2006STG(ABC): /* Bugs */

2025-08-10T05:43:15Z

Bugs

Plasmo: /* Gallery */

2025-04-18T04:59:52Z

Gallery

JSAV2006STG(ABC): /* Development History */

2024-05-05T18:12:25Z

Development History

Plasmo at 14:47, 5 May 2024

2024-05-05T14:47:50Z

@@ Line 19: / Line 19: @@
 | nextgame = [[ESP Ra.De]]
 }}
-'''DoDonPachi''' <small>(怒首領蜂 "Angry Leader Bee", abbreviated: '''DDP''')</small> is the second entry in the [[:Category:DonPachi series|''DonPachi'' series]] of [[shooting game|shoot-em-ups]], developed and released by [[CAVE]]. It expanded upon the chaining system innovated in the [[DonPachi|first game]] in the series, and introduced a "variation system" that allowed you to pick two different styles of three ships (Shot and Laser types), giving the player a slightly higher degree of playstyle customization.
+'''''DoDonPachi''''' <small>(怒首領蜂 "Angry Leader Bee", abbreviated: '''DDP''')</small> is the second entry in the [[:Category:DonPachi series|''DonPachi'' series]] of [[shooting game|shoot-em-ups]], developed and released by [[CAVE]]. It expanded upon the chaining system innovated in the [[DonPachi|first game]] in the series, and introduced a "variation system" that allowed you to pick two different styles of three ships (Shot and Laser types), giving the player a slightly higher degree of playstyle customization.
 This game in particular is considered by most STG enthusiasts to be the grandfather of the ''bullet hell'' sub-genre of shooting games, pushing bullet counts into the '''hundreds''', especially if the player is able to reach the second [[loop]]. ''DoDonPachi'' is also the first game in the series to introduce [[Hibachi]], the [[True Last Boss]], who would return in all future ''DonPachi'' games as a challenge for particularly skilled players.

@@ Line 302: / Line 302: @@
 {| class="wikitable"
 |-
-| [[DoDonPachi/stage1_beemap|Stage 1]] || [[DoDonPachi/stage2_beemap|Stage 2]] || [[DoDonPachi/stage3_beemap|Stage 3]] || [[DoDonPachi/stage4_beemap|Stage 4]] || [[DoDonPachi/stage5_beemap|Stage 5]] || [[DoDonPachi/stage6_beemap|Stage 6]]
+| [[DoDonPachi/Stage 1 Bee Map|Stage 1]] || [[DoDonPachi/Stage 2 Bee Map|Stage 2]] || [[DoDonPachi/Stage 3 Bee Map|Stage 3]] || [[DoDonPachi/Stage 4 Bee Map|Stage 4]] || [[DoDonPachi/Stage 5 Bee Map|Stage 5]] || [[DoDonPachi/Stage 6 Bee Map|Stage 6]]
 |}

@@ Line 330: / Line 330: @@
 Like its predecessor ''DonPachi'', ''DoDonPachi'' features a second loop with more aggressive enemies firing much larger amounts of bullets at a higher frequency. Accessing the second loop is the only way to fight the EX Boss [[Taisabachi]] and the [[True Last Boss]] of the game, [[Hibachi]].
-However, unlike ''DonPachi'', the player must meet certain requirements during play in order to access the second loop. To get to the second loop, the player must accomplish any '''one''' of the following four tasks:
+However, unlike ''DonPachi'', the player must meet certain requirements during play in order to access the second loop. To get to the second loop, the player must complete the first loop on one credit and accomplish any '''one''' of the following four tasks:
 * Lose a ship '''two times or less'''.

@@ Line 443: / Line 443: @@
 ====The source of the glitch====
-[[File:DDP_glitcho.png|thumb|right|"Glitcho / Bug (バグ)"]]
+[[File:DDP_glitcho.png|thumb|right|"Glitcho"]]
-During the stage the player encounters four honeycombs with an enemy sitting on top, upon destroying it, turrets will endlessly spawn from the honeycomb. As the turrets are an easy way to build chain hits and the enemy guarding the honeycomb has both low HP and low amount of bullets fired, it usually goes unnoticed. This enemy is what causes the Double GP glitch to occur.
+During the stage the player encounters four honeycombs with an enemy sitting on top, upon destroying it infinitely spawning turrets will start emerging from the honeycomb. As the turrets are an easy way to build chain hits and the enemy guarding the honeycomb has both low HP and low amount of bullets fired, it usually goes unnoticed. This enemy is what causes the Double GP glitch.
-Glitcho / Bug ''normally'' gives 10 points for its base value, which is the lowest existing base value in the game. There are only two other sources for a 10 points base value: the missiles fired by the truck enemies at the start of stage 1-6 and 2-6 and Laser Hits.
+Glitcho ''normally'' gives 10 points for its base value, which is the lowest existing base value in the game. There are only two other sources for a 10 points base value: the missiles fired by the truck enemies at the start of stage 1-6 and 2-6 and Laser Hits.
 ====Activating the glitch====
-The glitch happens upon gaining a Laser Hit and destroying Glitcho / Bug '''in the same frame'''. As Glitcho / Bug has very low HP the player has to use the Laser while it is at the very top of the screen (thus being invincible), but doing so prematurely will lead to gaining the Laser Hit before Glitcho / Bug is destroyed, this won't trigger the glitch. Furthermore, an enemy can't get in the way of the Laser, even ones that wouldn't block it such as [[Help:Glossary#Popcorn|zakos]] (if the player is using a Laser Type) otherwise the frame count for the Laser Hit will be interrupted, again failing to activate the glitch. A cue to know whether the glitch was done succesfully or not is the chain Hit count will increase by 2 upon destroying Glitcho / Bug.
+The glitch happens upon gaining a Laser Hit and destroying Glitcho '''in the same frame'''. As Glitcho has very low HP the player has to use the Laser while it is at the very top of the screen (thus being invincible), but doing so prematurely will lead to gaining the Laser Hit before Glitcho is destroyed, this won't trigger the glitch. Furthermore, an enemy can't get in the way of the Laser, even ones that wouldn't block it such as [[Help:Glossary#Popcorn|zakos]] (if the player is using a Laser Type) otherwise the frame count for the Laser Hit will be interrupted, again failing to activate the glitch. A cue to know whether the glitch was done succesfully or not is the chain Hit count will increase by 2 upon destroying Glitcho.
 Because of the precision involved when triggering the glitch it's likely setups wouldn't be transferable from one ship to the other, especially for the case of Shot Types as they each have different activation speeds and Laser damage.
@@ Line 456: / Line 456: @@
 ====What causes the glitch?====
-Each enemy’s base value is hard-coded into their programming. When an enemy is destroyed, the game executes standard code that processes scoring from killing an enemy, or from sustained Laser Hits, etc. While every enemy has a hard-coded number programmed for the score value that is used when calculating the chain scoring, Glitcho / Bug is simply missing this very important hard-coded number. All of Glitcho’s / Bug’s scoring is a glitch, not just the double GP.
+Each enemy’s base value is hard-coded into their programming. When an enemy is destroyed, the game executes standard code that processes scoring from killing an enemy, or from sustained Laser Hits, etc. While every enemy has a hard-coded number programmed for the score value that is used when calculating the chain scoring, Glitcho is simply missing this very important hard-coded number. All of Glitcho’s scoring is a glitch, not just the double GP.
-As a result, the chain scoring simply operates on whatever junk data is loaded into memory. Under normal circumstances, holding the Laser on an enemy adds 10 points to the GP value, and then adds it to both the player's score and the total Chain value. That 10 points from holding the Laser is what causes Glitcho / Bug to give 10 points normally, even on frames that it doesn’t do this addition memory is loaded with a value representing 10 points for this. On the frame that the sustained Laser hit adds to the hit counter, and the score addition actually happens though, the game reloads this memory a few times to do score math.
+As a result, the chain scoring simply operates on whatever junk data is loaded into memory. Under normal circumstances, holding the Laser on an enemy adds 10 points to the GP value, and then adds it to both the player's score and the total Chain value. That 10 points from holding the Laser is what causes Glitcho to give 10 points normally, even on frames that it doesn’t do this addition memory is loaded with a value representing 10 points for this. On the frame that the sustained Laser hit adds to the hit counter, and the score addition actually happens though, the game reloads this memory a few times to do score math.
-At the end of the function, the last thing it does is add the GP value to the player score, this is done by loading that same memory with the current GP value. When the function is done, the GP value lingers in memory. A normal enemy would overwrite this memory with the base value of the enemy. Glitcho / Bug, however, doesn't do this. As a result, most of the time Glitcho / Bug awards with 10 points. On the Laser Hit + kill frame however, Glitcho / Bug awards the GP value instead, effectively doubling it (since the GP value is added to itself).
+At the end of the function, the last thing it does is add the GP value to the player score, this is done by loading that same memory with the current GP value. When the function is done, the GP value lingers in memory. A normal enemy would overwrite this memory with the base value of the enemy. Glitcho, however, doesn't do this. As a result, most of the time Glitcho awards with 10 points. On the Laser Hit + kill frame however, Glitcho awards the GP value instead, effectively doubling it (since the GP value is added to itself).
 ====Scoring potential====
@@ Line 514: / Line 514: @@
 The GP value before the glitch is at 77,860. When the glitch is triggered at 359 hits > 361 hits (green boxes in the table), the second hit of it exactly doubles your GP value to 155,720. This GP value then increases normally afterwards again. Incidentally, what follows is another frame perfect double kill (two enemies with a Base value of 120 points each), but this is calculated normally.
-The point gain from the Double GP Glitch is highly dependent on the current GP value. Consequently, the first honeycomb is worth significantly less than any of the later ones, as the GP value is naturally increasing with a higher chain. As Glitcho / Bug is essentially doubling the GP value, its normal Base value of 10 points is overwritten by the number of the current GP value.
+The point gain from the Double GP Glitch is highly dependent on the current GP value. Consequently, the first honeycomb is worth significantly less than any of the later ones, as the GP value is naturally increasing with a higher chain. As Glitcho is essentially doubling the GP value, its normal Base value of 10 points is overwritten by the number of the current GP value.
 For the following scenarios, the Double GP Glitch is only triggered once and the rest of the stage is fully chained with about 900 hits.
@@ Line 525: / Line 525: @@
 ! Point gain
 |-
-| 1st Glitcho / Bug || 22,000 || 730 || 16,060,000
+| 1st Glitcho || 22,000 || 730 || 16,060,000
 |-
-| 2nd Glitcho / Bug || 59,000 || 460 || 27,140,000
+| 2nd Glitcho || 59,000 || 460 || 27,140,000
 |-
-| 3rd Glitcho / Bug || 61,000 || 445 || 27,145,000
+| 3rd Glitcho || 61,000 || 445 || 27,145,000
 |-
-| 4th Glitcho / Bug || 67,000 || 410 || 27,470,000
+| 4th Glitcho || 67,000 || 410 || 27,470,000
 |-
 |}
@@ Line 537: / Line 537: @@
 The total point gain in the last column refers to the score the player would get on top of their regular score, i.e. the actual score from triggering the glitch alone. As this calculation does not take into account the fact chain hits would be lost under normal circumstances due to correctly setting up for the glitch to work, these numbers are most likely lower in an actual run. Therefore, the score gain would be expected to be 15m from the first and about 25m from the other three when triggered in isolation.
-Doing a final calculation for all four Glitchos / Bugs triggered consecutively within one run brings up to the following numbers. Note that these numbers do not take into account the regular score from the stage but purely reflect what the Glitchos / Bugs add to this.
+Doing a final calculation for all four Glitchos triggered consecutively within one run brings up to the following numbers. Note that these numbers do not take into account the regular score from the stage but purely reflect what the Glitchos add to this.
 {| class="wikitable" style="text-align:center"

@@ Line 458: / Line 458: @@
 Each enemy’s base value is hard-coded into their programming. When an enemy is destroyed, the game executes standard code that processes scoring from killing an enemy, or from sustained Laser Hits, etc. While every enemy has a hard-coded number programmed for the score value that is used when calculating the chain scoring, Glitcho / Bug is simply missing this very important hard-coded number. All of Glitcho’s / Bug’s scoring is a glitch, not just the double GP.
-As a result, the chain scoring simply operates on whatever junk data is loaded into memory. Under normal circumstances, holding the Laser on an enemy adds 10 points to the GP value, and then adds it to both the player's score and the total Chain value. That 10 points from holding the Laser is what causes Glitcho to give 10 points normally, even on frames that it doesn’t do this addition memory is loaded with a value representing 10 points for this. On the frame that the sustained Laser hit adds to the hit counter, and the score addition actually happens though, the game reloads this memory a few times to do score math.
+As a result, the chain scoring simply operates on whatever junk data is loaded into memory. Under normal circumstances, holding the Laser on an enemy adds 10 points to the GP value, and then adds it to both the player's score and the total Chain value. That 10 points from holding the Laser is what causes Glitcho / Bug to give 10 points normally, even on frames that it doesn’t do this addition memory is loaded with a value representing 10 points for this. On the frame that the sustained Laser hit adds to the hit counter, and the score addition actually happens though, the game reloads this memory a few times to do score math.
 At the end of the function, the last thing it does is add the GP value to the player score, this is done by loading that same memory with the current GP value. When the function is done, the GP value lingers in memory. A normal enemy would overwrite this memory with the base value of the enemy. Glitcho / Bug, however, doesn't do this. As a result, most of the time Glitcho / Bug awards with 10 points. On the Laser Hit + kill frame however, Glitcho / Bug awards the GP value instead, effectively doubling it (since the GP value is added to itself).

@@ Line 744: / Line 744: @@
 <gallery>
-DDP saturn competition.jpg|Results of the scoring competition<ref>[https://twitter.com/Plasmo_STG/status/1101929581529976833 Tweet by ASE-Plasmo]</ref>.
+DDP saturn competition.jpg|Results of the scoring competition<ref>Gamest #212 (1998-1.30/2.15), p. 209</ref>.
 DDP CV warning screen.png|Warning screen<ref name="sammy-house-blog">[https://blog.goo.ne.jp/summyhouse/e/9003ab783f31b5a6f07cebf88188649b Sammy House Blog]</ref>.
 DDP CV PCB.jpg|PCB<ref name="sammy-house-blog" />.

@@ Line 368: / Line 368: @@
 == Development History ==
-DoDonPachi's development began shortly after the release of its predecessor, [[DonPachi]]. It was the second game developed by Cave; DDP ended up being the favored game over another canceled project, "Danmaku Tengoku";
+DoDonPachi's development began shortly after the release of its predecessor, [[DonPachi]]. It was the second game developed by CAVE; DDP ended up being the favored game over another canceled project, "Danmaku Tengoku";
-that game's development was terminated due to unsolvable problems regarding art & sprite design. Another canceled Cave game, "Oni Death", was also worked on in parallel with DDP, but it too ended up being canceled
+that game's development was terminated due to unsolvable problems regarding art & sprite design. Another canceled CAVE game, "Oni Death", was also worked on in parallel with DDP, but it too ended up being canceled
 for unknown reasons despite having a solid concept and graphical design.
@@ Line 376: / Line 376: @@
 and finally Ikeda himself was tired of the mechanic itself and how it impacted gameplay.
-In the middle of DDP's development, manga artist Junya Inoue joined Cave and the project. When he joined, the only work left to be done was the ship select, opening demo, last boss, and ending. It was Inoue who
+In the middle of DDP's development, manga artist Junya Inoue joined CAVE and the project. When he joined, the only work left to be done was the ship select, opening demo, last boss, and ending. It was Inoue who
 asked IKD "Could I put a colonel or something like that at the end?"; he was given the greenlight for the design and text of the series' villain, Colonel Schwarlitz Longhena. Inoue's general attitude towards
 DDP's art was very relaxed, yet directionless; "[...]things like the story and opening weren't seen as very important. So my boss at the time told me, 'It's not that important, so Inoue, you do it.'" He
 was lost as to what he should have done, as since most of the art was already complete, he struggled to come up with a story after the fact - something that many years later he still wonders about.
-Despite this, "I ended up studying up on DonPachi, and realized it didn't have that deep of a story. Well, now I could relax a little...and with that feeling my work at Cave began." He further elaborates on his
+Despite this, "I ended up studying up on DonPachi, and realized it didn't have that deep of a story. Well, now I could relax a little...and with that feeling my work at CAVE began." He further elaborates on his
 methodology; "[...]I think that for each game you work on you have to take things according to their circumstances, and not be too hung up on particular ideas. I think that in a game's characters and background,
 you find the core of the story, and the world of the game flows from there." DonPachi/DoDonPachi had a world and story that - in contrast to many games at the time - were not that intertwined; while Inoue
 tried his hardest to create a backstory, "I thought I would never reach something on the level of the Raystorm games. With that being the case, I had a very blasé attitude about it and the result was that I just worked on
 things in a very casual way, not taking it too seriously." In light of all of his work, Inoue wishes to not recieve too much credit/respect for DDP; he wants IKD to have that instead, for he was the one that designed
-the game's "charismatic bosses". A senior employee at Cave - as told by Inoue - announced that his image for DDP was Space Battleship Yamato. With this in mind, Inoue thought about "refining the story of DDP
+the game's "charismatic bosses". A senior employee at CAVE - as told by Inoue - announced that his image for DDP was Space Battleship Yamato. With this in mind, Inoue thought about "refining the story of DDP
 to be more like 70s era sci-fi, and the phrase 'shinu ga yoi' just came out naturally. [...] They seemed like phrases that Battleship Yamato villains like Lord Desler or Emperor Zwoda would say."
-IKD recalls in an interview for Cave's 15th anniversary, that while Inoue had a small part in DDP's development, he - in his typical fashion - would later be critical of the game's setting; saying "This colorful world of mechas is ridiculous!". This directly influenced the art direction of the next game by Cave - ESP.RA.DE. - as Inoue was assigned as its graphic leader, and wanted a "more realistic" and "inhabited" world for it, in contrast to DDP.
+IKD recalls in an interview for CAVE's 15th anniversary, that while Inoue had a small part in DDP's development, he - in his typical fashion - would later be critical of the game's setting; saying "This colorful world of mechas is ridiculous!". This directly influenced the art direction of the next game by Cave - ESP.RA.DE. - as Inoue was assigned as its graphic leader, and wanted a "more realistic" and "inhabited" world for it, in contrast to DDP.
-When designing the game's true final boss - Hibachi - Tsuneki Ikeda recalls it conceptually being a test for the limits of human dodging ability, so there wasn't an intended "requirement" for lives/bombs
+When designing the game's True Last Boss, Hibachi, Tsuneki Ikeda recalls it conceptually being a test for the limits of human dodging ability, so there wasn't an intended "requirement" for lives/bombs
 when a player reaches them; it was more so of "can this be done on one credit?" - this perhaps is the reason why he would later say that a NMNB clear of DDP was "theoretically humanly possible".
 The reason for Hibachi's small size, as he says, was for having more space on the screen to create the danmaku patterns (which memory limitations ensured was the only way); its first form,
-the Final Demonic Weapon aka "Big Bee" was closer to his original image of a final boss. However, this ended up conflicting with other things he wanted to do, as its size made it impossible to
+the Final Demonic Weapon aka "Big Bee / Hachi" was closer to his original image of a Last Boss. However, this ended up conflicting with other things he wanted to do, as its size made it impossible to
 create truly hellish patterns; thus he chose its patterns over sprite design (which dumbfounded the other graphic designers on the project). During the last portion of the game's development
-(the final 2-3 weeks where extensive playtesting and debugging were done), Cave determined that the boss as-is was possible, and so it was left at that difficulty; a difficulty level that as
+(the final 2-3 weeks where extensive playtesting and debugging were done), CAVE determined that the boss as-is was possible, and so it was left at that difficulty; a difficulty level that as
 later revealed was specifically tailored for average people: to make DDP a "user friendly game".
 This is a sentiment that IKD would contradict much later; in a 2010 issue of Arcadia magazine he says that "I actually thought [Hibachi] might be impossible", recalling how even the STG lovers
-at Cave deemed DDP "WAY too much!" He wanted Hibachi to "give even advanced players a fight that would test their skills to the utmost. [...] if you weren't gritting your teeth to the end
+at CAVE deemed DDP "WAY too much!" He wanted Hibachi to "give even advanced players a fight that would test their skills to the utmost. [...] if you weren't gritting your teeth to the end
 of that fight, it would be meaningless. I wanted people to look at Hibachi and laugh, to be like 'This is ridiculous!'" The idea of Hibachi having a bomb barrier came from a joke him and a senior colleague
 at Toaplan used to share: “Hey, wouldn’t it be funny if, when you used a bomb on the last boss, he put up a barrier? Hahaha…” While IKD said at the time that it would be too far,
 "[..]secretly I was thinking to myself: this is a great idea. When the time came for DDP, I thought with Hibachi, it's now or never! And it became a basic feature of all our final bosses after that."
-After the game's release, Cave would later remark that they were very confident about the game and its demonstration of (at the time) the enduring popularity of STG arcade games. Satoshi Kouyama,
+After the game's release, CAVE would later remark that they were very confident about the game and its demonstration of (at the time) the enduring popularity of STG arcade games. Satoshi Kouyama,
 a sub-programmer of the game, remarked that the heart of the game's fun is a "simple joy of dodging bullets"/"that visceral experience of dodging the patterns"; that is, it attracts both superplayers
 and everyday players (such as having people swarm its arcade cabinets, which is the first game IKD developed that got that treatment). He says that the opinion of normal players was where
-everything was risked - whether or not they would enjoy the bullet dodging - thus, to see that idea understood and praised, pleased Cave. Much later, in 2010, IKD would tell that
+everything was risked - whether or not they would enjoy the bullet dodging - thus, to see that idea understood and praised, pleased CAVE. Much later, in 2010, IKD would tell that
 "as [DDP] neared completion, I started to think about it more objectively, and worried, 'There's a chance this might be hated by everyone...'" due to the game's sheer bullet count.
-This is not to say that superplayers were disregarded; on the contrary, Cave thought that it would take 6 months a player to achieve a 2-ALL (completing both loops):
+This is not to say that superplayers were disregarded; on the contrary, CAVE thought that it would take 6 months a player to achieve a 2-ALL (completing both loops):
 in reality it took only a month, a fact that shocked Kouyama when he and IKD learned of the news. As said before, the game's playtesting intensified towards the end of development; one
 method used was calculating scoring limits by way of using invincibility. They ended up only reaching around 400 million, 200 million lower than the world record at the time in 1997:
@@ Line 418: / Line 418: @@
 Speaking of 1997, there was another variant of the game being developed for a scoring competition to celebrate the release of the later ill-seen Sega Saturn port;
-this was titled "DoDonPachi Campaign Version". For more information about this version, go here.
+this was titled "DoDonPachi Campaign ver.". For more information about this version, go here.
 The editors of Gamest in 1998 remarked of how their love of DDP stemmed from the Get Point System; as it "allows players who are just going for a clear to start gradually and
@@ Line 427: / Line 427: @@
 as summed by a Gamest interviewer. IKD said of how during [[DonPachi]] that a friend of his told him of how "It would be more fun if you could do more chaining", which he agreed with.
-The game's lengthy and overall relaxed development allowed Cave, according to IKD, to make the game that they truly wanted. While development typically would end with the want of a few more
+The game's lengthy and overall relaxed development allowed CAVE, according to IKD, to make the game that they truly wanted. While development typically would end with the want of a few more
 additions or polish, DoDonPachi was felt to be a genuinely complete game after development concluded. The triad of difficulty balance, enemy placement, and danmaku patterns
 respectively having so much time spent upon them is a large part of why - as IKD believes - DDP succeeded. Kouyama adds that due to much of the basics already having been built
 in the preceding game [[DonPachi]] there wasn't much time needed to work on the finer details of gameplay; focus could be directed to the things that they wanted to work on.
-IKD was very thankful to have such time, and while he was happy if he could give Cave's next game the same treatment, he "somehow doubt[ed] that will be the case", a sentiment which would turn out to be correct.
+IKD was very thankful to have such time, and while he was happy if he could give CAVE's next game the same treatment, he "somehow doubt[ed] that will be the case", a sentiment which would turn out to be correct.
 Even 13 years later, Ikeda still considers DDP his most memorable and completed game. He stressed that despite the support he recieved in-house, should his attempt at "evolution" have turned out to be a failure it would

@@ Line 2: / Line 2: @@
 |bordercolor = #B93F25
 |innerbordercolor = #AF4028
-|title = DoDonPachi 怒首領蜂
+|title = DoDonPachi
 |background = #fce9bc
 |image = Screenshot_DDP_001.png