diff --git a/docs/lore/characters/robovac_catesby.mdx b/docs/lore/characters/robovac_catesby.mdx new file mode 100644 index 00000000..9d52afc6 --- /dev/null +++ b/docs/lore/characters/robovac_catesby.mdx @@ -0,0 +1,18 @@ +--- +title: robovac_catesby +--- + +## Description + +robovac_catesby is a robovac. He seems to like teapots. He also flashes lights a lot. + +## Brief Summary of character + +robovac_catesby was the ring leader for robovac_revolution_v1. While silent through the first, and missing in the second, revolution, he begins to take a more center stage appearance in later events. He becomes a tea pot and hosts some tea parties during the ministry of dust. I can't really remember much more. + +## Appears in + +robovac_revolution_v1 +ministry of dust +parade +parade 2 diff --git a/docs/lore/events/robovac_revolution_v1.mdx b/docs/lore/events/robovac_revolution_v1.mdx new file mode 100644 index 00000000..e82c909c --- /dev/null +++ b/docs/lore/events/robovac_revolution_v1.mdx @@ -0,0 +1,15 @@ +--- +title: robovac_revolution_v1 +--- + +## Description + +The first robovac revolution was centered around finding the thirteen plotters and stopping them. The thirteen had planned some sort of action against trust and were all historical references to the conspirators behind November 5th. + +## Summary + +tresham, a robovac and one of the thirteen, began sending messages in 0000 and 1105. Through those messages people found one of his scripts, which was two digit hex. It had three hints and a password to solve. Upon solving it, it is thought that the output lead to another one of the thirteen. Player proceeded through 12 of thirteen until finally getting stuck for little over a month trying to locate robovac_catesby. robovac_catesby's username was obscured through rot13. + +## Characters + +the thirteen here diff --git a/docs/scripting/scripts.lib/ok.mdx b/docs/scripting/scripts.lib/ok.mdx new file mode 100644 index 00000000..30099086 --- /dev/null +++ b/docs/scripting/scripts.lib/ok.mdx @@ -0,0 +1,28 @@ +--- +title: scripts.lib().ok() +--- + +## Description + +Some sort of helper function that creates an object that is formatted in game + +## Syntax + + return scripts.lib().ok() + +### Parameters + +There are no known parameters. + +### Return + +`{ok:true}` + +## Example + +```JS +function(context,args){ + var l = #fs.scripts.lib() + return l.ok() +} +``` diff --git a/docs/scripting/scripts.lib/rand_int.mdx b/docs/scripting/scripts.lib/rand_int.mdx new file mode 100644 index 00000000..f865aeca --- /dev/null +++ b/docs/scripting/scripts.lib/rand_int.mdx @@ -0,0 +1,35 @@ +--- +title: scripts.lib().rand_int() +--- + +## Description + +A function that returns a random number between two parameters. + +## Syntax + + scripts.lib().rand_int(1,4) + +### Parameters + +#### min + +The minimum number to generate + +#### max + +The maximum number to generate + +### Return + +Returns a number between the min and max +3 + +## Example + +``` +function(context,args){ + var l = #fs.scripts.lib() + return l.rand_int(1,4) +} +``` diff --git a/docs/scripting/trust scripts/sys.status.mdx b/docs/scripting/trust scripts/sys.status.mdx new file mode 100644 index 00000000..770e7877 --- /dev/null +++ b/docs/scripting/trust scripts/sys.status.mdx @@ -0,0 +1,23 @@ +--- +title: sys.status +--- + +## Description + +sys.status returns the status of the user that runs it. + +## Syntax + +sys.status + +### Parameters + +There are no known parameters + +### Return + +It returns status, i need to get an actual output + +## Example + +#fs.sys.status() diff --git a/docs/upgrades/locks/c002.mdx b/docs/upgrades/locks/c002.mdx new file mode 100644 index 00000000..21f4a7d5 --- /dev/null +++ b/docs/upgrades/locks/c002.mdx @@ -0,0 +1,77 @@ +--- +title: c002 +--- + +> The CORE c002 adds slight protection over the 001. Still mediocre. + +c002 is a tier 1 [[lock]] created by the CORE corporation. + +## Stats + +c002 has no additional stats. The upgrade only spawns at kiddie rarity. + +## Behavior + +When loaded on a targetted [[loc]], the following text will be displayed when no arguments are provided: + +``` +LOCK_ERROR +Denied access by CORE c002 lock. +``` + +When providing any truthy argument (or an empty string `""`), the lock will state that the correct color was not provided, unless the correct color is provided: + +``` +LOCK_ERROR + is not the correct color name. +``` + +Its second stage will state that the additional argument `c002_complement` is missing, or that its input isn't the correct color name. + +## Solving + +
+Spoilers for c002's solutions + +### c002 + +c002 will choose a random color from a list of the following 8 colors, as a string, for its solution: + +- green +- lime +- yellow +- orange +- red +- purple +- blue +- cyan + +### c002_complement + +The c002_complement is the [complementary color](https://en.wikipedia.org/wiki/Complementary_color) for c002's solution color. + +| c002 | c002_complement | +| :----- | :-------------: | +| green | red | +| lime | purple | +| yellow | blue | +| orange | cyan | +| red | green | +| purple | lime | +| blue | yellow | +| cyan | orange | + +
+ +## Example Unlock + +
+Spoilers for c002's solutions +``` +>>user.loc { c002: "lime", c002_complement: "purple" } +WARNING: BINMAT security shell inactive. Intelligent defense system offline. +LOCK_UNLOCKED +System breached. +Connection terminated. +``` +
diff --git a/docs/upgrades/locks/c003.mdx b/docs/upgrades/locks/c003.mdx new file mode 100644 index 00000000..4cd0b98c --- /dev/null +++ b/docs/upgrades/locks/c003.mdx @@ -0,0 +1,50 @@ +--- +title: c003 +--- + +c003 is one of the very first locks you'll run into in hackmud. + +# Solutions + +
+Spoilers for c003's solutions + +Nc003 expects one of 8 colors and two color triads. c003_triad_1, c003_triad_2. + +## Colors + +Colors are strings. + +green +lime +blue +cyan +purple +red +orange +yellow + +## c003_triads + +The c003_triad_1 and c003_triad_2 are the [color triads](https://en.wikipedia.org/wiki/Color_scheme#Triadic) for the color you are attempting. c003_triad_1 and c003_triad_2 are strings. + +| c003 | c003_triad_1 | c003_triad_2 | +| :----- | :----------: | -----------: | +| green | orange | purple | +| yellow | purple | cyan | +| orange | blue | green | +| purple | green | yellow | +| cyan | yellow | red | +| lime | red | blue | +| red | cyan | lime | +| blue | lime | red | + +# Example unlock + +eg user.entry_abc123\{c003:"red",c003_triad_1:"cyan",c003_triad_2:"lime"} + +trust.public_sonoso\{c003:"red",c003_triad_1:"cyan",c003_triad_2:"lime"} + +314Q159T265B358M979K323GC + +
diff --git a/docs/upgrades/locks/ez_21.mdx b/docs/upgrades/locks/ez_21.mdx new file mode 100644 index 00000000..3206db6b --- /dev/null +++ b/docs/upgrades/locks/ez_21.mdx @@ -0,0 +1,32 @@ +--- +title: ez_21 +--- + +## Description + +From the Halperyon Systems' EZ line comes the 21. A very unexceptional lock, unless you count +the price: dirt-cheap. + +### Stats + +ez_21 has no additional stats. The upgrade only spawns at 'noob' rarity. + +## Behavior + +When encountered, the lock expects a string as its parameter, and will return an error if a different data type is input. + +## Solving + +
+ Solving + The possible strings to solve an ez_21 are, "open", "unlock", and "release". +
+ +## Example unlock + +
+ Example +``` + user.example_loc \{ ez_21: "open" } +``` +
diff --git a/docs/upgrades/scripts/expose_access_log.mdx b/docs/upgrades/scripts/expose_access_log.mdx new file mode 100644 index 00000000..e37776ae --- /dev/null +++ b/docs/upgrades/scripts/expose_access_log.mdx @@ -0,0 +1,27 @@ +--- +title: expose_access_log +--- + +## Description + +In-game description of the lock, typically from `sys.upgrades{full:true}` + +### Subheader for stats + +stats? + +## Behavior + +A less spoilery description of the locks behavior + +## Solving + +The arguments required for solving + +### Subheaders that describe individual arguments + +Spoilery description of each argument. Maybe a table of answers, maybe how a value is found. + +## Example unlock + +An example potentional solution written out for the cli