YukkuriC / YukkuriC/bitburner-codebase

更新2.0,旧API全爆了,有空想起来了更一波罢

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

V2_0_0_API_BREAK.txt

This file contains the list of potential API break. A pattern was used to look through all your files and note the spots where you might have a problem. Not everything here is broken.
/ns.scp/g
scp arguments were switch, it is now scp(files, destination, optionally_source). If you were using 2 argument (not 3) this doesn't affect you.

a/autoFarm.js
	Line 60 await ns.scp(FILES, host)
old/deployFarm.js
	Line 31 await ns.scp(file, host)

/ns.installAugmentations/g
ns.installAugmentations was moved to ns.singularity.installAugmentations

s/break.js
	Line 36 await ns.installAugmentations('/s/break.js')

/hacking/g
The work system is completely reworked and ns.getPlayer().hacking no longer exists. This data is likely available inside ns.getPlayer().currentWork, skills, exp, or hp

meta/rise.js
	Line 6 const skills = ['hacking', 'strength', 'defense', 'dexterity', 'agility', 'charisma']
s/sleeve.js
	Line 7 'hacking', 'strength', 'defense', 'dexterity',

/strength/g
The work system is completely reworked and ns.getPlayer().strength no longer exists. This data is likely available inside ns.getPlayer().currentWork, skills, exp, or hp

meta/rise.js
	Line 6 const skills = ['hacking', 'strength', 'defense', 'dexterity', 'agility', 'charisma']
s/sleeve.js
	Line 7 'hacking', 'strength', 'defense', 'dexterity',

/defense/g
The work system is completely reworked and ns.getPlayer().defense no longer exists. This data is likely available inside ns.getPlayer().currentWork, skills, exp, or hp

meta/rise.js
	Line 6 const skills = ['hacking', 'strength', 'defense', 'dexterity', 'agility', 'charisma']
s/sleeve.js
	Line 7 'hacking', 'strength', 'defense', 'dexterity',

/dexterity/g
The work system is completely reworked and ns.getPlayer().dexterity no longer exists. This data is likely available inside ns.getPlayer().currentWork, skills, exp, or hp

meta/rise.js
	Line 6 const skills = ['hacking', 'strength', 'defense', 'dexterity', 'agility', 'charisma']
s/sleeve.js
	Line 7 'hacking', 'strength', 'defense', 'dexterity',

/agility/g
The work system is completely reworked and ns.getPlayer().agility no longer exists. This data is likely available inside ns.getPlayer().currentWork, skills, exp, or hp

meta/rise.js
	Line 6 const skills = ['hacking', 'strength', 'defense', 'dexterity', 'agility', 'charisma']
s/sleeve.js
	Line 8 'agility', 'charisma',

/charisma/g
The work system is completely reworked and ns.getPlayer().charisma no longer exists. This data is likely available inside ns.getPlayer().currentWork, skills, exp, or hp

meta/rise.js
	Line 6 const skills = ['hacking', 'strength', 'defense', 'dexterity', 'agility', 'charisma']
s/sleeve.js
	Line 8 'agility', 'charisma',

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with V2_0_0_API_BREAK.txt and inspect the listed locations in a/autoFarm.js, old/deployFarm.js, s/break.js, meta/rise.js, and s/sleeve.js. Compare each use with the API changes described in the issue, then run the affected scripts to verify that the old calls and player-stat accesses no longer break.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.