.
.
.
.
.
.
.
.
.
.
X
.
.
.
.
.
X
X
.
.
.
.
.
.
X
X
.
.
.
.
.
X
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
m (Move page script moved page BugStop (6) to BugStop (BN6) without leaving a redirect) |
m (→Counterplay) |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
|number=31 | |number=31 | ||
|name=BugStop | |name=BugStop | ||
|fullname=Bug Stop | |||
|series=Bug Stop | |||
|bug= | |||
|compressioncode=AAABRLBAAL | |||
|description=Prevents bugs | |description=Prevents bugs | ||
|colors=Yellow | |colors=Yellow | ||
| Line 28: | Line 32: | ||
Stops every bug in the NaviCust, even when placed out of bounds. Must be placed on the command line to work. It does not remove the requirement that other program parts need to be placed on the command line to work. | Stops every bug in the NaviCust, even when placed out of bounds. Must be placed on the command line to work. It does not remove the requirement that other program parts need to be placed on the command line to work. | ||
{{Navplate NaviCust parts | ==Competitive Overview== | ||
The choice to use Bug Stop has a few influences on the user's strategy: | |||
* The user does not need to include {{Chip|6|Bug Fix}} in their folder. As well as freeing up that space for a different chip, this means there is no pressure to find Bug Fix before the bugs in the user's NaviCust become overly cumbersome. | |||
* On the opposite side, the user cannot ''benefit'' from any bugs. This is most apparent with [[Bugs_(BN6)#Buster_Bug|Buster Bug]], denying the user the opportunity for 10x damage buster shots. Strategies taking advantage of [[Bugs_(BN6)#Emotion_Bug|Emotion Bug]] or [[Bugs_(BN6)#Movement_Bug|Movement Bug]] are also off-limits. {{Chip|6|Static}} cannot have its range increased. | |||
* Like all parts, using Bug Stop has an opportunity cost where the squares and shape of Bug Stop could instead be used for other NaviCust parts. | |||
===Counterplay=== | |||
A user with Bug Stop has no immediate reason to carry Bug Fix as well. This means any bugs they receive in the middle of battle, such as by the {{Chip|6|Moon Blade}}, {{Chip|6|Elec Pulse 3}}, the [[Destroy_Pulse_(BN6)|Destroy Pulse]] program advance, or [[Erase Cross]] can't be fixed. | |||
{{Navplate NaviCust parts (BN6)}} | |||
Latest revision as of 19:35, 25 June 2024
| BugStop | |
|---|---|
| Description | Prevents bugs |
| Full name | Bug Stop |
| Type | Solid |
| Colors | Yellow |
| Compression code | AAABRLBAAL |
Stops every bug in the NaviCust, even when placed out of bounds. Must be placed on the command line to work. It does not remove the requirement that other program parts need to be placed on the command line to work.
Competitive Overview
The choice to use Bug Stop has a few influences on the user's strategy:
- The user does not need to include
BugFix in their folder. As well as freeing up that space for a different chip, this means there is no pressure to find Bug Fix before the bugs in the user's NaviCust become overly cumbersome. - On the opposite side, the user cannot benefit from any bugs. This is most apparent with Buster Bug, denying the user the opportunity for 10x damage buster shots. Strategies taking advantage of Emotion Bug or Movement Bug are also off-limits.
Static cannot have its range increased. - Like all parts, using Bug Stop has an opportunity cost where the squares and shape of Bug Stop could instead be used for other NaviCust parts.
Counterplay
A user with Bug Stop has no immediate reason to carry Bug Fix as well. This means any bugs they receive in the middle of battle, such as by the 
MoonBld, 
ElcPuls3, the Destroy Pulse program advance, or Erase Cross can't be fixed.