Fixed bug with contract generation when player doesn't have a job. Added bladeburner.getActionRepGain() function

doc/source/codingcontracts.rst

@@ -33,6 +33,32 @@ Interacting through Scripts
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
 See :ref:`netscriptcodingcontractapi`.
 
+Submitting Solutions
+^^^^^^^^^^^^^^^^^^^^
+Different contract problem types will require different types of
+solutions. Some may be numbers, others may be strings or arrays.
+If a contract asks for a specific solution format, then
+use that. Otherwise, follow these rules when submitting solutions:
+
+* String-type solutions should not have quotation marks surrounding
+  the string (unless specifically asked for). Only quotation
+  marks that are part of the actual string solution should be included.
+* Array-type solutions should be submitted with each element
+  in the array separated by commas. Brackets are optional. For example,
+  both of the following are valid solution formats::
+
+    1,2,3
+    [1,2,3]
+
+  However, if the solution is a multidimensional array, then
+  all arrays that are not the outer-most array DO require the brackets.
+  For example, an array of arrays can be submitted as one of the following::
+
+    [1,2],[3,4]
+    [[1,2],[3,4]]
+
+* Numeric solutions should be submitted normally, as expected
+
 Rewards
 ^^^^^^^
 There are currently four possible rewards for solving a Coding Contract:
@@ -45,3 +71,8 @@ There are currently four possible rewards for solving a Coding Contract:
 The 'amount' of reward varies based on the difficulty of the problem
 posed by the Coding Contract. There is no way to know what a
 Coding Contract's exact reward will be until it is solved.
+
+Notes
+^^^^^
+
+* The *scp* Terminal command does not work on Coding Contracts