Skip to content

Commit d04ccb0

Browse files
Update priv_store page (#564)
* Amending priv_store page to describe that it cannot be attacked. * Updated priv_store page to include some edge cases. * Apply suggestions from code review Co-authored-by: matr1x <[email protected]> --------- Co-authored-by: matr1x <[email protected]>
1 parent 68a1c7a commit d04ccb0

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

docs/guides/new_players/priv_store.mdx

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ _- Unknown, ((%Fmarks%.%Qlost_and_found%))_
88

99
((%Cpriv_store%)) is a special user that does not take a user slot, cannot be retired, and cannot run any scripts other than ((accts.balance)) or ((accts.xfer_gc_to)).
1010

11-
It can be accessed by entering ((%Cpriv_store%)) or ((%Cuser priv_store%)) into the CLI.
11+
It can be accessed by entering ((%Cpriv_store%)) or ((%Cuser% %Apriv_store%)) into the CLI.
1212

1313
A ((%Cpriv_store%)) user is named similar to an NPC, and can hold up to ((1B337MGC)).
1414

@@ -18,3 +18,15 @@ You can transfer ((%CGC%)) to your ((%Cpriv_store%)) with ((accts.xfer_gc_to \{
1818
but only when calling it directly in the CLI. Subscripts cannot target ((%Cpriv_store%)).
1919

2020
To target your ((%Cpriv_store%)) in a subscript call, you must enter the actual name of your ((%Cpriv_store%)) user.
21+
22+
## Edge Cases & Notable Behaviours
23+
24+
Attempting to send any amount of ((%CGC%)) to a ((%Cpriv_store%)) that is not associated with your account will always return the following irregardless of the balance of the ((%Cpriv_store%)) user:
25+
26+
> ((%DFailure%))\
27+
> User can't store that much ((%CGC%)). Recipient must init to tier 2.
28+
29+
Attempting to send ((%CGC%)) to your ((%Cpriv_store%)) when it is full will return the following, including when the transfer is subscripted:
30+
31+
> ((%DFailure%))\
32+
> balance would exceed the priv_store limit of 1B337MGC

0 commit comments

Comments
 (0)