mirror of
https://github.com/bitburner-official/bitburner-src.git
synced 2025-03-07 11:04:36 +01:00
MISC: Stanek UI description corrections (#1161)
Corrected description on charging efficacy against threadcount and time From https://github.com/bitburner-official/bitburner-src/issues/689, description has been corrected to reflect the scaling for highestCharge and numCharge
This commit is contained in:
@ -41,28 +41,28 @@ export function Effect(tpe: FragmentType): string {
|
||||
return "+x% grow() power";
|
||||
}
|
||||
case FragmentType.Hacking: {
|
||||
return "+x% hacking skill";
|
||||
return "+x% hacking experience and skill level";
|
||||
}
|
||||
case FragmentType.Strength: {
|
||||
return "+x% strength skill";
|
||||
return "+x% strength experience and skill level";
|
||||
}
|
||||
case FragmentType.Defense: {
|
||||
return "+x% defense skill";
|
||||
return "+x% defense experience and skill level";
|
||||
}
|
||||
case FragmentType.Dexterity: {
|
||||
return "+x% dexterity skill";
|
||||
return "+x% dexterity experience and skill level";
|
||||
}
|
||||
case FragmentType.Agility: {
|
||||
return "+x% agility skill";
|
||||
return "+x% agility experience and skill level";
|
||||
}
|
||||
case FragmentType.Charisma: {
|
||||
return "+x% charisma skill";
|
||||
return "+x% charisma experience and skill level";
|
||||
}
|
||||
case FragmentType.HacknetMoney: {
|
||||
return "+x% hacknet production";
|
||||
}
|
||||
case FragmentType.HacknetCost: {
|
||||
return "-x% cheaper hacknet cost";
|
||||
return "-x% cheaper hacknet costs";
|
||||
}
|
||||
case FragmentType.Rep: {
|
||||
return "+x% reputation from factions and companies";
|
||||
@ -71,7 +71,7 @@ export function Effect(tpe: FragmentType): string {
|
||||
return "+x% work money";
|
||||
}
|
||||
case FragmentType.Crime: {
|
||||
return "+x% crime money";
|
||||
return "+x% crime money and success chance";
|
||||
}
|
||||
case FragmentType.Bladeburner: {
|
||||
return "+x% all bladeburner stats";
|
||||
|
@ -63,7 +63,7 @@ export function StaneksGiftRoot({ staneksGift }: IProps): React.ReactElement {
|
||||
Booster Fragments, which take up 5 tiles of the grid. There is no shortage of Booster Fragments, and
|
||||
it is virtually impossible to run out of them. While not providing any direct stat increases to their
|
||||
user, Booster Fragments increase the efficacy of adjacent Stat Fragments by 10%, and do not need to be
|
||||
charged.
|
||||
charged. Multiple Booster Fragments can affect the same Stat Fragment.
|
||||
</Typography>
|
||||
<br />
|
||||
|
||||
@ -170,11 +170,11 @@ export function StaneksGiftRoot({ staneksGift }: IProps): React.ReactElement {
|
||||
Stat Fragments are charged using the stanek.chargeFragment(rootX, rootY) NetScript API function. The
|
||||
charging process ordinarily takes 1000ms to complete, but only takes 200ms during bonus time. When the
|
||||
function finishes executing, the fragment's charge levels will be raised by an amount corresponding to
|
||||
the number of threads that were used. Note that it is no more effective to charge a fragment many
|
||||
times with few threads than to charge few times with many threads, so there is no need to distribute
|
||||
charging jobs across multiple scripts. As a Stat Fragment's charge level is increased, its bonuses
|
||||
will increase, but there will be diminishing returns. As such, it is generally most efficient to
|
||||
charge all of the placed fragments equally. The charge level of a fragment will not decrease over
|
||||
the number of threads that were used. Note that it is generally more effective to charge a fragment a
|
||||
few times with many threads than to charge it many times with few threads, so there is a benefit to
|
||||
combining charging jobs into fewer scripts. As a Stat Fragment's charge level is increased, its
|
||||
bonuses will increase, but there will be diminishing returns. As such, it is generally most efficient
|
||||
to charge all of the placed fragments equally. The charge level of a fragment will not decrease over
|
||||
time, but it will be reset to 0 upon removing it from the board or installing augmentations.
|
||||
</Typography>
|
||||
</>,
|
||||
|
Reference in New Issue
Block a user