mirror of
https://github.com/bitburner-official/bitburner-src.git
synced 2026-04-21 08:42:53 +02:00
Michael Taylor
dcd2f33f7c
* Update api-documentor and api-extractor. #1566 follow-up.
I have verified that the HTML/markdown table generation bug in
[#4878](https://github.com/microsoft/rushstack/issues/4878) in rushstack
for api-documentor has been fixed as per rushstack#5256. The testcase
[repro](https://github.com/catloversg/api-documenter-bug-pr-4578) now
produces the correct expected output.
I have confirmed that the generated output in bitburner from
`npm run doc` now generated HTML tables, and correctly inserts
a blank line between the </table> and the follow line (e.g. Returns).
Stylisticly it could use some whitespace, but it is correctly rendered.
This commit is only the updated packages, not the updated generated
documentation. I assume that is automatically generated by the GitHub
workflow.
* Follow up to 5f732a6f35, include `npm run doc` changed docs.
* Add missing license info
* Fix React warning
---------
Co-authored-by: CatLover <152669316+catloversg@users.noreply.github.com>
109 lines
1.6 KiB
Markdown
109 lines
1.6 KiB
Markdown
<!-- Do not edit this file. It is automatically generated by API Documenter. -->
|
|
|
|
[Home](./index.md) > [bitburner](./bitburner.md) > [CodingContract](./bitburner.codingcontract.md) > [attempt](./bitburner.codingcontract.attempt.md)
|
|
|
|
## CodingContract.attempt() method
|
|
|
|
Attempts a coding contract, returning a reward string on success or empty string on failure.
|
|
|
|
**Signature:**
|
|
|
|
```typescript
|
|
attempt(answer: any, filename: string, host?: string): string;
|
|
```
|
|
|
|
## Parameters
|
|
|
|
<table><thead><tr><th>
|
|
|
|
Parameter
|
|
|
|
|
|
</th><th>
|
|
|
|
Type
|
|
|
|
|
|
</th><th>
|
|
|
|
Description
|
|
|
|
|
|
</th></tr></thead>
|
|
<tbody><tr><td>
|
|
|
|
answer
|
|
|
|
|
|
</td><td>
|
|
|
|
any
|
|
|
|
|
|
</td><td>
|
|
|
|
Attempted solution for the contract. This can be a string formatted like submitting manually, or the answer in the format of the specific contract type.
|
|
|
|
|
|
</td></tr>
|
|
<tr><td>
|
|
|
|
filename
|
|
|
|
|
|
</td><td>
|
|
|
|
string
|
|
|
|
|
|
</td><td>
|
|
|
|
Filename of the contract.
|
|
|
|
|
|
</td></tr>
|
|
<tr><td>
|
|
|
|
host
|
|
|
|
|
|
</td><td>
|
|
|
|
string
|
|
|
|
|
|
</td><td>
|
|
|
|
_(Optional)_ Hostname/IP of the server containing the contract. Optional. Defaults to current server if not provided.
|
|
|
|
|
|
</td></tr>
|
|
</tbody></table>
|
|
|
|
**Returns:**
|
|
|
|
string
|
|
|
|
A reward description string on success, or an empty string on failure.
|
|
|
|
## Remarks
|
|
|
|
RAM cost: 10 GB
|
|
|
|
Attempts to solve the Coding Contract with the provided solution.
|
|
|
|
## Example
|
|
|
|
|
|
```js
|
|
const reward = ns.codingcontract.attempt("[solution, as, a, string]", filename, hostname);
|
|
// or
|
|
const reward = ns.codingcontract.attempt(["answer", "as", "an", "array"], filename, hostname);
|
|
if (reward) {
|
|
ns.tprint(`Contract solved successfully! Reward: ${reward}`);
|
|
} else {
|
|
ns.tprint("Failed to solve contract.");
|
|
}
|
|
```
|
|
|