PD Crew Wiki - User contributions [en-gb]

Ribbons

2023-07-07T12:42:03Z

Jmabb: struck again by missing the pesky god code :(

Start by getting to the “Ribbon” tab of the crew interface. The default screen you land on is the “View Ribbon” page. This is
discussed in detail in ''View Ribbon'' below.

===Ribbon FAQ's===
* I’m a new artisan – where are my starting ribbons?

Brand new characters with the Artisan skill get three starting ribbons. Existing characters who have just learned the Artisan skill do not: they get to craft their first items during the next downtime.
* I’m a new artisan – why are my ribbon expiry dates different?

Brand new artisans get one ribbon that lasts for three seasons (events), one that lasts for two seasons, and one that lasts for one season.

===New ribbon===

Don’t worry about this unless you already know what you’re doing!

===View ribbon===

'''TODO'''
* what information it’s okay to give out without any special abilities at all
* what information it is NOT okay to give out without special abilities
* what information it’s okay to give out given insight (take liao?)
* when it’s okay to tell people there’s more information they can obtain if they perform rituals
* how they can find out which rituals they have to perform
* how to register rituals more generally in this context in a step-by-step &c

===Bonding to items===

'''TODO'''

===Search ribbon===

'''TODO'''

===Item data===

'''TODO'''
[[Category:GOD manual]]

Ribbons

2023-07-07T12:41:20Z

Jmabb: ribbon page- lots of to-do's!

Religion

2023-07-07T12:36:53Z

Jmabb:

The Empire runs on three main strands: magic, religion, and politics. This chapter of the manual deals with GOD’s interactions with religion. Because we only care about recording religious ceremonies (and more pertinently, because MattP), the relevant tab in the crew interface is labelled “Ceremony” instead of “Religion”.

For the processes in this section, start by getting to the “Ceremony” tab of the crew interface.

===New Ceremony===

====Anointing====

Don’t actually record anointing into the system. Just hand the priest as many of the virtue/anointing cards as they’re willing to take away.

====Consecration====
<box>
1. In the “Lead Priest” section of the page:

(a) In the box labelled “CID”, enter the lead priest’s PID.

(b) Press Tab or Enter.

(c) Confirm the name of the caster’s character.

2. In the “Ceremony” section of the page:

(a) From the “Skill” drop-down menu, select “Consecration”.

(b) Ask the player if they are performing the ceremony alone.
* If yes, select “Lone Priest” from the “Type” drop-down menu.
* If no, select “Virtue” from the “Type” drop-down menu.

3. Ignore the “Date” section of the page, or escalate to a head of department or referee if there’s some reason you think you shouldn’t.

4. If multiple priests are involved in the ceremony, advance to the Participants tab.
* Add additional casters either by entering their PIDs into the CID box and pressing Tab or Enter.

5. Advance to the Targets tab.

6. In the “Consecration Options” section of the page, select a radio button for either “Consecration” or “Remove Consecration”.

7. In the “Enter Target Location” section of the page, provide a description of the location sufficient for a ref to positively identify the intended location in the field.

8. Advance to the Strength tab.

9. For a lone priest performing a Strength 1 ritual, take 1 liao from the priest (if it’s already torn up, or they tell you they already tore it up and disposed of it during roleplay, that’s fine).
* Note: Occasionally, it’s more complicated than this. See 18.1.7 Calculating complicated liao costs for details, or grab a more experienced crew member.

10. Get an A5 area effect lammy from the refs.

'''TODO''' add details.
</box>

====Dedication====
<box>
1. In the “Lead Priest” section of the page:

(a) In the box labelled “CID”, enter the lead priest’s PID.

(b) Press Tab or Enter.

(c) Confirm the name of the caster’s character.

2. In the “Ceremony” section of the page:

(a) From the “Skill” drop-down menu, select “Dedication”.

(b) Ask the player if they are performing the ceremony alone.
* If yes, select “Lone Priest” from the “Type” drop-down menu.
* If no, select “Virtue” from the “Type” drop-down menu.

3. Ignore the “Date” section of the page, or escalate to a head of department or referee if there’s some reason you think you shouldn’t.

4. If multiple priests are involved in the ceremony, advance to the Participants tab.
* Add additional casters either by entering their PIDs into the CID box and pressing Tab or Enter.

5. Advance to the Targets tab.

6. In the “Dedication Options” section of the page, select a radio button for either “Dedication” or “Remove Dedication”.

7. In the “Add Target Character” section of the page:

(a) In the box labelled “CID”, enter the target character’s PID.

(b) Press Tab or Enter.

(c) Confirm the name of the target’s character.

8. Advance to the Strength tab.

9. For a lone priest performing a Strength 1 ritual, take 1 liao from the priest (if it’s already torn up, or they tell you they already tore it up and disposed of it during roleplay, that’s fine).
* '''''Note''': Occasionally, it’s more complicated than this''. See ''Calculating complicated liao costs'' below for details, or grab a more experienced crew member.

</box>

====Hallow====
<box>
1. In the “Lead Priest” section of the page:

(a) In the box labelled “CID”, enter the lead priest’s PID.

(b) Press Tab or Enter.

(c) Confirm the name of the caster’s character.

2. In the “Ceremony” section of the page:

(a) From the “Skill” drop-down menu, select “Hallow”.

(b) Ask the player if they are performing the ceremony alone.
* If yes, select “Lone Priest” from the “Type” drop-down menu.
* If no, select “Virtue” from the “Type” drop-down menu.

3. Ignore the “Date” section of the page, or escalate to a head of department or referee if there’s some reason you think you shouldn’t.

4. If multiple priests are involved in the ceremony, advance to the Participants tab.

* Add additional casters either by entering their PIDs into the CID box and pressing Tab or Enter.

5. Advance to the Targets tab.

6. In the “Hallowing Options” section of the page:

(a) Select a radio button for either “Create Aura” or “Remove Aura”.

(b) If creating an aura, ask the lead priest which aura they would like to create, and select the appropriate option from the drop-down menu.

7. In the “Ribbon Options” section of the page:

(a) Select a radio button for either “Ribboned Item” or “Non Ribboned Item”.

(b) Enter a name in the “Item Name” box.
* The name should not be comedic, or obviously taken from an existing work of fiction. If in doubt, ask a head of department.

8. In the “Add Target Ribbon” section of the page:

(a) If the target item already has a ribbon, enter the Ribbon Id in the box.

(b) Press Tab or Enter.

(c) Confirm that the details on the ribbon in front of you match the details on screen.

9. Advance to the Strength tab.

10. For a lone priest performing a Strength 1 ritual, take 1 liao from the priest (if it’s already torn up, or they tell you they already tore it up and disposed of it during roleplay, that’s fine).
* Note: Occasionally, it’s more complicated than this. See ''Calculating complicated liao costs'' below for details, or grab a more experienced crew member.
</box>

====Insight====
Insight should not be processed as a ceremony. Instead:

1. Confirm the character who wishes to cast Insight has the necessary skill. (Look up the character: see '''REF GOES HERE.''')

(a) If they wish to perform Insight on a character, see '''REF GOES HERE.'''

(b) If they wish to perform Insight on an item, see '''REF GOES HERE.'''

''I don't understand the ref bits and also don't know what else to put into that bit so leaving it, '''TODO'''- make clearer (???) - Jess''

====Testimony====
<box>
1. In the “Lead Priest” section of the page:

(a) In the box labelled “CID”, enter the lead priest’s PID.

(b) Press Tab or Enter.

(c) Confirm the name of the caster’s character.

2. In the “Ceremony” section of the page:

(a) From the “Skill” drop-down menu, select “Testimony”.

(b) Ask the player if they are performing the ceremony alone.
* If yes, select “Lone Priest” from the “Type” drop-down menu.
* If no, select “Virtue” from the “Type” drop-down menu.

3. Ignore the “Date” section of the page, or escalate to a head of department or referee if there’s some reason you think you shouldn’t.

4. If multiple priests are involved in the ceremony, advance to the Participants tab.
* Add additional casters either by entering their PIDs into the CID box and pressing Tab or Enter.

5. Advance to the Targets tab.

6. In the “Testimony Options” section of the page:

(a) Select a radio button for either “Create Testimony” or “Remove All Testimonies”.

(b) If creating a testimony, enter it into the text box.
* A testimony should consist of at most two words, one adjective and one noun.
* Offer the priest the opportunity to confirm they’re happy with spelling and capitalisation.

7. In the “Add Target Character” section of the page:

(a) In the box labelled “CID”, enter the target character’s PID.

(b) Press Tab or Enter

(c) Confirm the name of the target character.

8. Advance to the Strength tab.

9. For a lone priest performing a Strength 1 ritual, take 1 liao from the priest (if it’s already torn up, or they tell you they already tore it up and disposed of it during roleplay, that’s fine).
* '''Note:''' Occasionally, it’s more complicated than this. '''See Calculating complicated liao costs''' below for details, or grab a more experienced crew member.

10. Click the button labelled “Process” on the right-hand side of the “Ceremony Details” section
</box>

====Calculating complicated liao costs====
All ceremonies cost liao to perform. The vast majority of ceremonies are performed by a lone priest as level 1 ceremonies, and cost 1 liao to perform. Things are generally more complicated when ceremony is being performed at a level higher than strength 1, for example because:
* there’s more than one priest involved, or
* magic items, potions, or ritual enchantments that allow a priest to use additional liao are being used.

'''The players will generally let you know this is happening!'''

In the “Strength” tab, the “Strength Achieved” line tells you the automatically calculated maximum level of ceremony that can be performed, taking into account only the number of priests. The “Strength Achieved” will be equal to the number of priests. ''(There are columns for items and potions, but you can’t tell the calculator about these at the moment.)''
<box>
In the “Ceremony Details” section of the “Strength” tab:

1. Enter the level at which the players want to perform the ceremony in the “Strength” field.

2. Take some liao off the priests.

(a) If the number you have entered in the “Strength” field is less than or equal to the number after “Strength Achieved”, and there are no other effects, take that number of liao and leave the “Notes” field empty.

(b) If the players are using magic items, potions, or enchantments to affect how much liao the ceremony costs, enter the details of what they’re using, what effect it has, and how much liao you actually take off them in the “Notes” field.
</box>

===Search ceremony===
'''TODO'''
[[Category:GOD manual]]

Religion

2023-07-07T12:36:30Z

Jmabb:

Religion

2023-07-07T12:33:27Z

Jmabb:

The Empire runs on three main strands: magic, religion, and politics. This chapter of the manual deals with GOD’s interactions with religion. Because we only care about recording religious ceremonies (and more pertinently, because MattP), the relevant tab in the crew interface is labelled “Ceremony” instead of “Religion”.

For the processes in this section, start by getting to the “Ceremony” tab of the crew interface.

===New Ceremony===

====Anointing====

Don’t actually record anointing into the system. Just hand the priest as many of the virtue/anointing cards as they’re willing to take away.

====Consecration====
<box>
1. In the “Lead Priest” section of the page:

(a) In the box labelled “CID”, enter the lead priest’s PID.

(b) Press Tab or Enter.

(c) Confirm the name of the caster’s character.

2. In the “Ceremony” section of the page:

(a) From the “Skill” drop-down menu, select “Consecration”.

(b) Ask the player if they are performing the ceremony alone.
* If yes, select “Lone Priest” from the “Type” drop-down menu.
* If no, select “Virtue” from the “Type” drop-down menu.

3. Ignore the “Date” section of the page, or escalate to a head of department or referee if there’s some reason you think you shouldn’t.

4. If multiple priests are involved in the ceremony, advance to the Participants tab.
* Add additional casters either by entering their PIDs into the CID box and pressing Tab or Enter.

5. Advance to the Targets tab.

6. In the “Consecration Options” section of the page, select a radio button for either “Consecration” or “Remove Consecration”.

7. In the “Enter Target Location” section of the page, provide a description of the location sufficient for a ref to positively identify the intended location in the field.

8. Advance to the Strength tab.

9. For a lone priest performing a Strength 1 ritual, take 1 liao from the priest (if it’s already torn up, or they tell you they already tore it up and disposed of it during roleplay, that’s fine).
* Note: Occasionally, it’s more complicated than this. See 18.1.7 Calculating complicated liao costs for details, or grab a more experienced crew member.

10. Get an A5 area effect lammy from the refs.

'''TODO''' add details.
</box>

====Dedication====
<box>
1. In the “Lead Priest” section of the page:

(a) In the box labelled “CID”, enter the lead priest’s PID.

(b) Press Tab or Enter.

(c) Confirm the name of the caster’s character.

2. In the “Ceremony” section of the page:

(a) From the “Skill” drop-down menu, select “Dedication”.

(b) Ask the player if they are performing the ceremony alone.
* If yes, select “Lone Priest” from the “Type” drop-down menu.
* If no, select “Virtue” from the “Type” drop-down menu.

3. Ignore the “Date” section of the page, or escalate to a head of department or referee if there’s some reason you think you shouldn’t.

4. If multiple priests are involved in the ceremony, advance to the Participants tab.
* Add additional casters either by entering their PIDs into the CID box and pressing Tab or Enter.

5. Advance to the Targets tab.

6. In the “Dedication Options” section of the page, select a radio button for either “Dedication” or “Remove Dedication”.

7. In the “Add Target Character” section of the page:

(a) In the box labelled “CID”, enter the target character’s PID.

(b) Press Tab or Enter.

(c) Confirm the name of the target’s character.

8. Advance to the Strength tab.

9. For a lone priest performing a Strength 1 ritual, take 1 liao from the priest (if it’s already torn up, or they tell you they already tore it up and disposed of it during roleplay, that’s fine).
* '''''Note''': Occasionally, it’s more complicated than this''. See ''Calculating complicated liao costs'' below for details, or grab a more experienced crew member.

</box>

====Hallow====
<box>
1. In the “Lead Priest” section of the page:

(a) In the box labelled “CID”, enter the lead priest’s PID.

(b) Press Tab or Enter.

(c) Confirm the name of the caster’s character.

2. In the “Ceremony” section of the page:

(a) From the “Skill” drop-down menu, select “Hallow”.

(b) Ask the player if they are performing the ceremony alone.
* If yes, select “Lone Priest” from the “Type” drop-down menu.
* If no, select “Virtue” from the “Type” drop-down menu.

3. Ignore the “Date” section of the page, or escalate to a head of department or referee if there’s some reason you think you shouldn’t.

4. If multiple priests are involved in the ceremony, advance to the Participants tab.

* Add additional casters either by entering their PIDs into the CID box and pressing Tab or Enter.

5. Advance to the Targets tab.

6. In the “Hallowing Options” section of the page:

(a) Select a radio button for either “Create Aura” or “Remove Aura”.

(b) If creating an aura, ask the lead priest which aura they would like to create, and select the appropriate option from the drop-down menu.

7. In the “Ribbon Options” section of the page:

(a) Select a radio button for either “Ribboned Item” or “Non Ribboned Item”.

(b) Enter a name in the “Item Name” box.
* The name should not be comedic, or obviously taken from an existing work of fiction. If in doubt, ask a head of department.

8. In the “Add Target Ribbon” section of the page:

(a) If the target item already has a ribbon, enter the Ribbon Id in the box.

(b) Press Tab or Enter.

(c) Confirm that the details on the ribbon in front of you match the details on screen.

9. Advance to the Strength tab.

10. For a lone priest performing a Strength 1 ritual, take 1 liao from the priest (if it’s already torn up, or they tell you they already tore it up and disposed of it during roleplay, that’s fine).
* Note: Occasionally, it’s more complicated than this. See ''Calculating complicated liao costs'' below for details, or grab a more experienced crew member.
</box>

====Insight====
Insight should not be processed as a ceremony. Instead:

1. Confirm the character who wishes to cast Insight has the necessary skill. (Look up the character: see '''REF GOES HERE.''')

(a) If they wish to perform Insight on a character, see '''REF GOES HERE.'''

(b) If they wish to perform Insight on an item, see '''REF GOES HERE.'''

''I don't understand the ref bits and also don't know what else to put into that bit so leaving it, '''TODO'''- make clearer (???) - Jess''

====Testimony====
<box>
1. In the “Lead Priest” section of the page:

(a) In the box labelled “CID”, enter the lead priest’s PID.

(b) Press Tab or Enter.

(c) Confirm the name of the caster’s character.

2. In the “Ceremony” section of the page:

(a) From the “Skill” drop-down menu, select “Testimony”.

(b) Ask the player if they are performing the ceremony alone.
* If yes, select “Lone Priest” from the “Type” drop-down menu.
* If no, select “Virtue” from the “Type” drop-down menu.

3. Ignore the “Date” section of the page, or escalate to a head of department or referee if there’s some reason you think you shouldn’t.

4. If multiple priests are involved in the ceremony, advance to the Participants tab.
* Add additional casters either by entering their PIDs into the CID box and pressing Tab or Enter.

5. Advance to the Targets tab.

6. In the “Testimony Options” section of the page:

(a) Select a radio button for either “Create Testimony” or “Remove All Testimonies”.

(b) If creating a testimony, enter it into the text box.
* A testimony should consist of at most two words, one adjective and one noun.
* Offer the priest the opportunity to confirm they’re happy with spelling and capitalisation.

7. In the “Add Target Character” section of the page:

(a) In the box labelled “CID”, enter the target character’s PID.

(b) Press Tab or Enter

(c) Confirm the name of the target character.

8. Advance to the Strength tab.

9. For a lone priest performing a Strength 1 ritual, take 1 liao from the priest (if it’s already torn up, or they tell you they already tore it up and disposed of it during roleplay, that’s fine).
* Note: Occasionally, it’s more complicated than this. See ''Calculating complicated liao costs'' below for details, or grab a more experienced crew member.

10. Click the button labelled “Process” on the right-hand side of the “Ceremony Details” section
</box>

====Calculating complicated liao costs====
All ceremonies cost liao to perform. The vast majority of ceremonies are performed by a lone priest as level 1 ceremonies, and cost 1 liao to perform. Things are generally more complicated when ceremony is being performed at a level higher than strength 1, for example because:
* there’s more than one priest involved, or
* magic items, potions, or ritual enchantments that allow a priest to use additional liao are being used.

'''The players will generally let you know this is happening!'''

In the “Strength” tab, the “Strength Achieved” line tells you the automatically calculated maximum level of ceremony that can be performed, taking into account only the number of priests. The “Strength Achieved” will be equal to the number of priests. ''(There are columns for items and potions, but you can’t tell the calculator about these at the moment.)''
<box>
In the “Ceremony Details” section of the “Strength” tab:

1. Enter the level at which the players want to perform the ceremony in the “Strength” field.

2. Take some liao off the priests.

(a) If the number you have entered in the “Strength” field is less than or equal to the number after “Strength Achieved”, and there are no other effects, take that number of liao and leave the “Notes” field empty.

(b) If the players are using magic items, potions, or enchantments to affect how much liao the ceremony costs, enter the details of what they’re using, what effect it has, and how much liao you actually take off them in the “Notes” field.
</box>

===Search ceremony===
'''TODO'''

Magic

2023-07-07T12:12:38Z

Jmabb:

The Empire runs on three main strands: magic, religion, and politics. This chapter of the manual deals with GOD’s interactions with magic.

If you go to the “Magic” tab of the crew interface, you will land on the “New Ritual” page, which is discussed in detail in ''New Ritual'' below.

'''TODO:''' Notes on how / when players can change rituals

===Spells===
Spells are “small” magics. Every character with the Magician skill is able to cast some spells, and some magicians spend XP to be able to cast additional spells. Unlike rituals, we don’t record every spell that gets cast. Players cast a lot of spells over the course of an event, and it’s just not worth the effort. However, not needing to record the casting of a spell doesn’t mean we don’t need to do anything with them at all.

In general, casting a spell will cost “personal mana”. Every mage gets a supply of personal mana for free, and we don’t track usage of personal mana in the system. Occasionally characters will run out of personal mana and need to use crystallised mana (i.e. mana cards); you only need to worry about this if you have a mage who seems to be casting at least four spells in quick succession.

====Detect magic====
Detect magic is nominally a single spell, but from our perspective it’s really six different spells in one. Each time someone casts any of these variants, it will cost them one mana (personal or crystallised), so someone casting the full set of spells that can target a magic item (Identify Magical Item, Divination and Discern Enchantment) will be spending three mana.

It’s easy for a character to run out of personal mana if they’re doing this sort of thing, so you should check how someone is paying the mana if they’re casting more than four spells at once.

=====Identify magic item=====
If someone says they want to cast “Detect Magic” without any further qualification, they almost always actually mean “Identify Magical Item”. This is normally the first step for any character who has found a ribboned item, since the ribbon itself is likely to say nothing more informative than “Weapon”.

Players will sometimes ask to “identify this ribbon” or similar. There’s a subtle but important distinction here: their character is casting the spell to identify the item, and in character, the ribbon does not exist. The ribbon is there to allow us to track that the physrep it is attached to is not, for example, a common-or-garden sword but a magical sword with special abilities. Their character is instead identifying the magical item that, out of character, the ribbon is attached to.
<box>
1. Get the player to confirm they’re a mage. You can take their word for this. If they’re not a mage, they can’t cast the spell.

2. Get the player to give you the ribbon ID for the item they want to identify. Unless they have a very good reason, they should be able to show you the ribbon itself. Occasionally someone will try to cast this on an item that doesn’t have a ribbon, in which case the result is simple: “this is not a magical item”.

3. Confirm the ribbon is attached to a reasonable physrep, unless they have a good excuse such as the physrep being heavy armour they don’t want to carry across the field. There’s a fair degree of latitude here, but we do expect players to make at least a passable effort to have an appropriate physrep for the item. If it’s a sword they’ve looted on the battlefield, the best they might be able to do is a dagger or a mace or a hessian sack (preferably with “swag” written on the side…), all of which would be fine, but a teddybear or no physrep at all wouldn’t be good enough.

4. From the crew page, click the “Ribbon” tab, and enter the ribbon ID in the box. Press Tab or Enter, and the ribbon should load.

5. Review the “Ref Notes” section, just in case there’s something odd about this item that means this needs special handling. In particular, if there are any notes about a “Mark of Ownership”, you should tell the player that the item is subject to a mark of ownership, and tell them the recorded character name.

6. Provide the player with the details in the “Name” and “Bonded Power” sections, and nothing else.
</box>

=====Divination=====
Divination is the mechanism by which characters can work out what other things they could do to find out something interesting about an item. For most items, there is nothing to report here, but generally players will be performing this on some item where they have reason to believe there is something interesting.

If a player has a ribbon and wants to know how they can find out more about it, telling them they can cast this spell (or find a mage who can cast this spell) is often sensible.
<box>
1. Get the player to confirm they’re a mage. You can take their word for this. If they’re not a mage, they can’t cast the spell.

2. Get the player to give you the ribbon ID for the item they want to identify. Unless they have a very good reason, they should be able to show you the ribbon itself. Occasionally someone will try to cast this on an item that doesn’t have a ribbon, in which case the result is simple: “divination tells you nothing interesting about this item”.

3. Confirm the ribbon is attached to a reasonable physrep, unless they have a good excuse such as the physrep being heavy armour they don’t want to carry across the field. There’s a fair degree of latitude here, but we do expect players to make at least a passable effort to have an appropriate physrep for the item. If it’s a sword they’ve looted on the battlefield, the best they might be able to do is a dagger or a mace or a hessian sack (preferably with “swag” written on the side…), all of which would be fine, but a teddybear
or no physrep at all wouldn’t be good enough.

4. From the crew page, click the “Ribbon” tab, and enter the ribbon ID in the box. Press Tab or Enter, and the ribbon should load.

5. Review the “Ref Notes” section, just in case there’s something odd about this item that means this needs special handling. In particular, if there are any notes about a “Mark of Ownership”, you should tell the player that the item is subject to a mark of ownership, and tell them the recorded character name.

6. If there are any boxes with red outlines on the page, provide the player with the names of the rituals or ceremonies stated in those boxes. Don’t tell them anything else, and in particular don’t give them any of the text to the left of those red boxes.
</box>

=====Discern enchantment=====
Discern Enchantment is the way for characters to find out some basic information about other rituals that an item might be subject to. Honestly, this is sufficiently rare that I can’t remember how to handle it. If one of these comes up, get a ref or one of the heads of department to help, and we’ll work it out on the fly. ''(Then remind us to update this manual!)''

'''Identify ritual performance''
In the ''incredibly unlikely'' event that someone comes to GOD to attempt to cast this spell, you’ll need to hand them over to a ref.

=====Discern Arcane Mark=====
“Arcane Marks” are magical records that a character has joined one of the Empire’s magical Orders. The vast majority of the time, this will be handled in the field with a ref, but ''in theory'' it could come to GOD.
<box>
1. Get the player who cast the spell to give you their PID.

2. From the crew page, click “Character”, then enter their PID (with or without the additional CID part) in CID box, then press Tab or Enter to load their character page.

3. Check the character is a mage: they should have “Magician” in a list of skills at the bottom of the page. If they’re not a mage, they can’t cast the spell.

4. Check if the character is a member of one of the Empire’s orders: if they are, it’ll be listed as “Order” in the main part of the character page, in the same place as “Banner”, “Coven” and “Sect”. The entry simply doesn’t appear for characters who aren’t members of an order. If this character is a member of the order, note the name of the order.

Confirm the result here is what the player is expecting: it’s occasionally the case that the database gets this wrong. You may need to be subtle about this, as membership of orders can be an in-character secret.

It’s fine for the character to not be a member of an order, you just need to know because it affects the later results.

5. Get the details of the target of the spell:
* If the target player is present, just get them to give you their PID.
* If the target player is not present:

(a) Confirm that the spell was cast within touching distance of the target, and with the target’s knowledge that this spell was being cast. If the player can’t confirm that, hand this over to a ref.

(b) Get the player to identify the target of the spell. Hopefully they can give you a PID that you can enter into the CID box; if not you’ll need to use the “Search” button or the “Search Characters” interface to find them.

6. On the target’s character page, confirm whether they are a member of an order, just as for the casting character. As with the caster, if the target player is present, double check the result here is what they’re expecting. You may need to be subtle about this, as membership of orders can be an in-character secret.

7. Give the casting player one of the following answers, as appropriate:
* “The target character does not have an arcane mark”
* “The target character has an arcane mark, but as your character does not have an arcane mark themselves, you cannot tell anything else”
* “The target character has an arcane mark, and it is the mark of the same order as your character”
* “The target character has an arcane mark, and it is the mark of a different order to your character’s order”
</box>

=====Discover Conjunction=====
“Discover Conjunction” or “Detect Conjunction” is the mechanism by which ''(a)'' players find out the details of a skirmish they could go on, and ''(b)'' Plot find out that players know the details of a skirmish they could go on. As such, it’s important to use this process if players are finding out about some plot, and equally important to not use this process for purely out-of-character enquiries about things like accessibility information, or enquiries on behalf of crew. As such, “Discover Conjunction” must get recorded whenever it is cast.

If you want to look up information about some plot / encounter / conjunction without using the Detect Conjunction interface, for now either work it out yourself from the Plot pages, or see a head of department; at some point we might get around to documenting the process…
<box>
To record someone casting Discover Conjunction, and to get the information you need to provide:
1. From the crew page, click “Magic”, then “Detect Conjunction”.

2. Enter the PID of the player in the CID box (optionally with the CID part), then press Tab or Enter, or use the Search box to find the character if the player doesn’t know their PID.

3. Get the player to give you the location information they have. Hopefully the player will be able to give you a nation or territory or region, as that’ll give you something to select in the drop-downs on screen and therefore narrow down the search. Once you’ve selected those details, click through to the “Conjunction” view.

4. Getting the region right isn’t enough, in the same way that meeting someone for dinner when the only address you have is “Preston” isn’t likely to work. The player should be able to give you more specific location information, that matches the “Location” column on the screen.

If there’s clearly no match, detecting the conjunction fails. If there’s a good match, carry on. If you’re unsure, get help, either by contacting the plot team yourself, or by escalating to a head of department.

5. Once you’ve found the correct conjunction, click the “Select” button. That ''(a)'' records that the conjunction has been seen by players, so the plot writers know to expect people to actually turn up, and ''(b)'' will get you the data you need to give to the players.

6. Provide the players with the time and day of the conjunction, the expected duration, and the size (which means the number of people who are allowed to go).

7. Ask the player if they need any accessibility information; we don’t provide this automatically, because it’s not in-character information, but if the player wants the accessibility information, we will provide it. Depending on what information will make the plot more accessible, you can provide any or all of the information on the “Access” tab.

If you’re unsure what’s appropriate, tell the player the categories of information that are there, and ask them what information would be relevant to them; trust the player’s assessment of their own abilities – in terms of both what they can and cannot do – and err towards giving as much information as they’d like. It’s much better to give someone a small IC advantage from having access information than it is for someone to be denied access to a plot unnecessarily because of their out-of-character disabilities.

In some cases, the access information may include offers of accommodations, e.g. the plot writer might be planning on using a smoke generator, but it’s not a critical part of the plot so they’d be able to run the plot without it if it’d help with accessibility. If a player wants to take advantage of those accommodations, you’ll probably need to let the plot writer know; either do that yourself or pass it over to a head of department.
</box>

====Night Pouch====

A “night pouch” is a bag up to 18” deep and 6” wide that can only be opened by the person who cast the “night pouch” spell. The pouch is very similar to the pouch created by the ritual “Secrets for the Shadow Courier”; if you have a player asking about a night pouch, make sure they really mean a night pouch, not a Shadow Courier bag. See ''Secrets for the Shadow Courier (Night)'' below if you need to.

If the player is actually casting the night pouch spell, we don’t record that, but we may need to give the player a night pouch ribbon. If the player has an old night pouch ribbon for their character, they can keep using that indefinitely; if they need a new one, we can just give them a replacement. In either case, this is covered in [[Printing]].

''Very occasionally'', a player might come in to hand over something that was left in a night pouch overnight, as that would mean whatever was in the pouch got sent to the Night realm. If that happens, it will need to be passed over to the Plot team; either sort that out yourself if you know what you’re doing, or pass it up to a head of department.

====Other spells====
There are several other spells in the game. GOD should never need to do anything about someone casting any of these.
* Operate portal
* Heal
* Mend
* Purify
* Restore limb
* Voice for the dead

===New ritual===
Rituals are “big” magics. They always require crystalized mana (or something that can substitute for crystalized mana), they’re always affiliated with a specific magical realm (Day, Night, Spring, Summer, Autumn or Winter), and they often involve multiple magicians working together as a coven.

The “New Ritual” page is the page you’ll probably use most frequently in GOD. You’ll land here by default when you click on the “Magic” tab. For most rituals, you can just follow the steps in this section. For complications, see the following subsections.
<box>
1. In the “Caster” section of the page:

''(a)'' In the box labelled “CID”, enter the lead caster’s PID.

''(b)'' Press Tab or Enter.

''(c)'' Confirm the name of the caster’s character.

2. In the “Ritual” section of the page:

(a) From the “Realm” drop-down menu, select the appropriate realm.

(b) From the “Ritual” drop-down menu, choose the name of the ritual.

(c) You can almost always ignore the “Ribbon ID” and “Projection” boxes; if these are relevant, the player will tell you they’re using an arcane projection or a ritual text, and you should choose your own adventure at Arcane Projections or Ritual texts below.

(d) Ask if a regio was used. The answer will usually be no, but if it isn’t, tick the relevant box.

3. Ignore the “Date” section of the page, or escalate to a head of department or referee if there’s some reason you think you shouldn’t.

4. Ask the player if they cast the ritual alone.
* If yes, advance to the Targets tab.
* If no, advance to the Participants tab, add additional casters either by entering their PIDs into the CID box and pressing Tab or Enter, or by clicking the appropriate checkboxes under the Participants heading. You can reorder the list of Participants by clicking the column headings. When you have selected all participants, advance to the Targets tab.

Occasionally the system will give you an error saying the character “has no way to contribute to this coven”. If that happens, ask the player how that person is contributing to the ritual, verify that’s an appropriate solution (get help if you need to), and record details of the explanation in the later “Notes” field.

5. The “Targets” section of the page will vary depending on the type of ritual:
* For rituals that take a prepared letter as a target, select the letter ID from the drop-down list, and confirm the name in the drop-down is the person the player is trying to send a letter to. See Call Winged Messenger below for how this process works in more detail.
* For rituals that target a location on the in-character field, you’ll see a free-text box. Enter enough information from the players that – if needed – a ref would be able to find that location; normally this means the nation camp on the in-character field, plus a description of the tent or area in question.
* For rituals that target some sort of specific location in the wider game world, confirm that the target is a valid target for the ritual (some of these rituals are more specific than the drop-down implies) and select the relevant target from the drop-down.
* For rituals that target an eternal, there are too many special cases to list here; go see Contacting eternals below.
* For rituals that target a ribboned item:

(a) In the box labelled “Ribbon Id”, enter the ribbon ID of the target item. Unless they have a very good reason, the player should be able to show you the ribbon itself.

(b) Confirm the ribbon is attached to a reasonable physrep, unless they have a good excuse such as the physrep being heavy armour they don’t want to carry across the field. There’s a fair degree of latitude here, but we do expect players to make at least a passable effort to have an appropriate physrep for the item. If it’s a sword they’ve looted on the battlefield, the best they might
be able to do is a dagger or a mace or a hessian sack (preferably with “swag” written on the side…), all of which would be fine, but a teddybear or no physrep at all wouldn’t be good enough.

(c) Press Tab or Enter.

(d) Confirm the name on the item shown matches the name printed on the ribbon.

(e) Repeat for any other targets.
* For rituals that target something associated with a character (either the character directly, armies via their general, character resources via the owning character):

(a) In the box labelled “CID”, enter the target character’s PID.

(b) Press Tab or Enter.

(c) Confirm the name of the target’s character.

(d) Repeat for any other targets.
* For all other rituals, you shouldn’t need to specify a target.

6. In the final Ranks section, the system will attempt – with varying degrees of competence – to check whether the players have actually achieved sufficient ranks to cast the ritual. Most of the time everything will be fine, there will be no warning pop-up. In that case, you should just tell the players how much the ritual will cost from the “Mana Crystal Cost” line, then take that many crystalized mana cards off them.

If there is a warning pop-up, or the players disagree with the mana cost, that could be because the players have made an error, because the players are doing something the system can’t (yet) handle to increase their ranks or decrease the cost, or because the system calculation is just plain wrong for some reason. That should be rare, but see Ritual calculations down below for how to handle the scenario.

7. In the notes field, enter anything unusual about the casting. In particular, note why you skipped past any warning messages, e.g. “CID 2458.1 was able to contribute to the casting by using a Volahov’s Robe, ribbon ID 23456”, or “Players achieved an extra three ranks of lore by consuming a Radiant Transcendence potion”.

8. Click “Process”.

9. Check the top of the page for any instructions and follow them as appropriate.
</box>

====Ritual calculations====
Calculating whether a ritual can be cast, and if so how much it costs, is unfortunately complicated. There should be ritual calculation sheets available to help, with brief instructions on the bottom.
If you don’t have that form to hand, use the process below plus a piece of paper.

''(Once you’ve got the hang of things, you don’t need the paper, or to follow this process in full, but I’m assuming if you’re reading this you want the step-by-step guide!)''
<box>

1. First work out the magnitude of the ritual being cast.
* All rituals have a base magnitude. For example, “The Sound of Drums” is a magnitude 11 ritual.
* Some rituals can have multiple targets which increases the magnitude. For example, “Rampant Growth” is a magnitude 10 ritual with a single target, but additional targets can be added, increasing the magnitude by 8 each time, so casting the ritual with three targets would make it a magnitude 26 ritual. Generally, the ritual casting interface will account for these changes correctly.
* Some rituals have mechanisms to reduce the magnitude. For example, “From the Mouths of Babes” is normally a magnitude 8 ritual, but is only a magnitude 2 ritual if an apprentice takes part in the casting. The ritual interface cannot currently account for these sorts of changes; you will need to account for them manually and record the details in the “Notes” section.
* Sometimes players may have some other special mechanism that increases or decreases the magnitude of a ritual, for example a magical artefact that makes it easier to cast a particular ritual.

The ritual interface cannot currently account for these sorts of changes; you will need to account for them manually and record the details in the “Notes” section. Write down this number as the target magnitude for the ritual.

2. If you’re doing this without the form, write out the name or PID of each of the casters across the top of a piece of paper, and label rows with “Lore”, “Regio”, “Other”, “Mana” and “Ranks”.

3. In the “Lore” row, for each caster, record the number of ranks of skill they have in the realm that the ritual is in. This will almost certainly be given correctly by the “Skill” column on the ritual casting page.

4. In the “Regio” row, write “1” for each character if a regio is being used, or “0” otherwise.

5. In the “Other” row, write down the additional ranks for each character that are granted because they’re using a potion or magical artefact or similar that increases their ranks.

6. In the “Mana” row, write down either the sum of the “Lore”, “Regio” and “Other” rows, or three times the number in the “Lore” row, whichever is smaller.

7. In the “Ranks” row, for each character who has the ritual mastered, write down double the number in the “Mana” row, and for each character who does not have the ritual mastered, write down the same number as in the “Mana” row.

8. The total of all the numbers in the “Ranks” row needs to be at least the magnitude of the ritual, or the ritual fails.

9. The numbers in the “Mana” row are the maximum amount of mana each ritual caster can contribute. If the total of the “Ranks” row is higher than the required magnitude, the players will probably not want to spend mana unnecessarily.

(a) Go through the list of characters who do not have the ritual mastered, and reduce the numbers in the “Mana” and “Ranks” rows either to zero or to the lowest number that still means the ritual can be cast.

(b) If there is still spare ranks, go through the list of characters who do have the ritual mastered, and reduce the amount of mana they’re contributing too, until you have reduced the numbers as far as they will go.

10. Add up the new total of the “Mana” row, and take this many crystalized mana cards off the players (or equivalents, e.g. Vis cards count for three crystalized mana in the relevant realm).
</box>

====Special rituals====

=====Contacting eternals=====
Eternals are magical beings. Players – in particular mages – often want to contact them. There are a selection of standard rituals for doing this, plus a couple of other options. They’re all processed as if they were a ritual, however.
<box>
1. Start by logging in and going to the “Magic” tab, which should load the “New Ritual” page.

2. Ask the player how they’re sending the message.
* If they’re using a named ritual, then:

(a) In the box labelled “CID”, enter the PID of the person sending the message.

(b) Press Tab or Enter.

(c) Confirm the name of the caster’s character.

(d) Fill in the realm and ritual name as appropriate, or, in the vanishingly rare case of an arcane projection or ritual text, see ''Arcane Projections'' or ''Ritual texts'' as appropriate.
* If they’re an archmage using the “Plenipotentiary” power:

(a) In the box labelled “CID”, enter “0.1”.

(b) Press Tab or Enter.

(c) Confirm the name that appears is “Ref Dummy Character”.

(d) Select the realm as “Autumn” and the ritual as “Plenipotentiary”.
* If they’re doing something else, check the details. If what they’re doing makes sense and there are no instructions to the contrary (e.g. in the ref notes on the page for the relevant ribboned item):

(a) In the box labelled “CID”, enter “0.1”.

(b) Press Tab or Enter.

(c) Confirm the name that appears is “Ref Dummy Character”.

(d) Select the realm as “Autumn” and the ritual as “Another Missive”.

3. Complete the participants list as normal for normal rituals, and ignore it for anything cast by Ref Dummy Character.

4. The path now diverges according to the contents of the “Targets” page:
* If the “Targets” page has “Set Target Eternal” at the top:

(a) Select the appropriate eternal from the drop-down, or – if they’re not listed – enter the eternal’s name in the “Name” box

(b) Click through to ranks.

– If the players are casting a regular ritual, they will need to meet the rank requirements as normal. The system will attempt – with varying degrees of competence – to check whether the players have actually achieved sufficient ranks to cast the ritual. Most of the time everything will be fine, there will be no warning pop-up. In that case, you should just tell the players how much the ritual will cost from the “Mana Crystal Cost” line, then take that many crystalized mana cards off them.

If there is a warning pop-up, or the players disagree with the mana cost, that could be because the players have made an error, because the players are doing something the system can’t (yet) handle to increase their ranks or decrease the cost, or because the system calculation is just plain wrong for some reason. That should be rare, but see Ritual calculations above for how to handle the scenario.

– If the players are doing something that involved Ref Dummy Character, you can ignore any warning messages about ranks achieved.

(c) Click “Process”

(d) You should now get a page with the details of the casting. Check the top of the page for any instructions and follow them as appropriate.

(e) Click the “Message” tab at the top of the page.

(f ) Click “Set Response”

(g) Type out the message in the “Message” section; don’t touch anything in the lower “Plot Response” section.

(h) Click “Save”.
* If the “Targets” page has anything else, such as a space for a target ribbon or a target character:

(a) Complete the targets as normal; the player should be expecting to provide these.

(b) Click through to ranks. The system will attempt – with varying degrees of competence – to check whether the players have actually achieved sufficient ranks to cast the ritual. Most of the time everything will be fine, there will be no warning pop-up. In that case, you should just tell the players how much the ritual will cost from the “Mana Crystal Cost” line, then take that many
crystalized mana cards off them.

If there is a warning pop-up, or the players disagree with the mana cost, that could be because the players have made an error, because the players are doing something the system can’t (yet) handle to increase their ranks or decrease the cost, or because the system calculation is just plain wrong for some reason. That should be rare, but see Ritual calculations above for how to handle the scenario.

(c) Click “Process”

(d) You should now get a page with the details of the casting. Check the top of the page for any instructions and follow them as appropriate.

(e) Click the “Notes” tab at the top of the page.

(f ) Click “New”

(g) Set the title of the new note to something like “Message text”.

(h) Type out the player’s message in the “Note” box.

(i) Click “Save”.
</box>

=====Secrets for the Shadow Courier (Night)=====
Secrets for the Shadow Courier essentially replicates the effect of the “night pouch” spell (see Night pouch above), but longer lasting and with the ability to create a pouch that can only be opened by any given character, rather than only by the person who cast the spell. As a result, players will sometimes incorrectly refer to this ritual as “night pouch”.

This ritual is recorded as normal, and doing so should generate a ribbon on the ribbon print queue. Fetch the ribbon, give it to the player.

=====Call Winged Messenger=====
This ritual allows players to send messages to regular, mortal NPCs. Technically it can also be used to send messages to regular, mortal player characters, but it’s very rarely used for that purpose, as it’s slow (we just put the message in the relevant player’s pack at the next event, so there’s at least a one-event delay) and expensive (it costs three Iridescent Gloaming and one or two crystal mana, compared to a few rings for an IC courier). It’s also a ritual that has multiple steps and often causes confusion, both for crew and players.

For players, there’s a pamphlet available, the GOD Guide to Call Winged Messenger. Feel free to give copies out to anyone who wants one; if we run out it’s easy to print more. It’s also useful for GOD crew to read, so we know what the process looks like from a player perspective. For GOD crew, there are multiple steps, each of which is individually straightforward, but – particularly if you’re dealing with a confused player – it can be helpful to understand how they all fit together!
<box>
1. So the player can write the letter in the first place, they need to have 3 Iridescent Gloaming in their character inventory. They’ll need to hand this in at GOD, and we need to record it; see ''New Entry'' under ''Inventory'' in [[Character processess]].

2. Once the player has the Gloaming in their account, send them to write their letter. They can do this on the player PCs, or on a device of their own that they can connect to the PD Wi-Fi. Now the Gloaming is in their account, there should be a button to write the letter on their character page.

3. Once the player has written their letter, they should come back to us to get us to print the letter phys-rep.

(a) Load the character inventory and check the only item in the inventory is the letter.
* If they do have anything else in their account, this becomes awkward and either needs much longer instructions (that I’ve not yet written out) or for someone who’s comfortable wrangling awkward bits of the interface to sort it, which probably means Adam or Matt.
* If they don’t have anything else in their account, click the “Book Out” button. This will add the letter to the print queue; see [[Printing]]

(b) Give the player their printed letter physrep.

4. The player will need to go away and perform the Call Winged Messenger ritual, or find someone who can perform it for them. When someone comes back to record that the ritual has been cast, we record it as normal per ''New Ritual'' above. It doesn’t have to be the same character writing the letter as sends the ritual; anyone can write a letter, but only a mage can cast the ritual to send it.

When you’re recording the ritual, the “target” will be the specific letter that’s being sent. If the player got us to print the letter for them, check the letter number and who it’s being sent to on the letter cover sheet; if they didn’t pick up the printed letter, get them to confirm the ID number and the name of the person they’ve selected.

</box>

=====A side note on inventories=====
The fact that letters get put into inventories when they get written, but not everyone asks us to print them, means that some letters get sent while they’re still in a character’s inventory. This doesn’t make sense, but it’s a side-effect of how the PD database works.

This means that when a player next comes to an event, the letter that they’ve already sent gets booked out of their inventory and put into their character pack with the rest of their character resources. After E1 2023, Adam has started clearing out these items from inventories, so this should stop being a problem and this will just be a historical note. It’s included in the manual at least until we’re confident Adam’s new process here works as expected.

=====Swim leviathan's depth=====
'''TODO'''

=====Arcane projections=====
An arcane projection is a text that players can create in downtime (or occasionally obtain by other means). It’s essentially a custom ritual generated as a one-off, rather than one of the standard rituals. This section only covers how to record when someone casts an arcane projection; for a more general overview of what arcane projections are and how they work, see Arcane projections below.

Arcane projections are distinct from ritual texts: an arcane projection can only be used once and provides 10 mana towards the casting, whereas a ritual text can be used repeatedly but the caters must pay the entire cost in crystal mana (or alternatives such as vis). For casting from ritual texts, see Ritual texts above.
<box>
From the “Magic” section of the crew pages:

1. Get the players to give you the arcane projection they’re casting. This should be a piece of paper with a number at the top similar to “E26”, and a ritual name.

2. In the “Caster” section of the page:

(a) In the box labelled “CID”, enter the lead caster’s PID.

(b) Press Tab or Enter.

(c) Confirm the name of the caster’s character.

3. In the “Ritual” section of the page:

(a) From the “Realm” drop-down menu, select the appropriate realm; this should be listed on the arcane projection.

(b) Ignore the “Ritual” drop down.

(c) In the first “Projection” box, select the “E” number from the top of the paperwork.

(d) In the second “Projection” box, which should have been populated when you selected the “E” number, select the name of the ritual being cast.

(e) Ignore the “Ribbon Id” box.

(f ) Ask if a regio was used. The answer will usually be no, but if it isn’t, tick the relevant box.

4. Ignore the “Date” section of the page, or escalate to a head of department or referee if there’s some reason you think you shouldn’t.

5. Ask the player if they cast the ritual alone.
* If yes, advance to the Targets tab.
* If no, advance to the Participants tab, add additional casters either by entering their PIDs into the CID box and pressing Tab or Enter, or by clicking the appropriate checkboxes under the Participants heading. You can reorder the list of Participants by clicking the column headings. When you have selected all participants, advance to the Targets tab.

Occasionally the system will give you an error saying the character “has no way to contribute to this coven”. If that happens, ask the player how that person is contributing to the ritual, verify that’s an appropriate solution (get help if you need to), and record details of the explanation in the later “Notes” field.

6. The “Targets” section of the page will vary depending on the type of ritual:
* For rituals that take a prepared letter as a target, select the letter ID from the drop-down list, and confirm the name in the drop-down is the person the player is trying to send a letter to. See ''Call Winged Messenger'' above for how this process works in more detail.
* For rituals that target a location on the in-character field, you’ll see a free-text box. Enter enough information from the players that – if needed – a ref would be able to find that location; normally this means the nation camp on the in-character field, plus a description of the tent or area in question.
* For rituals that target some sort of specific location in the wider game world, confirm that the target is a valid target for the ritual (some of these rituals are more specific than the drop-down implies) and select the relevant target from the drop-down.
* For rituals that target an eternal, there are too many special cases to list here; go see Contacting eternals above.
* For rituals that target a ribboned item:

(a) In the box labelled “Ribbon Id”, enter the ribbon ID of the target item. Unless they have a very good reason, the player should be able to show you the ribbon itself.

(b) Confirm the ribbon is attached to a reasonable physrep, unless they have a good excuse such as the physrep being heavy armour they don’t want to carry across the field.

There’s a fair degree of latitude here, but we do expect players to make at least a passable effort to have an appropriate physrep for the item. If it’s a sword they’ve looted on the battlefield, the best they might be able to do is a dagger or a mace or a hessian sack (preferably with “swag” written on the side…), all of which would be fine, but a teddybear or no physrep at all wouldn’t be good enough.

(c) Press Tab or Enter.

(d) Confirm the name on the item shown matches the name printed on the ribbon.

(e) Repeat for any other targets.
* For rituals that target something associated with a character (either the character directly, armies via their general, character resources via the owning character):

(a) In the box labelled “CID”, enter the target character’s PID.

(b) Press Tab or Enter.

(c) Confirm the name of the target’s character.

(d) Repeat for any other targets.

* For all other rituals, you shouldn’t need to specify a target.

7. In the final Ranks section, the system will attempt – with varying degrees of competence – to check whether the players have actually achieved sufficient ranks to cast the ritual. Most of the time everything will be fine, there will be no warning pop-up. In that case, you should just tell the players how much the ritual will cost from the “Mana Crystal Cost” line, then take that many crystalized mana cards off them. The arcane projection text counts as 10 crystal mana, so you need 10 fewer mana than the form states.

If there is a warning pop-up, or the players disagree with the mana cost, that could be because the players have made an error, because the players are doing something the system can’t (yet) handle to increase their ranks or decrease the cost, or because the system calculation is just plain wrong for some reason. That should be rare, but see Ritual calculations above for how to handle the scenario.

8. In the notes field, enter anything unusual about the casting. In particular, note why you skipped past any warning messages, e.g. “CID 2458.1 was able to contribute to the casting by using a Volahov’s Robe, ribbon ID 23456”, or “Players achieved an extra three ranks of lore by consuming a Radiant Transcendence potion”.

9. Click “Process”.

10. Check the top of the page for any instructions and follow them as appropriate.

11. Take the arcane projection text off the players, and destroy it.
</box>

=====Ritual texts=====
Ritual texts are pieces of paper that give details of a ritual, and allow anyone holding them to cast or learn the ritual on them. Players cannot typically create ritual texts.

For learning ritual texts, see ''Learning new rituals or recipes for items in'' [[Character processess]]. For casting from ritual texts, read on.
<box>
From the “Magic” section of the crew pages:

1. Get the players to give you the ritual text they’re using. This should be a piece of paper with a ribbon ID number printed in the corner.

2. In the “Caster” section of the page:

(a) In the box labelled “CID”, enter the lead caster’s PID.

(b) Press Tab or Enter.

(c) Confirm the name of the caster’s character.

3. In the “Ritual” section of the page:

(a) From the “Realm” drop-down menu, select the appropriate realm; this should be listed on the arcane projection.

(b) Ignore the “Ritual” and “Projection” boxes.

(c) In the first “Projection” box, select the “E” number from the top of the paperwork.

(d) In the “Ribbon Id” box, enter the ribbon number printed on the document.

(e) Ask if a regio was used. The answer will usually be no, but if it isn’t, tick the relevant box.

4. Ignore the “Date” section of the page, or escalate to a head of department or referee if there’s some reason you think you shouldn’t.

5. Ask the player if they cast the ritual alone.
* If yes, advance to the Targets tab.
* If no, advance to the Participants tab, add additional casters either by entering their PIDs into the CID box and pressing Tab or Enter, or by clicking the appropriate checkboxes under the Participants heading. You can reorder the list of Participants by clicking the column headings. When you have selected all participants, advance to the Targets tab.

Occasionally the system will give you an error saying the character “has no way to contribute to this coven”. If that happens, ask the player how that person is contributing to the ritual, verify that’s an appropriate solution (get help if you need to), and record details of the explanation in the later “Notes” field.

6. The “Targets” section of the page will vary depending on the type of ritual:
* For rituals that take a prepared letter as a target, select the letter ID from the drop-down list, and confirm the name in the drop-down is the person the player is trying to send a letter to. See ''Call Winged Messenger'' above for how this process works in more detail.
* For rituals that target a location on the in-character field, you’ll see a free-text box. Enter enough information from the players that – if needed – a ref would be able to find that location; normally this means the nation camp on the in-character field, plus a description of the tent or area in question.
* For rituals that target some sort of specific location in the wider game world, confirm that the target is a valid target for the ritual (some of these rituals are more specific than the drop-down implies) and select the relevant target from the drop-down.
* For rituals that target an eternal, there are too many special cases to list here; go see ''Contacting eternals'' above.
* For rituals that target a ribboned item:

(a) In the box labelled “Ribbon Id”, enter the ribbon ID of the target item. Unless they have a very good reason, the player should be able to show you the ribbon itself.

(b) Confirm the ribbon is attached to a reasonable physrep, unless they have a good excuse such as the physrep being heavy armour they don’t want to carry across the field. There’s a fair degree of latitude here, but we do expect players to make at least a passable effort to have an appropriate physrep for the item. If it’s a sword they’ve looted on the battlefield, the best they might
be able to do is a dagger or a mace or a hessian sack (preferably with “swag” written on the side…), all of which would be fine, but a teddybear or no physrep at all wouldn’t be good enough.

(c) Press Tab or Enter.

(d) Confirm the name on the item shown matches the name printed on the ribbon.

(e) Repeat for any other targets.
* For rituals that target something associated with a character (either the character directly, armies via their general, character resources via the owning character):

(a) In the box labelled “CID”, enter the target character’s PID.

(b) Press Tab or Enter.

(c) Confirm the name of the target’s character.

(d) Repeat for any other targets.

* For all other rituals, you shouldn’t need to specify a target.

7. In the final Ranks section, the system will attempt – with varying degrees of competence – to check whether the players have actually achieved sufficient ranks to cast the ritual. Most of the time everything will be fine, there will be no warning pop-up. In that case, you should just tell the players how much the ritual will cost from the “Mana Crystal Cost” line, then take that many crystalized mana cards off them. The arcane projection text counts as 10 crystal mana, so you need 10 fewer mana than the form states.

If there is a warning pop-up, or the players disagree with the mana cost, that could be because the players have made an error, because the players are doing something the system can’t (yet) handle to increase their ranks or decrease the cost, or because the system calculation is just plain wrong for some reason. That should be rare, but see Ritual calculations above for how to handle the scenario.

8. In the notes field, enter anything unusual about the casting. In particular, note why you skipped past any warning messages, e.g. “CID 2458.1 was able to contribute to the casting by using a Volahov’s Robe, ribbon ID 23456”, or “Players achieved an extra three ranks of lore by consuming a Radiant Transcendence potion”.

9. Click “Process”.

10. Check the top of the page for any instructions and follow them as appropriate.

11. Give the players back the ritual text.
</box>

===New campaign effect===
'''Never use this'''

===Search effects===

The “Search Effects” interface allows you to search for a ritual that was cast at some point in the past. It is mostly useful if you are trying to unpick something that has gone wrong, which probably means you want to be talking to a head of department if you’re interested in it.

===Arcane projections===

'''TODO:''' general process, also checking why APs were rejected &c‥

[[Category:GOD manual]]

Character processes

2023-07-07T10:44:48Z

Jmabb:

This page contains an exciting mix of things that players have to do, things that players can ''(and should, if possible)'' do themselves, things we’re happy to do for them, and things ''we'' have to do that players can’t.

'''Players have to:'''
* create new characters
* create new bands

'''Players generally should, but GOD can:'''
* record character retirements or deaths
* check what skills they know
* assign their own skill points
* choose which rituals and recipes to learn from within Imperial lore

'''GOD can:'''
* manually reassign skill points (e.g. for new players, or for access reasons)

'''GOD has to:'''
* perform dead-or-alive checks
* activate new characters
* move characters between nations
* change or swap characters’ Personal Resources
* record that characters have learned rituals or recipes that fall outside Imperial lore

For the processes in this chapter, start by getting to the “Character” tab of the crew interface unless otherwise specified.

===Miscellaneous===

====Creating new characters====

To create a new character, a player needs to log into their PD account on a device connected to the PD Wi-Fi. If they have their own phone or laptop and can connect to the PD Wi-Fi, or can use a player PC, this is ideal, but if necessary and the queue is short enough they can use one of the query PCs.

When creating a new character, the player can join any publicly listed band. If they want to join a secret band, they can only do that in play; from our perspective, that process is described in ('''TODO''' Create Bond). Once the new character has been created, the player should come to the front desk in GOD and ask for the new character to be activated and their new pack to be printed.

====Creating new bands====
To create a new band, a player needs to log into their PD account on a device connected to the PD Wi-Fi. Once the band has been created, there are two ways characters can join:
* If the band is public, new characters can join during the character generation process, by simply selecting the band name from a drop-down list.
* If the band is secret, or the character looking to join is already in play, the only way for them to join is in play, using the ('''TODO''' Create Bond spell per Create Bond.)

====Dead or Alive?====
'''''Note''' that egregores can check whether a character in their nation is dead or alive.''
<box>
1. Get to the “Players” tab of the crew interface.

2. Look up the PID of the character’s player.

3. Click on the “Characters” tab under the player name.

4. Check that the relevant character is a member of the egregore’s nation.

5. If the character status is “Dead”, the character is dead. If the character status is “Retired” or “Played”, the character is alive. Tell the egregore whether the character is dead or alive according to our system (obviously, particularly during and shortly after battles, there may be a delay between the character dying and it getting updated on the database, but egregores should be expecting that).
</box>

===Details===
This section describes the function of the buttons present on the right-hand side of the page on the Details tab under the character name.
====Play character====
This button is only present for a character that has been created but not activated
<box>
1. Click “Play Character”.

2. A pop-up will appear saying something like “Please confirm that you wish to set [character] to played and create their resource and inventory.” Click “Confirm”.

3. A button labelled “Event Pack” will now appear on the right-hand side of the page. Click “Event Pack”.

4. A pop-up will appear saying something like “Please confirm that you wish to book out the inventory for [character] and print them an event pack.” Click “Confirm”.
* '''''Note''': because the character has been newly set to played, you should always see a confirmation that the player envelope and passport have been sent to the print queue. You should never see a message that the envelope and passport were already in the print queue. If you do, something has gone very wrong – get one of the heads of department to come and poke around in the system!''

5. Either ask the player to wait while you assemble their pack (see 9.2 Making up), or ask them to come back in a time frame you have agreed with the heads of department, and make a note of the PID, the time you sent their pack request to the print queue, and the time you told them to come back. Make sure the heads of department have this information.
</box>

====Retiring and killing characters====

''Retiring'' a character leaves them alive but makes them unplayable. ''Killing'' a character changes their status to dead. When players come in to GOD to register a character death, they should hand in any game items that were on their character’s body at the moment they stopped phys-repping the body. (So, for example, if their body was looted after their death but before they stopped phys-repping the body, those items are still in circulation and do not need to be handed in!)

Players can both retire characters and report character deaths themselves, but we’ll often do it for them. If a player has already generated a new character, go ahead and retire or kill their existing active character for them before activating their new character. If they haven’t, feel free to tell them to head to the player PCs (or use one of their own devices connected to the PD Wi-Fi) to report their character death and create their new character, then come back to the front desk to have their new character activated and their new pack prepared.
<box>
The steps are at least straightforward for this one:

1. Click “Retire Character” or “Kill Character” as appropriate.

2. Click “Confirm” in the dialogue box.
</box>

====Edit character====
<box>
1. Enter the PID and press Tab or Enter. (This will automatically take you to the page of the currently active character.)

2. Click “Edit Character” from the buttons on the right-hand side of the page.

3. The only things you should ever change using this dialogue box are the name and the archetype. '''Do not change any other field via this dialogue unless you are being given explicit instructions by a head of department or referee''': some fields can be changed via other menus, and some fields should not be changed at all.
</box>

====Leave band====
Players can leave a band for any reason, but we have to process this for them. ''(Players automatically leave all bands when moving nations).''
<box>
1. Click “Leave Band”.

2. Double-check with the player which of their Banner, Coven, and Sect they wish to leave.

3. Tick the appropriate check boxes.

4. Click “Save”.
</box>

====Move nation====
Before registering a change of nation at GOD, players should have completed roleplay in the field and obtained agreement from the egregore of the nation the character is moving to.
<box>
1. Confirm that the character has performed the appropriate roleplaying with the egregore of the nation they are moving to. This is a key step, but some players aren’t aware of it.

2. Find the page for the player’s character, and click “Move Nation”.

3. In the pop-up, select the new nation from the drop-down.

4. Click “Save”.
</box>
When a character changes nation they ''may'' also wish to change the location of their Personal Resource (see Personal Resources below), but this isn’t a requirement.

====Personal Resources====

'''''For more details'''-[https://www.profounddecisions.co.uk/empire-wiki/Resource#Personal_Resource Personal Resources- Player wiki]''

There are nine types of Personal Resource, listed here along with what a basic (level 1) resource of each type, that is not
subject to any penalties, produces each downtime:
• Business: produces 9 crowns
• Congregation: produce 5 doses of liao; provides 10 votes in the Imperial Synod; '''cannot be owned by crew'''
• Farm: produces 9 crowns
• Fleet: trades to produce items or money, or privateers to produce random resources
• Forest: produces 12 units of one rare material
• Herb garden: produces 14 herbs (2 Bladeroot, 2 Cerulean Mazzarine, 2 Imperial Roseweald, 2 Marrowort, 6 True
Vervain)
• Mana site: produces 7 mana crystals
• Military unit: can be used to enhance an Imperial army, or to produce random resources
• Mine: produces 12 units of one rare metal

There are a number of things players might want to do with their resource, some of which GOD can help with and some of
which we can’t.
====Change resource====
Whether or not we charge people depends on why they want to change resource. If they’re a new player or character, they’re still getting to grips with the game, or they’re not having fun, they can change resource for free. Otherwise, there’s a charge.

'''''Note:''' game crew – crew like GOD whose crewing mostly happens during time-in, rather than, say, the site crew who make things happen before and after time-in – cannot have Congregations as their personal resource. This probably won’t come up, but if you do get a crew member asking to change their resource to a Congregation, call a head of department over.''
<box>
1. Click “New Resource”.

2. In the pop-up that appears, select the desired new resource from the “Type” drop-down.

3. Check whether the player wishes to change the location of their resource, and if so make that change using the “Territory” drop-down.

4. Select one of the Payment radio button options.

5. Click “Save”.
</box>
====Swap resource====
Sometimes two players will want to swap ownership of their resources. Provided you have both players in front of you and they’re both happy with this, go ahead and do it!

This is also how to handle resources that were left by a dead character to another in a will: swap the dead character’s resource with the living character’s resource. You can normally take it on trust that the players are being reasonable here, but if you’re concerned, get a head of department.

(Neither GOD nor referees will register wills out-of-character, nor will the Civil Service register them in character; they’re entirely managed by players, with the sole exceptions of ''(a)'' they need someone in GOD to swap resources over, and ''(b)'' if there’s a dispute about a will, player characters are able to involve the magistrates, who are PD NPC crew.)
<box>
1. Navigate to the character page of one of the players.

2. Confirm that their resource is what they think it should be.

3. Click “Swap Resource”.

4. In the pop-up that appears, enter the other player’s PID in the “Recipient” box and press Enter or Tab, or click “Search”.

5. Confirm with the players that the recipient character name is what they expect. (If not, see Looking up PID's in [[Player accounts]])

6. Select one of the Payment radio button options. ''(For resource swaps, you will almost always need to take payment.)''

7. Click “Save”.
</box>

====Assign Resource====
'''Ignore this button'''. If GOD ever needs to touch it, something has gone wrong – escalate to a head of department so they can handle things.

====Upgrades====

Personal resources can only be upgraded during downtime. This is not something we can do in GOD during an event.

Personal resources can only be upgraded one level per downtime. Upgrading a resource requires Bourse resources (i.e. mithril, weirwood, or white granite). The number of wains required is equal to the level being upgraded to, so upgrading a resource from level 1 to level 2 requires 2 wains of the relevant material; upgrading from level 2 to level 3 requires 3 wains; and so on.

To check what level a resource has been upgraded to, click the resource type under the character details. The resource details will open, likely in a new tab. In the Details tab, next to the heading “Upgrades”, a pair of numbers will be given in the format “2 / 1”.
* The first number indicates the number of upgrades the resource has received. This is likely to be relevant when double-checking that people are about to swap the resources they intended to.
* The second number indicates the effective number of upgrades taking into account any bonuses or penalties. For more detail as to what’s going on for any particular resource, see the “Magic” tab. This information is likely to be relevant if somebody received fewer materials in their player pack than they expected.

===Skills===

There are lots of things relating to skills that players can do for themselves. In general, in this section, use your discretion: if there’s a long queue for the player PCs and a short queue for queries, or the player wants to ask multiple questions and skills are only some of them, or they’re a new player or generally seem like they’d benefit from reassurance, feel free to use your judgement about whether to redirect them or whether to answer their questions yourself. All the step-by-step instructions in this section assume that you are starting from the “Skills” tab of a Character page.

====Miscellaneous information====

* Sometimes players are concerned that their player passport is out-of-date, either because they think GOD crew won’t believe they know how to do things (we can check on the computers if we’re worried), or because they’re concerned they’ll forget what they know. Offer to hand-write the details of their skills on their existing passport (and initial it). As a last resort, offer to print out a new copy of their player passport.
* If a player wants to know how much XP they have to spend: ideally redirect them to someone who can show them how to find this out for themselves at the player PCs.

====Learning new skills====
Characters learn skills by spending skill points, or XP. Characters receive 8 XP on creation, and 1 XP for the first and third event they attend each year. Players can spend XP themselves using player PCs or their own devices (connected to the PD Wi-Fi). If players aren’t sure how to do this themselves – or are unsure how many XP points they have available – ideally they’d be
redirected to the player PCs, if a member of GOD crew is present to explain to them, or show them how to do it. Use your judgement.

'''''Note:''' if you do wind up adding skills for players, be aware that the system lets crew spend more XP than the player actually has available, because it’s very occasionally useful to allow players to “overspend” their XP. You should never be doing this unless you have been told to by a head of department.''
<box>
1. Click “Edit Skills” from the buttons on the right-hand side of the page.

2. Click the “Add Skill” button in the middle of the page, under the “Total Points Available” line.
* Note the appearance of the “Total Points Allocated” line. When the number after the “Total Points Allocated” line is equal to the number of points after the “Total Points Available” line, you have spent all the character’s XP and should not keep adding skills!

3. Choose a skill from the drop-down box labelled “Choose One”.
* Note that some skills require other skills as prerequisites, e.g. the skill “Hero” must be bought before any of the other “Heroic Skills” can be purchased. See the wiki for more information.

4. If necessary, click “Add Skill” again to generate another drop-down box.

5. If at any point you make a mistake, click “Delete” next to the skill you wish to delete (or simply change the dropdown to a skill you intended to add). At any time, you can click “Cancel” at the bottom of the page to discard all your changes and leave the page, or “Reset” to return the page to the state it was in before you began editing it.

6. Read out the list of changes you’ve made to the player to confirm they’re happy.

7. When complete, click “Save” at the bottom of the page.
</box>
'''''Note''' that the interface for players looks different – both in terms of how to get there and in terms of what it looks like once you are there. Watching over our shoulders won’t help them much with sorting themselves out in future!''

====Learning new rituals or recipes for items====

Players can master most rituals (for mages) or learn most recipes for items (for artisans) themselves, at player PCs or using their own devices connected to PD Wi-Fi. Use your discretion.
<box>
To master a ritual that is part of Imperial lore:

1. Click “Edit Rituals” from the buttons on the right-hand side of the page.

2. Find an empty lore slot for the appropriate realm for the ritual, i.e. one with a blank drop-down (“Choose One”) next to it.
* If the player doesn’t know the realm for the ritual, you can look it up on the wiki.
* If the player does not have an empty lore slot, they will need to spend XP on an additional ritual slot for the appropriate realm. You can do this for them now (see Learning new skills above).

3. Select the ritual name from the drop-down box.

4. Click “Save” at the bottom of the page.
</box>
However, when characters learn rituals or recipes that do not form part of Imperial lore, this must be recorded by a member of GOD crew (or sometimes by MattP).
<box>
For mastering a ritual that is not part of Imperial lore:

1. The player must have in their possession the physical “ritual text” (magic bit of paper), which will usually be printed on vellum.

2. Click “Edit Rituals” from the buttons on the right-hand side of the page.

3. Find an “Extra lore” slot with a blank drop-down (“Choose One”) next to it.
* If the player does not have an empty “Extra lore” slot, they will need to spend XP on “Extra ritual”. You can do this for them now (see Learning new skills above).

4. Select the ritual matching the name on the ritual text.

5. Click “Save” at the bottom of the page.

To learn to make items in general:
1. Click “Edit Items” from the buttons on the right-hand side.

2. '''TODO''': complete this, including noting the restrictions on what levels of thing can go where.
</box>
Learning to make an item that is not part of Imperial lore happens rarely. If you’re confused about an item a player is asking about, escalate to the heads of department – they might well need to radio through to plot to ask what’s going on.

====Dropping and forgetting skills====
Players sometimes want to forget skills, rituals, or recipes they already know, for a variety of reasons.
* After a brand new player’s first event, they can retrain as many skills and options as they want to, including all of them, by logging in to their account on the PD website. There’s an enormous amount of lore, and getting your head around it takes time! We can also do this for them at their first event, especially if they’re not having fun.
* After every event a player attends, they can retrain a single skill, crafting option, or pair of rituals, by logging in to their account on the PD website. If a player did not use this option during downtime before an event, they can do it themselves at the event using a player PC or their own device.
* Sometimes a player’s access needs change, e.g. they have spent a lot of XP points on battle skills but can no longer participate in battles. In these cases, we need to remove all their battle skills for them. Err on the side of generosity and believing the player, here – and if in doubt, escalate to more senior crew or heads of department.

In general, if a player wants to forget more than one skill for IC reasons rather than OC reasons (e.g. access reasons, being a brand new player), they’ll need to forget skills gradually, one per event, or find some other in character mechanism (e.g. this has sometimes been possible with magic rituals) – but do escalate if you’re at all unsure.

'''''Note''': if players want to forget all the rituals they’ve mastered, freeing up all their ritual slots, this is possible in-game with the ritual Infant Starts with a Blank Slate. Tell them that a ritual exists for this, and ask them if they’d like to be told the name by you or if they’d rather find it out in play – either is fine!''
<box>
To use a player’s ability to forget one skill, one item recipe, or two mastered rituals per event on their behalf:

1. Click “Drop Skill” from the buttons on the right-hand side of the page.
* You will be taken to the “Retrain Skill” page.
* If the player wishes to retrain a skill:

(a) Click the button labelled “Retrain” next to the skill the player wants to forget.

(b) Click “Save” at the bottom of the page.

– Some skills are prerequisites for others. For example, the skill “Magician” cannot be retrained while a character knows any realm lore. The “Retrain Skill” button won’t appear next to a skill that is a required for other known skills.

* If the player wishes to retrain rituals:
(a) Click “Cancel” at the bottom of the page.

(b) Click “Rituals” from the tabs underneath the character name.

(c) Click “Retrain Ritual” from the buttons on the right-hand side of the page.

(d) Click the button labelled “Retrain” next to up to two rituals the player wants to forget.

(e) Click “Save” at the bottom of the page.

* If the player wishes to retrain an item recipe:
(a) Click “Cancel” at the bottom of the page.

(b) Click “Items” from the tabs underneath the character name.

(c) Click “Retrain Item” from the buttons on the right-hand side of the page.

(d) Click the button labelled “Retrain” next to the item the player wants to forget.

(e) Click “Save” at the bottom of the page.

The player can then relearn skills, rituals, and recipes as normal (see Learning new skills, Learning new rituals or recipes for items above).
</box>
<box>
To forget multiple skills, e.g. for access reasons or for a brand new player, without affecting the player’s ability to forget one skill per downtime:

1. Click “Edit Skills” from the buttons on the right-hand side of the page.

2. Click the button labelled “Delete” next to each skill the player wants to forget.
* Note: this system will let you delete skills that are prerequisites for other skills. For example, you will be able to delete “Magician” without also deleting “Autumn lore”. If in doubt, check the wiki or check in with more senior crew.

3. Click “Save” at the bottom of the page.

To forget rituals:

1. Click “Edit Rituals” from the buttons on the right-hand side of the page.

2. Click the button labelled “Delete” next to each ritual the player wants to forget.

3. Click “Save” at the bottom of the page.

To forget item recipes:

1. Click “Edit Items” from the buttons on the right-hand side of the page.

2. Click the button labelled “Delete” next to each item the player wants to forget.

3. Click “Save” at the bottom of the page.
</box>

'''Ignore the “Edit Dropped Skills” button '''– ''you shouldn’t ever need to use this if you’re not a head of department.''

===Inventory===
In theory, the entire contents of people’s inventories should be “booked out” into their player packs at the beginning of every event. In a small number of cases, this might not happen – if so, any items still in people’s inventories should be listed on the “Inventory” tab under the character name. All the processes in this section assume you’re starting from the Inventory tab unless otherwise specified.

Some frequently asked questions are:
* Can I deposit…? →New Entry
* Can I withdraw…? →New Entry
* I thought my pack was supposed to contain… →Show Entries
'''TODO:''' Actually write this up
====New entry====
Generally players are discouraged from depositing items to their inventory at the event unless they’re using them immediately for a ritual or similar. (See Resource hand-in in [[Player Packs- GOD]])
<box>
'''To record deposits:'''

1. Click “New Entry” from the buttons on the right-hand side of the page. A pop-up will appear.

2. For each resource, enter a positive number in the appropriate box. Multiple resources can be deposited at once.

3. Under the “Details” heading:

(a) leave the “Type” drop-down as “Handed in at God”

(b) change the “Notes” field to “Handed in at…” (from “Handed in after…”)

4. Click “Save”.

'''To record withdrawals (hopefully rarely!):'''

1. Click “New Entry”.

2. For each resource that is being withdrawn, enter a negative number in the corresponding box, i.e. a minus sign followed by a number. Multiple resources can be withdrawn at once.

3. Under the “Details” heading:

(a) change the “Type” drop-down to “Handed out at God”

(b) change the “Notes” field to “Handed out at…”

4. Click “Save”.
</box>

====Show entries====

This button is mostly useful for detective work, when someone’s confused or surprised about the quantity of resource in their pack. This is usually because they are ''(or in some cases are not)'' under the effect of some ritual or military action, which you’ll likely be able to dig out of the full history of inventory transactions. Grab a more senior member of crew to talk you through this until you’re confident with it.

====Book out====
This is the button to click when you want to withdraw everything in a player’s inventory without having to fiddle around with the individual numbers. You shouldn’t need to use this very often.
====Not collected====
See ''Break down'' in [[Player Packs- GOD]]

====Transfer====
You’re unlikely to need to use this button. Check with a head of department if you think you do

===Downtime===

[https://www.profounddecisions.co.uk/empire-wiki/Downtime Downtime- Player wiki]

This tab only appears for characters with the Artisan skill. It provides information about which items the character made during downtime between events, and which resources they consumed to make those items.

'''TODO:''' flesh this out more – what Do about it? What information do we give players? What Problems do they Have?

===Bonds===
[https://www.profounddecisions.co.uk/empire-wiki/Create_bond Create bond- Player wiki]

'''TODO:''' what Problems? what Information can we Provide?

===Magic===
[https://www.profounddecisions.co.uk/empire-wiki/Magic Magic- Player wiki]

This tab provides information about magical effects the character is under.

'''TODO:''' what Problems? what Information can we Provide?

===Soul===
[https://www.profounddecisions.co.uk/empire-wiki/Testimony Testimonies- Player wiki]

'''TODO:''' This will show Testimony but…. what else? what do we need to know? what can we tell players under what circumstances? &c.?

===Ribbons===

'''TODO''' Fill out this section
====Bonding items====

====Unbonding items====

====Identifying items====

====Editing items====

===Notes===

'''TODO:''' what for, when to use, how to use
[[Category:GOD manual]]

Character processes

2023-07-07T10:44:00Z

Jmabb:

Character processes

2023-07-07T10:42:43Z

Jmabb: big old page on character processes added!

This page contains an exciting mix of things that players have to do, things that players can ''(and should, if possible)'' do themselves, things we’re happy to do for them, and things ''we'' have to do that players can’t.

'''Players have to:'''
* create new characters
* create new bands

'''Players generally should, but GOD can:'''
* record character retirements or deaths
* check what skills they know
* assign their own skill points
* choose which rituals and recipes to learn from within Imperial lore

'''GOD can:'''
* manually reassign skill points (e.g. for new players, or for access reasons)

'''GOD has to:'''
* perform dead-or-alive checks
* activate new characters
* move characters between nations
* change or swap characters’ Personal Resources
* record that characters have learned rituals or recipes that fall outside Imperial lore

For the processes in this chapter, start by getting to the “Character” tab of the crew interface unless otherwise specified.

===Miscellaneous===

====Creating new characters====

To create a new character, a player needs to log into their PD account on a device connected to the PD Wi-Fi. If they have their own phone or laptop and can connect to the PD Wi-Fi, or can use a player PC, this is ideal, but if necessary and the queue is short enough they can use one of the query PCs.

When creating a new character, the player can join any publicly listed band. If they want to join a secret band, they can only do that in play; from our perspective, that process is described in ('''TODO''' Create Bond). Once the new character has been created, the player should come to the front desk in GOD and ask for the new character to be activated and their new pack to be printed.

====Creating new bands====
To create a new band, a player needs to log into their PD account on a device connected to the PD Wi-Fi. Once the band has been created, there are two ways characters can join:
* If the band is public, new characters can join during the character generation process, by simply selecting the band name from a drop-down list.
* If the band is secret, or the character looking to join is already in play, the only way for them to join is in play, using the ('''TODO''' Create Bond spell per Create Bond.)

====Dead or Alive?====
'''''Note''' that egregores can check whether a character in their nation is dead or alive.''
<box>
1. Get to the “Players” tab of the crew interface.

2. Look up the PID of the character’s player.

3. Click on the “Characters” tab under the player name.

4. Check that the relevant character is a member of the egregore’s nation.

5. If the character status is “Dead”, the character is dead. If the character status is “Retired” or “Played”, the character is alive. Tell the egregore whether the character is dead or alive according to our system (obviously, particularly during and shortly after battles, there may be a delay between the character dying and it getting updated on the database, but egregores should be expecting that).
</box>

===Details===
This section describes the function of the buttons present on the right-hand side of the page on the Details tab under the character name.
====Play character====
This button is only present for a character that has been created but not activated
<box>
1. Click “Play Character”.

2. A pop-up will appear saying something like “Please confirm that you wish to set [character] to played and create their resource and inventory.” Click “Confirm”.

3. A button labelled “Event Pack” will now appear on the right-hand side of the page. Click “Event Pack”.

4. A pop-up will appear saying something like “Please confirm that you wish to book out the inventory for [character] and print them an event pack.” Click “Confirm”.
* '''''Note''': because the character has been newly set to played, you should always see a confirmation that the player envelope and passport have been sent to the print queue. You should never see a message that the envelope and passport were already in the print queue. If you do, something has gone very wrong – get one of the heads of department to come and poke around in the system!''

5. Either ask the player to wait while you assemble their pack (see 9.2 Making up), or ask them to come back in a time frame you have agreed with the heads of department, and make a note of the PID, the time you sent their pack request to the print queue, and the time you told them to come back. Make sure the heads of department have this information.
</box>

====Retiring and killing characters====

''Retiring'' a character leaves them alive but makes them unplayable. ''Killing'' a character changes their status to dead. When players come in to GOD to register a character death, they should hand in any game items that were on their character’s body at the moment they stopped phys-repping the body. (So, for example, if their body was looted after their death but before they stopped phys-repping the body, those items are still in circulation and do not need to be handed in!)

Players can both retire characters and report character deaths themselves, but we’ll often do it for them. If a player has already generated a new character, go ahead and retire or kill their existing active character for them before activating their new character. If they haven’t, feel free to tell them to head to the player PCs (or use one of their own devices connected to the PD Wi-Fi) to report their character death and create their new character, then come back to the front desk to have their new character activated and their new pack prepared.
<box>
The steps are at least straightforward for this one:

1. Click “Retire Character” or “Kill Character” as appropriate.

2. Click “Confirm” in the dialogue box.
</box>

====Edit character====
<box>
1. Enter the PID and press Tab or Enter. (This will automatically take you to the page of the currently active character.)

2. Click “Edit Character” from the buttons on the right-hand side of the page.

3. The only things you should ever change using this dialogue box are the name and the archetype. '''Do not change any other field via this dialogue unless you are being given explicit instructions by a head of department or referee''': some fields can be changed via other menus, and some fields should not be changed at all.
</box>

====Leave band====
Players can leave a band for any reason, but we have to process this for them. ''(Players automatically leave all bands when moving nations).''
<box>
1. Click “Leave Band”.

2. Double-check with the player which of their Banner, Coven, and Sect they wish to leave.

3. Tick the appropriate check boxes.

4. Click “Save”.
</box>

====Move nation====
Before registering a change of nation at GOD, players should have completed roleplay in the field and obtained agreement from the egregore of the nation the character is moving to.
<box>
1. Confirm that the character has performed the appropriate roleplaying with the egregore of the nation they are moving to. This is a key step, but some players aren’t aware of it.

2. Find the page for the player’s character, and click “Move Nation”.

3. In the pop-up, select the new nation from the drop-down.

4. Click “Save”.
</box>
When a character changes nation they ''may'' also wish to change the location of their Personal Resource (see Personal Resources below), but this isn’t a requirement.

====Personal Resources====

'''''For more details'''-[https://www.profounddecisions.co.uk/empire-wiki/Resource#Personal_Resource Personal Resources- Player wiki]''

There are nine types of Personal Resource, listed here along with what a basic (level 1) resource of each type, that is not
subject to any penalties, produces each downtime:
• Business: produces 9 crowns
• Congregation: produce 5 doses of liao; provides 10 votes in the Imperial Synod; '''cannot be owned by crew'''
• Farm: produces 9 crowns
• Fleet: trades to produce items or money, or privateers to produce random resources
• Forest: produces 12 units of one rare material
• Herb garden: produces 14 herbs (2 Bladeroot, 2 Cerulean Mazzarine, 2 Imperial Roseweald, 2 Marrowort, 6 True
Vervain)
• Mana site: produces 7 mana crystals
• Military unit: can be used to enhance an Imperial army, or to produce random resources
• Mine: produces 12 units of one rare metal

There are a number of things players might want to do with their resource, some of which GOD can help with and some of
which we can’t.
====Change resource====
Whether or not we charge people depends on why they want to change resource. If they’re a new player or character, they’re still getting to grips with the game, or they’re not having fun, they can change resource for free. Otherwise, there’s a charge.

'''''Note:''' game crew – crew like GOD whose crewing mostly happens during time-in, rather than, say, the site crew who make things happen before and after time-in – cannot have Congregations as their personal resource. This probably won’t come up, but if you do get a crew member asking to change their resource to a Congregation, call a head of department over.''
<box>
1. Click “New Resource”.

2. In the pop-up that appears, select the desired new resource from the “Type” drop-down.

3. Check whether the player wishes to change the location of their resource, and if so make that change using the “Territory” drop-down.

4. Select one of the Payment radio button options.

5. Click “Save”.
</box>
====Swap resource====
Sometimes two players will want to swap ownership of their resources. Provided you have both players in front of you and they’re both happy with this, go ahead and do it!

This is also how to handle resources that were left by a dead character to another in a will: swap the dead character’s resource with the living character’s resource. You can normally take it on trust that the players are being reasonable here, but if you’re concerned, get a head of department.

(Neither GOD nor referees will register wills out-of-character, nor will the Civil Service register them in character; they’re entirely managed by players, with the sole exceptions of ''(a)'' they need someone in GOD to swap resources over, and ''(b)'' if there’s a dispute about a will, player characters are able to involve the magistrates, who are PD NPC crew.)
<box>
1. Navigate to the character page of one of the players.

2. Confirm that their resource is what they think it should be.

3. Click “Swap Resource”.

4. In the pop-up that appears, enter the other player’s PID in the “Recipient” box and press Enter or Tab, or click “Search”.

5. Confirm with the players that the recipient character name is what they expect. (If not, see Looking up PID's in [[Player accounts]])

6. Select one of the Payment radio button options. ''(For resource swaps, you will almost always need to take payment.)''

7. Click “Save”.
</box>

====Assign Resource====
'''Ignore this button'''. If GOD ever needs to touch it, something has gone wrong – escalate to a head of department so they can handle things.

====Upgrades====

Personal resources can only be upgraded during downtime. This is not something we can do in GOD during an event.

Personal resources can only be upgraded one level per downtime. Upgrading a resource requires Bourse resources (i.e. mithril, weirwood, or white granite). The number of wains required is equal to the level being upgraded to, so upgrading a resource from level 1 to level 2 requires 2 wains of the relevant material; upgrading from level 2 to level 3 requires 3 wains; and so on.

To check what level a resource has been upgraded to, click the resource type under the character details. The resource details will open, likely in a new tab. In the Details tab, next to the heading “Upgrades”, a pair of numbers will be given in the format “2 / 1”.
* The first number indicates the number of upgrades the resource has received. This is likely to be relevant when double-checking that people are about to swap the resources they intended to.
* The second number indicates the effective number of upgrades taking into account any bonuses or penalties. For more detail as to what’s going on for any particular resource, see the “Magic” tab. This information is likely to be relevant if somebody received fewer materials in their player pack than they expected.

===Skills===

There are lots of things relating to skills that players can do for themselves. In general, in this section, use your discretion: if there’s a long queue for the player PCs and a short queue for queries, or the player wants to ask multiple questions and skills are only some of them, or they’re a new player or generally seem like they’d benefit from reassurance, feel free to use your judgement about whether to redirect them or whether to answer their questions yourself. All the step-by-step instructions in this section assume that you are starting from the “Skills” tab of a Character page.

====Miscellaneous information====

* Sometimes players are concerned that their player passport is out-of-date, either because they think GOD crew won’t believe they know how to do things (we can check on the computers if we’re worried), or because they’re concerned they’ll forget what they know. Offer to hand-write the details of their skills on their existing passport (and initial it). As a last resort, offer to print out a new copy of their player passport.
* If a player wants to know how much XP they have to spend: ideally redirect them to someone who can show them how to find this out for themselves at the player PCs.

====Learning new skills====
Characters learn skills by spending skill points, or XP. Characters receive 8 XP on creation, and 1 XP for the first and third event they attend each year. Players can spend XP themselves using player PCs or their own devices (connected to the PD Wi-Fi). If players aren’t sure how to do this themselves – or are unsure how many XP points they have available – ideally they’d be
redirected to the player PCs, if a member of GOD crew is present to explain to them, or show them how to do it. Use your judgement.

'''''Note:''' if you do wind up adding skills for players, be aware that the system lets crew spend more XP than the player actually has available, because it’s very occasionally useful to allow players to “overspend” their XP. You should never be doing this unless you have been told to by a head of department.''
<box>
1. Click “Edit Skills” from the buttons on the right-hand side of the page.

2. Click the “Add Skill” button in the middle of the page, under the “Total Points Available” line.
* Note the appearance of the “Total Points Allocated” line. When the number after the “Total Points Allocated” line is equal to the number of points after the “Total Points Available” line, you have spent all the character’s XP and should not keep adding skills!

3. Choose a skill from the drop-down box labelled “Choose One”.
* Note that some skills require other skills as prerequisites, e.g. the skill “Hero” must be bought before any of the other “Heroic Skills” can be purchased. See the wiki for more information.

4. If necessary, click “Add Skill” again to generate another drop-down box.

5. If at any point you make a mistake, click “Delete” next to the skill you wish to delete (or simply change the dropdown to a skill you intended to add). At any time, you can click “Cancel” at the bottom of the page to discard all your changes and leave the page, or “Reset” to return the page to the state it was in before you began editing it.

6. Read out the list of changes you’ve made to the player to confirm they’re happy.

7. When complete, click “Save” at the bottom of the page.
</box>
'''''Note''' that the interface for players looks different – both in terms of how to get there and in terms of what it looks like once you are there. Watching over our shoulders won’t help them much with sorting themselves out in future!''

====Learning new rituals or recipes for items====

Players can master most rituals (for mages) or learn most recipes for items (for artisans) themselves, at player PCs or using their own devices connected to PD Wi-Fi. Use your discretion.
<box>
To master a ritual that is part of Imperial lore:

1. Click “Edit Rituals” from the buttons on the right-hand side of the page.

2. Find an empty lore slot for the appropriate realm for the ritual, i.e. one with a blank drop-down (“Choose One”) next to it.
* If the player doesn’t know the realm for the ritual, you can look it up on the wiki.
* If the player does not have an empty lore slot, they will need to spend XP on an additional ritual slot for the appropriate realm. You can do this for them now (see Learning new skills above).

3. Select the ritual name from the drop-down box.

4. Click “Save” at the bottom of the page.
</box>
However, when characters learn rituals or recipes that do not form part of Imperial lore, this must be recorded by a member of GOD crew (or sometimes by MattP).
<box>
For mastering a ritual that is not part of Imperial lore:

1. The player must have in their possession the physical “ritual text” (magic bit of paper), which will usually be printed on vellum.

2. Click “Edit Rituals” from the buttons on the right-hand side of the page.

3. Find an “Extra lore” slot with a blank drop-down (“Choose One”) next to it.
* If the player does not have an empty “Extra lore” slot, they will need to spend XP on “Extra ritual”. You can do this for them now (see Learning new skills above).

4. Select the ritual matching the name on the ritual text.

5. Click “Save” at the bottom of the page.

To learn to make items in general:
1. Click “Edit Items” from the buttons on the right-hand side.

2. '''TODO''': complete this, including noting the restrictions on what levels of thing can go where.
</box>
Learning to make an item that is not part of Imperial lore happens rarely. If you’re confused about an item a player is asking about, escalate to the heads of department – they might well need to radio through to plot to ask what’s going on.

====Dropping and forgetting skills====
Players sometimes want to forget skills, rituals, or recipes they already know, for a variety of reasons.
* After a brand new player’s first event, they can retrain as many skills and options as they want to, including all of them, by logging in to their account on the PD website. There’s an enormous amount of lore, and getting your head around it takes time! We can also do this for them at their first event, especially if they’re not having fun.
* After every event a player attends, they can retrain a single skill, crafting option, or pair of rituals, by logging in to their account on the PD website. If a player did not use this option during downtime before an event, they can do it themselves at the event using a player PC or their own device.
* Sometimes a player’s access needs change, e.g. they have spent a lot of XP points on battle skills but can no longer participate in battles. In these cases, we need to remove all their battle skills for them. Err on the side of generosity and believing the player, here – and if in doubt, escalate to more senior crew or heads of department.

In general, if a player wants to forget more than one skill for IC reasons rather than OC reasons (e.g. access reasons, being a brand new player), they’ll need to forget skills gradually, one per event, or find some other in character mechanism (e.g. this has sometimes been possible with magic rituals) – but do escalate if you’re at all unsure.

'''''Note''': if players want to forget all the rituals they’ve mastered, freeing up all their ritual slots, this is possible in-game with the ritual Infant Starts with a Blank Slate. Tell them that a ritual exists for this, and ask them if they’d like to be told the name by you or if they’d rather find it out in play – either is fine!''
<box>
To use a player’s ability to forget one skill, one item recipe, or two mastered rituals per event on their behalf:

1. Click “Drop Skill” from the buttons on the right-hand side of the page.
* You will be taken to the “Retrain Skill” page.
* If the player wishes to retrain a skill:

(a) Click the button labelled “Retrain” next to the skill the player wants to forget.

(b) Click “Save” at the bottom of the page.

– Some skills are prerequisites for others. For example, the skill “Magician” cannot be retrained while a character knows any realm lore. The “Retrain Skill” button won’t appear next to a skill that is a required for other known skills.

* If the player wishes to retrain rituals:
(a) Click “Cancel” at the bottom of the page.

(b) Click “Rituals” from the tabs underneath the character name.

(c) Click “Retrain Ritual” from the buttons on the right-hand side of the page.

(d) Click the button labelled “Retrain” next to up to two rituals the player wants to forget.

(e) Click “Save” at the bottom of the page.

* If the player wishes to retrain an item recipe:
(a) Click “Cancel” at the bottom of the page.

(b) Click “Items” from the tabs underneath the character name.

(c) Click “Retrain Item” from the buttons on the right-hand side of the page.

(d) Click the button labelled “Retrain” next to the item the player wants to forget.

(e) Click “Save” at the bottom of the page.

The player can then relearn skills, rituals, and recipes as normal (see Learning new skills, Learning new rituals or recipes for items above).
</box>
<box>
To forget multiple skills, e.g. for access reasons or for a brand new player, without affecting the player’s ability to forget one skill per downtime:

1. Click “Edit Skills” from the buttons on the right-hand side of the page.

2. Click the button labelled “Delete” next to each skill the player wants to forget.
* Note: this system will let you delete skills that are prerequisites for other skills. For example, you will be able to delete “Magician” without also deleting “Autumn lore”. If in doubt, check the wiki or check in with more senior crew.

3. Click “Save” at the bottom of the page.

To forget rituals:

1. Click “Edit Rituals” from the buttons on the right-hand side of the page.

2. Click the button labelled “Delete” next to each ritual the player wants to forget.

3. Click “Save” at the bottom of the page.

To forget item recipes:

1. Click “Edit Items” from the buttons on the right-hand side of the page.

2. Click the button labelled “Delete” next to each item the player wants to forget.

3. Click “Save” at the bottom of the page.
</box>

'''Ignore the “Edit Dropped Skills” button '''– ''you shouldn’t ever need to use this if you’re not a head of department.''

===Inventory===
In theory, the entire contents of people’s inventories should be “booked out” into their player packs at the beginning of every event. In a small number of cases, this might not happen – if so, any items still in people’s inventories should be listed on the “Inventory” tab under the character name. All the processes in this section assume you’re starting from the Inventory tab unless otherwise specified.

Some frequently asked questions are:
* Can I deposit…? →New Entry
* Can I withdraw…? →New Entry
* I thought my pack was supposed to contain… →Show Entries
'''TODO:''' Actually write this up
====New entry====
Generally players are discouraged from depositing items to their inventory at the event unless they’re using them immediately for a ritual or similar. (See Resource hand-in in [[Player Packs- GOD]])
<box>
'''To record deposits:'''

1. Click “New Entry” from the buttons on the right-hand side of the page. A pop-up will appear.

2. For each resource, enter a positive number in the appropriate box. Multiple resources can be deposited at once.

3. Under the “Details” heading:

(a) leave the “Type” drop-down as “Handed in at God”

(b) change the “Notes” field to “Handed in at…” (from “Handed in after…”)

4. Click “Save”.

'''To record withdrawals (hopefully rarely!):'''

1. Click “New Entry”.

2. For each resource that is being withdrawn, enter a negative number in the corresponding box, i.e. a minus sign followed by a number. Multiple resources can be withdrawn at once.

3. Under the “Details” heading:

(a) change the “Type” drop-down to “Handed out at God”

(b) change the “Notes” field to “Handed out at…”

4. Click “Save”.
</box>

====Show entries====

This button is mostly useful for detective work, when someone’s confused or surprised about the quantity of resource in their pack. This is usually because they are ''(or in some cases are not)'' under the effect of some ritual or military action, which you’ll likely be able to dig out of the full history of inventory transactions. Grab a more senior member of crew to talk you through this until you’re confident with it.

====Book out====
This is the button to click when you want to withdraw everything in a player’s inventory without having to fiddle around with the individual numbers. You shouldn’t need to use this very often.
====Not collected====
See ''Break down'' in [[Player Packs- GOD]]

====Transfer====
You’re unlikely to need to use this button. Check with a head of department if you think you do

===Downtime===

[https://www.profounddecisions.co.uk/empire-wiki/Downtime Downtime- Player wiki]

This tab only appears for characters with the Artisan skill. It provides information about which items the character made during downtime between events, and which resources they consumed to make those items.
'''TODO:''' flesh this out more – what Do about it? What information do we give players? What Problems do they Have?

===Bonds===
[https://www.profounddecisions.co.uk/empire-wiki/Create_bond Create bond- Player wiki]
'''TODO:''' what Problems? what Information can we Provide?

===Magic===
[https://www.profounddecisions.co.uk/empire-wiki/Magic Magic- Player wiki]

This tab provides information about magical effects the character is under.

'''TODO:''' what Problems? what Information can we Provide?
===Soul===
[https://www.profounddecisions.co.uk/empire-wiki/Testimony Testimonies- Player wiki]
'''TODO:''' This will show Testimony but…. what else? what do we need to know? what can we tell players under what circumstances? &c.?

===Ribbons===
'''TODO''' Fill out this section
====Bonding items====

====Unbonding items====

====Identifying items====

====Editing items====

===Notes===
'''TODO:''' what for, when to use, how to use

Player accounts

2023-07-07T09:28:13Z

Jmabb: player account processes added

For the processes in this chapter, start by getting to the “Players” tab of the crew interface.

===Looking up PID's===

<box>
1. Click “Search”. This will bring up a dialogue box with more options.

2. Enter one of surname, forename, or e-mail address, preferably the combination of “easiest” and “most unusual”. (This is usually surname. Get them to spell it. You will probably need to ask them to repeat themselves multiple times. Optionally, ask them to write it down for you on your notepad.)
* The Search function returns “and” not “or” – so if you search for “Alex Brown” you will get results for everyone with a first name that contains “Alex” AND everyone with a surname that contains “Brown”.

3. Scroll through the results to find likely candidates.
* If there’s more than one result with the same first name and surname, you will need to click through to the accounts and ask the player to provide additional information to help you identify the correct profile. This might be age, login name, number plate, or postcode.

4. If the player wanted to know their PID, tell them what it is and offer to write it down for them. If you needed to know their PID, work out whether you need to make a note of it (e.g. are you looking them up because you need to know so you can enter a ritual into the database, or are you just trying to activate a new character?) and then do so if appropriate
</box>

===Resetting passwords===
<box>

1. Enter the player’s PID and press Tab or Enter. (If the player doesn’t know their PID, see Looking up PIDs above).

2. Satisfy yourself that the account you are looking at belongs to the person in front of you. For example:
* can they tell you their full name or any other personal details?
* can they tell you the name of their character?
* can they give you details about their character’s skills or personal resource?
3. Click “Reset Password” from the buttons down the right-hand side of the screen.

4. Click “Confirm” in the dialogue box that pops up.

5. Show the player their username (“Login” on the Details tab) and new password (in the pop-up). Offer to write these down for them.

6. Check that the player knows how to do whatever it is they want to do.

7. Direct the player to the player PCs
</box>

===Setting up proxies===

'''Note''' ''that this is not the same system as in-character proxying.''

In general, setting up out-of-character proxies is not something we should do at events – people should e-mail admin@profounddecisions.co.ukbetween events with their PID and the PIDs of anyone they want to nominate as proxies to deal with GOD for them. However, if the person who wants to give permission to someone to proxy for them is present, you can add a proxy to their
account. ''(If the person who wants to nominate a new proxy can’t make it to the GOD tent, e.g. because they’re disabled, escalate to a head of department.)''

<box>
1. Enter the PID of the player who wants to nominate a proxy or proxies, and press Tab or Enter. (If the player doesn’t know their PID, see Looking up PIDs above).
2. Satisfy yourself that the account you are looking at belongs to the person in front of you. For example:
* can they tell you their full name or any other personal details?
* can they tell you the name of their character?
* can they give you details about their character’s skills or personal resource?
3. Click “Add Proxy” from the buttons down the right-hand side of the page.

4. If the player knows the PID of the person they wish to nominate as a proxy, Enter it in the PID field, and press Tab or Enter.
* If the name that appears next to the “Search” button is correct, click “Add Proxy”.
* Repeat for any other proxies.
5. If the player does not know the PID of the person they wish to nominate as a proxy, see Looking up PIDs above.
</box>

===Duplicate accounts===

Occasionally we find players with duplicate accounts. '''These always need Matt Pennington to merge the accounts.'''
<box>
If you come across multiple accounts for the same person:
* If it needs dealing with promptly at the event (e.g. you’re trying to process a booking or generate a character pack, and the character is on one account and the booking is on a different account), either raise it with Matt Pennington yourself, or pass it over to someone with a radio to raise with him.
* If it needs dealing with promptly at the event and you can’t get through to Matt, raise it up the GOD management chain and we’ll find some temporary workaround.
* If it doesn’t need dealing with at the event, make sufficient notes that you’ll be able to identify the accounts involved, and pass up the management chain to handle after the event; there’s normally a small handful of these, so we’ll collate them and pass them to Matt to fix up between events.
</box>

===Adding notes===
'''TODO''' ''Needs writing up''

===Test of arms and Test of citizenship===
'''TODO: Update, as apparently the academy are recording citizenship themselves these days, and just sending folk to GOD to select their resource and pick up their new goodies.'''
<box>
A player who has just passed their Test of Arms or Test of Citizenship will present a certificate from the Academy. To record that they have passed these tests:

1. Enter the PID of the player and press Tab or Enter. (This might be on the certificate, but if it isn’t and the player doesn’t know it, see Looking up PIDs. above)

2. Click “Edit Empire Status” from the buttons down the right-hand side of the page.

3. Tick “Empire Citizen” or “Empire Warrior”, as appropriate.

4. Click “Save Details”.
</box>
If the player is a new Citizen, encourage them to spend their skill points/XP, select a new resource, and then print (see [[printing]]) and make up their pack (see [[Player Packs- GOD]]). Consider encouraging them to spend their skills with you instead of going to the player PCs, depending on what the queues are like – ''use your judgement.''

'''TODO: Process for adding a resource and generating starting materials'''

[[Category:GOD manual]]

Bookings

2023-07-06T11:42:36Z

Jmabb:

===Bookings taken at site entrance===

The process for taking bookings at the site entrance is mostly not one GOD is involved with, but it’s outlined here for context:

1. The gate team take a payment from someone arriving on site, and note down the player’s details as best they can.

2. The gate team send a runner from the gate to the Matt Cave on a semi-regular basis to drop off cash and paperwork. (Occasionally we get asked to send a runner ourselves, depending on who can spare the crew more easily.)

3. Graeme, in the Matt Cave, processes the paperwork and books players in.

4. The GOD heads of department do intermittent print runs of new character packs, which will get made up and put in the matrix per [[Player Packs- GOD]].

If someone appears and tells you they’ve paid on the gate, this means their pack may be in the matrix ready for them to collect, but that relies on them having got through this entire process.

<box>
What you need to do with someone who turns up at GOD who has paid at the gate depends on a variety of details:
* Check they’ve actually paid. They should have a receipt they can show you. Sometimes players will say something like “I’m here for a gate booking”, meaning they’ve already paid and they want to pick up their pack, and sometimes they’ll say something more-or-less identical but meaning that they want to make a booking now, in which case see '''Front desk bookings'''.
* Check they have an account. Sometimes the first contact someone has with PD will be when they turn up at the gate, and we need them to have an account before we can help them. If they don’t have an account, send them to create one on the player PCs or using their own device connected to the PD Wi-Fi. Once they’ve done that, fill out a query form, add it to the HoD Player Waiting inbox, and send them to the heads of department to sort out.
* Check when they paid, and check with the heads of department how up-to-date we are with gate bookings. If we’re sufficiently up-to-date, they can just be treated like any other player coming to pick up their pack. If not, depending on the backlog, we might be able to sort their pack straight away, or we might need to tell them to come back later.
</box>

===Front desk bookings===

'''''The Simple case'''''

This should cover the majority of cases where someone wants to buy a ticket in GOD, that is: they’re an adult who needs either a crew or gate ticket for the current event, they already have an account, they’re buying the ticket for themselves, and they’re paying the balance due immediately. For more complex cases, refer to ''The complex case.''

<box>

To create a booking, once you’re logged in to the website and you’ve clicked “Crew” from the home page:

1. Click “GOD” in the top bar, then click “Gate Booking”

2. Ask the player if they know their PID.

* If they do, put their PID in the PID box, then press Tab or Enter or click somewhere else on the page. Confirm the player’s name on your screen matches what they tell your their name is.
* If they don’t know their PID, click the “Search” button, and get some information from the player to be able to find their details; surname is normally best. Find and select the relevant player.

3. Check with the player which character they want to play, and select the character name from the “Character” drop-down menu.

4. Select the appropriate ticket type from the “Ticket” drop-down. This will normally be “Gate Booking” unless they’re crew, in which case select “Crew”.

5. If it’s a gate booking rather than a crew booking, ask the player if they’re entitled to a concession.
* If they’re not entitled to a concession, select “No” from the “Concession” drop-down.
* If they’re entitled to a concession and show you evidence of that, select “Yes” from the “Concession” drop-down.
* If they claim they’re entitled to a concession but aren’t able to show evidence, leave the Concession checkboxes blank. Tell them that you’ll need to charge full price, but that if they email in after the event, PD will refund the concession discount. More detail in [[Confirming concessions]]

6. Check how the player wants to pay:
* For cash, take the cash off them, check it’s the right amount, hand the cash off to a head of department or whoever has the cash box at the time, and select “Cash” in the Method dropdown.
* For card payments, follow the instructions at ''Operating the card reader'' in [[Taking payments]], and once the payment has been processed, select “Sumup” in the Method dropdown.
* If the player isn’t able or willing to pay for some reason, escalate to a head of department.

7. Click “Create Booking”

8. Check with the heads of department whether we’re creating packs on demand or if there’s a queue, and either have the player wait while you prepare their pack per 9.2 Making up, or come back later and collect their pack from the Matrix.

</box>

'''''The Complex case'''''

Bookings following this process should be relatively rare, but it allows us to sell any type of ticket (e.g. children’s tickets), to purchase multiple tickets at once, and to process tickets that one person is buying on someone else’s behalf (e.g. parents buying for their children, or traders paying for tickets for their crew).

<box>
To create bookings, once you’re logged in to the website and you’ve clicked “Crew” from the home page:
1. Click “Players” in the top bar.

2. Ask the player if they know their PID. If you have one person buying tickets for someone else, it’s the PID of the buyer we care about at this point, and since it’s their account we’re charging, their should either be present or the person you’re talking to should be an authorised proxy for them.
* If they do, put their PID in the PID box, then press Tab or Enter or click somewhere else on the page. Confirm the player’s name on your screen matches what they tell your their name is.
* If they don’t know their PID, click the “Search” button, and get some information from the player to be able to find their details; surname is normally best. Find and select the relevant player.
3. Click the “Bookings” tab, then click “Create Booking”

4. The “Purchase Details” section should already be filled out correctly, with the PID and name of the player buying the tickets, today’s date, and no introducer.

5. Change the Event drop-down if necessary (this should very rarely be necessary; we only take bookings for the current event at the event)

6. In the Ticket drop-down, select the appropriate ticket type. This will normally be “Gate Booking”, but may be “Crew” or one of the children’s tickets. Don’t select “Early Booking” or “Late Booking” without first checking with a head of department; don’t select “Crew” unless the person is actually crew.

7. In the Recipient box, select the person who is receiving the ticket. This will normally be the same person as is buying the ticket, but might be different if, for example, this is a ticket being bought by a parent for a child, or a ticket being bought by a trader for one of their staff.

8. Check with the player which character they want to be playing, and select it in the Character drop-down.

9. Never select the Complimentary checkbox unless either (a) you’ve been told to by a head of department, or (b) this is a booking for a child and all their responsible adults are crew.

10. If it’s a gate booking, ask the player if they’re entitled to a concession.
* If they’re not entitled to a concession, leave the Concession checkboxes blank.
* If they’re entitled to a concession and show you evidence, select both “Concession” and “Concession Seen”. (Acceptable concession evidence examples in [[Confirming concessions]])
* If they claim they’re entitled to a concession but aren’t able to show evidence, leave the Concession checkboxes blank. Tell them that you’ll need to charge full price, but that if they email in after the event, PD will refund the concession discount.

'''''Note:''' in GOD, you should never select one of the Concession checkboxes but not the other.''

11. Check that the amount in the “Amount” box is as expected. Don’t change this without first checking with a head of department.

12. Click “Add Ticket”.

13. If the buyer wants to buy multiple tickets at the same time, go back to step 5.

14. Click “Create Booking”.

15. You should now be returned to the player bookings page; note the balance at the top of the table, then click “Take Payment”.

16. Enter the appropriate amount in the “Amount” box.

17. Ask the player how they want to pay:
* For cash: take the cash off them, check the right amount, and select “Cash” in the Method dropdown. Hand the cash to a head of department (or whoever is in charge of the real-world cash box).
* For card payments: follow the instructions at Operating the card reader in [[Taking payments]] . Once the payment has been processed, select “Sumup” in the Method dropdown.
* If the player isn’t able or willing to pay for some reason, escalate to a head of department.

18. Don’t change any of the other values without first checking with a head of department: PID should already be correct, we never use any of the other payment methods, and the date and VAT rate will be automatically correct.

19. Click “Save”.

</box>

===Day Tickets===

Very occasionally, someone wants to attend for just one day of the event, normally turning up in the morning and leaving in the evening. They can, and they don’t have to pay full price. If someone asks for this, pass them off to one of the heads of department.

===Trader Bookings===

In principle, trader bookings are no different from player bookings: we expect traders to pay for tickets at the regular player prices. The two key differences are that '''(a)''' some of our traders also book and pay for trader pitches, and '''(b)''' some of our traders have their own crew, who also have regular player tickets, but which will typically be paid for by the trader.

If you have a trader wanting to make a pitch booking at GOD, they’re almost certainly far too late- Escalate to a head of department.

If you have a trader wanting to buy tickets for some of their crew, process that as a normal booking at the gate price per '''''The Complex case'''''. The trader may already have funds in their account to pay for the ticket, in which case there will be no need to take payment. If they don’t, they may want to leave the debt on their account rather than paying immediately; that’s probably fine, but check with a head of department (who will probably want to check with Graeme).

===Caterer Bookings===

Caterer bookings are always handled by Graeme. If you have someone from one of the caterers looking to make a booking or get a character pack or similar, escalate to a head of department or to Graeme directly

===Converting Open Tickets===

PD sell “open tickets” which aren’t tied to a particular event. Occasionally people will come to GOD saying they’re booked, but it’ll turn out they haven’t converted their open ticket to a booking for the specific event. If this happens, there’s a £10 charge for converting an open ticket to a regular booking at the event. '''Escalate this to a head of department''', as it’s reasonably likely to become a complaint.

===Price List===

In case you need them, here’s the full list of prices as of 2023. PD honours prices from when bookings were first made provided they were paid for promptly, so if a player made a booking a while ago, the correct price might not be the one below:
<box>
* Adult early booking: £75 (£55 concession)
* Adult late booking: £80 (£60 concession)
* Adult gate booking: £90 (£70 concession)
* 16/17 year olds: as adult prices, but will generally be eligible for a concession
* 11–15 year olds: £20 (£10 if a responsible adult gets a concession)
* 7–10 year olds: £10 (£5 if a responsible adult gets a concession)
* Under-7s: free
* Day tickets: ask a head of department (who will probably need to ask Graeme)
</box>

''Players may also have a £15 credits on their account if they were introduced by another player or have introduced another player. This doesn’t affect the ticket price directly.''

For day tickets, the most common prices are:
<box>
* Adult full price for all Saturday: £60
* Adult concession for all Saturday: £45
* Adult full price for Friday or Sunday: £45
* Adult concession for Friday or Sunday: £35
</box>

The rules for working out the day ticket prices (ask one of the heads of department if you’re not sure):

1. Find out how long the player is at the event: the categories we care about are broadly “a full day” (probably all Saturday),
“less than that” (e.g. Friday only, or Saturday but leaving by 6pm) or “more than that” (e.g. arriving Saturday morning
and staying the full event.

2. Find out the normal gate price for the full event, e.g. £90 for adult full price, £70 adult concession.

3. For the “a full day” category, apply a 33% discount. For the “less than that” category, apply a 50% discount. For the
“more than that” category, charge full price.

4. Round to £5.

===Thursday Nights===

There’s a £5 charge for players people staying on Thursday night. The vast majority of the time, this will be handled by the folk on the gate, but we do occasionally get people turning up at GOD to pay.

If someone wants to pay for Thursday night camping:

* If they’re paying by cash, pass the cash off to a head of department or to whoever has the cash box. Make sure it’s tallied that the money is for Thursday night camping – that cash needs to be kept (or at least counted) separately – and '''do not record it on the player account.'''
* If they’re paying by card, follow the instructions at Operating the card reader in [[Taking payments]]. Again, '''do not record the payment on the player account'''.

===Lost Bookings===

So you have a player who thinks they should be booked, but as best you can tell they don’t have a pack anywhere, or you otherwise need to work out what’s going on with their booking. Here’s the process for that:
<box>
First of all, work out whether the database thinks they’re actually booked. Once you’re logged into the website and have
clicked the “Crew” link…

1. Click “Player” across the top bar.

2. Ask the player if they know their PID.

* If they do, put their PID in the PID box, then press Tab or Enter or click somewhere else on the page. Confirm the player’s name on your screen matches what they tell your their name is.
* If they don’t know their PID, click the “Search” button, and get some information from the player to be able to find their details; surname is normally best. Find and select the relevant player.

3. Check you’ve actually found the relevant player, rather than just a different player with the same or a similar name. Click the “Characters” tab and get them to verify the name of one of their characters, or get them to give you the registration plate of their car if there’s one on the account, or their login username.

4. Click the “Events” tab. This is the definitive list of what events someone actually has tickets for. If the current event (“Winter” for E1, “Spring” for E2, “Summer” for E3, “Autumn” for E4) is listed, the system thinks they have a booking. If the current event isn’t listed, we don’t have a booking for them.

From here, next steps will depend on whether we have a booking for them at all.

If the system does think there’s a booking for this player:

1. Find out when they booked. If they didn’t book until after the start of the packing weekend, and the issue is you can’t find a pack for them, it’s likely we just haven’t got it ready yet; see ''Bookings taken at the site entrance'' above. If we just haven’t had chance to make a pack up for them yet, they’ll need to come back later. The “Date” column should tell you when the system thinks they booked.

2. If we can’t find a pack for them and we should have made one up already, we’ll just need to make one up anew. Take down the player’s details, and either get a pack made up immediately or add it to the queue and get them to come back later. (See Making up packs in [[Player Packs- GOD]])

If the system does not think there’s a booking for this player, the first question has to be why, which will hopefully point us to what to do about it.

* Does the player have any open bookings? You can see these on the “Events” tab as bookings that don’t have a ticket type or event name listed, and also on the “Bookings” tab. If the player has an open booking that they wanted to convert to a regular booking, see Converting open tickets above.

* Does the player think someone else booked for them? If you can find details of the other person who made the booking, the booking should show up on the “Events” tab for the person who received the ticket, and the “Bookings” tab for the person who made and paid for the booking. If there’s an issue around this, you’ll probably need to escalate to a head of department.
* Is there a booking listed on the “Bookings” tab that’s crossed out? If so, that indicates the booking was cancelled
for some reason. Possibly the player cancelled it themselves; possibly PD cancelled it for some reason for them. There may be a note explaining what’s going on on the “Notes” and/or “Audit” tabs, but this will also probably need escalating to a head of department.
</box>
[[Category:GOD manual]]

Bookings

2023-07-06T11:36:02Z

Jmabb:

Bookings

2023-07-06T11:35:15Z

Jmabb:

===Bookings taken at site entrance===

The process for taking bookings at the site entrance is mostly not one GOD is involved with, but it’s outlined here for context:

1. The gate team take a payment from someone arriving on site, and note down the player’s details as best they can.

2. The gate team send a runner from the gate to the Matt Cave on a semi-regular basis to drop off cash and paperwork. (Occasionally we get asked to send a runner ourselves, depending on who can spare the crew more easily.)

3. Graeme, in the Matt Cave, processes the paperwork and books players in.

4. The GOD heads of department do intermittent print runs of new character packs, which will get made up and put in the matrix per [[Player Packs- GOD]].

If someone appears and tells you they’ve paid on the gate, this means their pack may be in the matrix ready for them to collect, but that relies on them having got through this entire process.

<box>
What you need to do with someone who turns up at GOD who has paid at the gate depends on a variety of details:
* Check they’ve actually paid. They should have a receipt they can show you. Sometimes players will say something like “I’m here for a gate booking”, meaning they’ve already paid and they want to pick up their pack, and sometimes they’ll say something more-or-less identical but meaning that they want to make a booking now, in which case see '''Front desk bookings'''.
* Check they have an account. Sometimes the first contact someone has with PD will be when they turn up at the gate, and we need them to have an account before we can help them. If they don’t have an account, send them to create one on the player PCs or using their own device connected to the PD Wi-Fi. Once they’ve done that, fill out a query form, add it to the HoD Player Waiting inbox, and send them to the heads of department to sort out.
* Check when they paid, and check with the heads of department how up-to-date we are with gate bookings. If we’re sufficiently up-to-date, they can just be treated like any other player coming to pick up their pack. If not, depending on the backlog, we might be able to sort their pack straight away, or we might need to tell them to come back later.
</box>

===Front desk bookings===

'''''The Simple case'''''

This should cover the majority of cases where someone wants to buy a ticket in GOD, that is: they’re an adult who needs either a crew or gate ticket for the current event, they already have an account, they’re buying the ticket for themselves, and they’re paying the balance due immediately. For more complex cases, refer to ''The complex case.''

<box>

To create a booking, once you’re logged in to the website and you’ve clicked “Crew” from the home page:

1. Click “GOD” in the top bar, then click “Gate Booking”

2. Ask the player if they know their PID.

* If they do, put their PID in the PID box, then press Tab or Enter or click somewhere else on the page. Confirm the player’s name on your screen matches what they tell your their name is.
* If they don’t know their PID, click the “Search” button, and get some information from the player to be able to find their details; surname is normally best. Find and select the relevant player.

3. Check with the player which character they want to play, and select the character name from the “Character” drop-down menu.

4. Select the appropriate ticket type from the “Ticket” drop-down. This will normally be “Gate Booking” unless they’re crew, in which case select “Crew”.

5. If it’s a gate booking rather than a crew booking, ask the player if they’re entitled to a concession.
* If they’re not entitled to a concession, select “No” from the “Concession” drop-down.
* If they’re entitled to a concession and show you evidence of that, select “Yes” from the “Concession” drop-down.
* If they claim they’re entitled to a concession but aren’t able to show evidence, leave the Concession checkboxes blank. Tell them that you’ll need to charge full price, but that if they email in after the event, PD will refund the concession discount. More detail in [[Confirming concessions]]

6. Check how the player wants to pay:
* For cash, take the cash off them, check it’s the right amount, hand the cash off to a head of department or whoever has the cash box at the time, and select “Cash” in the Method dropdown.
* For card payments, follow the instructions at ''Operating the card reader'' in [[Taking payments]], and once the payment has been processed, select “Sumup” in the Method dropdown.
* If the player isn’t able or willing to pay for some reason, escalate to a head of department.

7. Click “Create Booking”

8. Check with the heads of department whether we’re creating packs on demand or if there’s a queue, and either have the player wait while you prepare their pack per 9.2 Making up, or come back later and collect their pack from the Matrix.

</box>

'''''The Complex case'''''

Bookings following this process should be relatively rare, but it allows us to sell any type of ticket (e.g. children’s tickets), to purchase multiple tickets at once, and to process tickets that one person is buying on someone else’s behalf (e.g. parents buying for their children, or traders paying for tickets for their crew).

<box>
To create bookings, once you’re logged in to the website and you’ve clicked “Crew” from the home page:
1. Click “Players” in the top bar.

2. Ask the player if they know their PID. If you have one person buying tickets for someone else, it’s the PID of the buyer we care about at this point, and since it’s their account we’re charging, their should either be present or the person you’re talking to should be an authorised proxy for them.
* If they do, put their PID in the PID box, then press Tab or Enter or click somewhere else on the page. Confirm the player’s name on your screen matches what they tell your their name is.
* If they don’t know their PID, click the “Search” button, and get some information from the player to be able to find their details; surname is normally best. Find and select the relevant player.
3. Click the “Bookings” tab, then click “Create Booking”

4. The “Purchase Details” section should already be filled out correctly, with the PID and name of the player buying the tickets, today’s date, and no introducer.

5. Change the Event drop-down if necessary (this should very rarely be necessary; we only take bookings for the current event at the event)

6. In the Ticket drop-down, select the appropriate ticket type. This will normally be “Gate Booking”, but may be “Crew” or one of the children’s tickets. Don’t select “Early Booking” or “Late Booking” without first checking with a head of department; don’t select “Crew” unless the person is actually crew.

7. In the Recipient box, select the person who is receiving the ticket. This will normally be the same person as is buying the ticket, but might be different if, for example, this is a ticket being bought by a parent for a child, or a ticket being bought by a trader for one of their staff.

8. Check with the player which character they want to be playing, and select it in the Character drop-down.

9. Never select the Complimentary checkbox unless either (a) you’ve been told to by a head of department, or (b) this is a booking for a child and all their responsible adults are crew.

10. If it’s a gate booking, ask the player if they’re entitled to a concession.
* If they’re not entitled to a concession, leave the Concession checkboxes blank.
* If they’re entitled to a concession and show you evidence, select both “Concession” and “Concession Seen”. (Acceptable concession evidence examples in [[Confirming concessions]])
* If they claim they’re entitled to a concession but aren’t able to show evidence, leave the Concession checkboxes blank. Tell them that you’ll need to charge full price, but that if they email in after the event, PD will refund the concession discount.

'''''Note:''' in GOD, you should never select one of the Concession checkboxes but not the other.''

11. Check that the amount in the “Amount” box is as expected. Don’t change this without first checking with a head of department.

12. Click “Add Ticket”.

13. If the buyer wants to buy multiple tickets at the same time, go back to step 5.

14. Click “Create Booking”.

15. You should now be returned to the player bookings page; note the balance at the top of the table, then click “Take Payment”.

16. Enter the appropriate amount in the “Amount” box.

17. Ask the player how they want to pay:
* For cash: take the cash off them, check the right amount, and select “Cash” in the Method dropdown. Hand the cash to a head of department (or whoever is in charge of the real-world cash box).
* For card payments: follow the instructions at Operating the card reader in [[Taking payments]] . Once the payment has been processed, select “Sumup” in the Method dropdown.
* If the player isn’t able or willing to pay for some reason, escalate to a head of department.

18. Don’t change any of the other values without first checking with a head of department: PID should already be correct, we never use any of the other payment methods, and the date and VAT rate will be automatically correct.

19. Click “Save”.

</box>

===Day Tickets===

Very occasionally, someone wants to attend for just one day of the event, normally turning up in the morning and leaving in the evening. They can, and they don’t have to pay full price. If someone asks for this, pass them off to one of the heads of department.

===Trader Bookings===

In principle, trader bookings are no different from player bookings: we expect traders to pay for tickets at the regular player prices. The two key differences are that '''(a)''' some of our traders also book and pay for trader pitches, and '''(b)''' some of our traders have their own crew, who also have regular player tickets, but which will typically be paid for by the trader.

If you have a trader wanting to make a pitch booking at GOD, they’re almost certainly far too late- Escalate to a head of department.

If you have a trader wanting to buy tickets for some of their crew, process that as a normal booking at the gate price per '''''The Complex case'''''. The trader may already have funds in their account to pay for the ticket, in which case there will be no need to take payment. If they don’t, they may want to leave the debt on their account rather than paying immediately; that’s probably fine, but check with a head of department (who will probably want to check with Graeme).

===Caterer Bookings===

Caterer bookings are always handled by Graeme. If you have someone from one of the caterers looking to make a booking or get a character pack or similar, escalate to a head of department or to Graeme directly

===Converting Open Tickets===

PD sell “open tickets” which aren’t tied to a particular event. Occasionally people will come to GOD saying they’re booked, but it’ll turn out they haven’t converted their open ticket to a booking for the specific event. If this happens, there’s a £10 charge for converting an open ticket to a regular booking at the event. '''Escalate this to a head of department''', as it’s reasonably likely to become a complaint.

===Price List===

In case you need them, here’s the full list of prices as of 2023. PD honours prices from when bookings were first made provided they were paid for promptly, so if a player made a booking a while ago, the correct price might not be the one below:
<box>
* Adult early booking: £75 (£55 concession)
* Adult late booking: £80 (£60 concession)
* Adult gate booking: £90 (£70 concession)
* 16/17 year olds: as adult prices, but will generally be eligible for a concession
* 11–15 year olds: £20 (£10 if a responsible adult gets a concession)
* 7–10 year olds: £10 (£5 if a responsible adult gets a concession)
* Under-7s: free
* Day tickets: ask a head of department (who will probably need to ask Graeme)
</box>

''Players may also have a £15 credits on their account if they were introduced by another player or have introduced another player. This doesn’t affect the ticket price directly.''

For day tickets, the most common prices are:
<box>
* Adult full price for all Saturday: £60
* Adult concession for all Saturday: £45
* Adult full price for Friday or Sunday: £45
* Adult concession for Friday or Sunday: £35
</box>

The rules for working out the day ticket prices (ask one of the heads of department if you’re not sure):

1. Find out how long the player is at the event: the categories we care about are broadly “a full day” (probably all Saturday),
“less than that” (e.g. Friday only, or Saturday but leaving by 6pm) or “more than that” (e.g. arriving Saturday morning
and staying the full event.

2. Find out the normal gate price for the full event, e.g. £90 for adult full price, £70 adult concession.

3. For the “a full day” category, apply a 33% discount. For the “less than that” category, apply a 50% discount. For the
“more than that” category, charge full price.

4. Round to £5.

===Thursday Nights===

There’s a £5 charge for players people staying on Thursday night. The vast majority of the time, this will be handled by the folk on the gate, but we do occasionally get people turning up at GOD to pay.

If someone wants to pay for Thursday night camping:

* If they’re paying by cash, pass the cash off to a head of department or to whoever has the cash box. Make sure it’s tallied that the money is for Thursday night camping – that cash needs to be kept (or at least counted) separately – and '''do not record it on the player account.'''
* If they’re paying by card, follow the instructions at 14.3.3 Operating the card reader. Again, '''do not record the payment on the player account'''.
[[Category:GOD manual]]

Confirming concessions

2023-07-06T11:29:20Z

Jmabb: Created page with "'''From the wiki:''' ''Anyone who is a full time student, a full time member of the armed services, a pensioner, or receives state benefits as their main income is eligible fo..."

'''From the wiki:''' ''Anyone who is a full time student, a full time member of the armed services, a pensioner, or receives state benefits as their main income is eligible for the concession on the ticket price.''

Concessions are applied on a per-booking basis. If someone books three events in one go, they will only have to show proof that they’re eligible to receive a concession for the first event. If they book three events separately, however, they’ll have to show proof for all three events.

PD generally wants to err on the side of being generous with concessions. In particular, if players booked for events before The Long Dark, and were eligible for a concession at the time of the booking but aren’t any longer (e.g. they were students but have now graduated), those concessions are being honoured. If they’re really keen to, they’re very welcome to make a donation to PD (see Taking donations in [[Taking payments]]) to make up the difference in ticket price, but there’s absolutely no obligation to do so
<box>
'''To confirm a concession, once you’re logged in to the website and you’ve clicked “Crew” from the home page:'''

1. Click “GOD”. You will land on the “Book-in Baggy” page.

2. Click the “Concessions” tab in the top bar.

3. Enter the player’s PID in the relevant box and press Tab or Enter on the keyboard. If they don’t know their PID, you can look it up or try searching from this page using their first name, surname, or e-mail.

4. If their account does not come up in the Concessions search results, look up their PID. If any new PID also does not come up in the Concessions search results, direct them to the main Matrix.

5. If their account comes up in search results, ask to see proof of concession.
* For children under the age of 18, this might be a college ID card, or you might need to confirm that their parent is eligible for a concession due to falling into one of the categories above.
* For students, you can ask to see their university or college ID card, their NUS card, or to see them logged into their student e-mail account.
* For members of the armed forces, you can ask to see their ID cards.
* For people receiving a pension, this information is likely to be present in their player profile. You can also ask to see photo ID that includes their date of birth, or a letter about their pension.
* For people receiving state benefits, you can ask to see a letter from the DWP, or a screenshot of their Universal credit account or bank statement.

6. If you are satisfied that the player is entitled to the concessionary rate, click “Confirm”.

7. If you are unsure whether the player is entitled to the concessionary rate, ask a head of department for advice.

8. If a player is unable to show proof of entitlement, and can’t e.g. go to fetch it from a tent and then come back to show it, click “Cancel”.
* If the player is no longer entitled to a concession and wishes to pay the difference in ticket price now, select the appropriate option for the form of payment, take the payment, and click “Save”.
* If the player wants to e-mail in proof of entitlement after the event, note this down along with their PID and name, select “No payment taken from player”, and click “Save”. Pass the PID and name to the heads of department at some point, so they can follow up after the end of the event.

9. The player’s pack should (hopefully!) be in the Concessions Matrix. Hand it over! :)
* If not, follow the procedure for Missing packs in [[Player Packs- GOD]]

''Notes:''
*If the player is likely to be entitled to concessionary tickets forever (e.g. they’re over the age of 60 or they’re permanently disabled), we can set a “permanent concession” flag on their account, so they don’t need to keep providing proof of their eligibility. If you think that’s appropriate, raise with a head of department.
* Hand the list of players who need to e-mail in proof of their entitlement to concession to the heads of department.
* The network sometimes goes on. This doesn’t mean you can’t confirm concessions! If you have the player’s pack in the Concessions matrix and they show you acceptable proof of entitlement, write down their PID in a notebook so you can run through and confirm it once the network is back up. Similarly, you can note down PIDs for players whose concessions you need to cancel, if they couldn’t show proof of concession but wanted to pick up their pack anyway
</box>
[[Category:GOD manual]]

Bookings

2023-07-06T11:21:35Z

Jmabb: adding links

===Bookings taken at site entrance===

The process for taking bookings at the site entrance is mostly not one GOD is involved with, but it’s outlined here for context:

1. The gate team take a payment from someone arriving on site, and note down the player’s details as best they can.

2. The gate team send a runner from the gate to the Matt Cave on a semi-regular basis to drop off cash and paperwork. (Occasionally we get asked to send a runner ourselves, depending on who can spare the crew more easily.)

3. Graeme, in the Matt Cave, processes the paperwork and books players in.

4. The GOD heads of department do intermittent print runs of new character packs, which will get made up and put in the matrix per [[Player Packs- GOD]].

If someone appears and tells you they’ve paid on the gate, this means their pack may be in the matrix ready for them to collect, but that relies on them having got through this entire process.

<box>
What you need to do with someone who turns up at GOD who has paid at the gate depends on a variety of details:
* Check they’ve actually paid. They should have a receipt they can show you. Sometimes players will say something like “I’m here for a gate booking”, meaning they’ve already paid and they want to pick up their pack, and sometimes they’ll say something more-or-less identical but meaning that they want to make a booking now, in which case
see '''Front desk bookings'''.
* Check they have an account. Sometimes the first contact someone has with PD will be when they turn up at the gate, and we need them to have an account before we can help them. If they don’t have an account, send them to create one on the player PCs or using their own device connected to the PD Wi-Fi. Once they’ve done that, fill out a query form, add it to the HoD Player Waiting inbox, and send them to the heads of department to sort out.
* Check when they paid, and check with the heads of department how up-to-date we are with gate bookings. If we’re sufficiently up-to-date, they can just be treated like any other player coming to pick up their pack. If not, depending on the backlog, we might be able to sort their pack straight away, or we might need to tell them to come back later.
</box>

===Front desk bookings===

'''''The Simple case'''''

This should cover the majority of cases where someone wants to buy a ticket in GOD, that is: they’re an adult who needs either a crew or gate ticket for the current event, they already have an account, they’re buying the ticket for themselves, and they’re paying the balance due immediately. For more complex cases, refer to ''The complex case.''

<box>

To create a booking, once you’re logged in to the website and you’ve clicked “Crew” from the home page:

1. Click “GOD” in the top bar, then click “Gate Booking”

2. Ask the player if they know their PID.

* If they do, put their PID in the PID box, then press Tab or Enter or click somewhere else on the page. Confirm the player’s name on your screen matches what they tell your their name is.
* If they don’t know their PID, click the “Search” button, and get some information from the player to be able to find their details; surname is normally best. Find and select the relevant player.

3. Check with the player which character they want to play, and select the character name from the “Character” drop-down menu.

4. Select the appropriate ticket type from the “Ticket” drop-down. This will normally be “Gate Booking” unless they’re crew, in which case select “Crew”.

5. If it’s a gate booking rather than a crew booking, ask the player if they’re entitled to a concession.
* If they’re not entitled to a concession, select “No” from the “Concession” drop-down.
* If they’re entitled to a concession and show you evidence of that, select “Yes” from the “Concession” drop-down.
* If they claim they’re entitled to a concession but aren’t able to show evidence, leave the Concession checkboxes blank. Tell them that you’ll need to charge full price, but that if they email in after the event, PD will refund the concession discount.

6. Check how the player wants to pay:
* For cash, take the cash off them, check it’s the right amount, hand the cash off to a head of department or whoever has the cash box at the time, and select “Cash” in the Method dropdown.
* For card payments, follow the instructions at ('''TODO'''Operating the card reader), and once the payment has been processed, select “Sumup” in the Method dropdown.
* If the player isn’t able or willing to pay for some reason, escalate to a head of department.

7. Click “Create Booking”

8. Check with the heads of department whether we’re creating packs on demand or if there’s a queue, and either have the player wait while you prepare their pack per 9.2 Making up, or come back later and collect their pack from the Matrix.

</box>

'''''The Complex case'''''

Bookings following this process should be relatively rare, but it allows us to sell any type of ticket (e.g. children’s tickets), to purchase multiple tickets at once, and to process tickets that one person is buying on someone else’s behalf (e.g. parents buying for their children, or traders paying for tickets for their crew).

<box>
To create bookings, once you’re logged in to the website and you’ve clicked “Crew” from the home page:
1. Click “Players” in the top bar.

2. Ask the player if they know their PID. If you have one person buying tickets for someone else, it’s the PID of the buyer we care about at this point, and since it’s their account we’re charging, their should either be present or the person you’re talking to should be an authorised proxy for them.
* If they do, put their PID in the PID box, then press Tab or Enter or click somewhere else on the page. Confirm the player’s name on your screen matches what they tell your their name is.
* If they don’t know their PID, click the “Search” button, and get some information from the player to be able to find their details; surname is normally best. Find and select the relevant player.
3. Click the “Bookings” tab, then click “Create Booking”

4. The “Purchase Details” section should already be filled out correctly, with the PID and name of the player buying the tickets, today’s date, and no introducer.

5. Change the Event drop-down if necessary (this should very rarely be necessary; we only take bookings for the current event at the event)

6. In the Ticket drop-down, select the appropriate ticket type. This will normally be “Gate Booking”, but may be “Crew” or one of the children’s tickets. Don’t select “Early Booking” or “Late Booking” without first checking with a head of department; don’t select “Crew” unless the person is actually crew.

7. In the Recipient box, select the person who is receiving the ticket. This will normally be the same person as is buying the ticket, but might be different if, for example, this is a ticket being bought by a parent for a child, or a ticket being bought by a trader for one of their staff.

8. Check with the player which character they want to be playing, and select it in the Character drop-down.

9. Never select the Complimentary checkbox unless either (a) you’ve been told to by a head of department, or (b) this is a booking for a child and all their responsible adults are crew.

10. If it’s a gate booking, ask the player if they’re entitled to a concession.
* If they’re not entitled to a concession, leave the Concession checkboxes blank.
* If they’re entitled to a concession and show you evidence, select both “Concession” and “Concession Seen”.
('''TODO''' Confirming concessions for more information about acceptable evidence.)
* If they claim they’re entitled to a concession but aren’t able to show evidence, leave the Concession checkboxes blank. Tell them that you’ll need to charge full price, but that if they email in after the event, PD will refund the concession discount. Examples of acceptable evidence are given in ('''TODO''' Confirming concessions.)

'''''Note:''' in GOD, you should never select one of the Concession checkboxes but not the other.''

11. Check that the amount in the “Amount” box is as expected. Don’t change this without first checking with a head of department.

12. Click “Add Ticket”.

13. If the buyer wants to buy multiple tickets at the same time, go back to step 5.

14. Click “Create Booking”.

15. You should now be returned to the player bookings page; note the balance at the top of the table, then click “Take Payment”.

16. Enter the appropriate amount in the “Amount” box.

17. Ask the player how they want to pay:
* For cash: take the cash off them, check the right amount, and select “Cash” in the Method dropdown. Hand the cash to a head of department (or whoever is in charge of the real-world cash box).
* For card payments: follow the instructions at Operating the card reader in [[Taking payments]] . Once the payment has been processed, select “Sumup” in the Method dropdown.
* If the player isn’t able or willing to pay for some reason, escalate to a head of department.

18. Don’t change any of the other values without first checking with a head of department: PID should already be correct, we never use any of the other payment methods, and the date and VAT rate will be automatically correct.

19. Click “Save”.

</box>

===Day Tickets===

Very occasionally, someone wants to attend for just one day of the event, normally turning up in the morning and leaving in the evening. They can, and they don’t have to pay full price. If someone asks for this, pass them off to one of the heads of department.

===Trader Bookings===

In principle, trader bookings are no different from player bookings: we expect traders to pay for tickets at the regular player prices. The two key differences are that '''(a)''' some of our traders also book and pay for trader pitches, and '''(b)''' some of our traders have their own crew, who also have regular player tickets, but which will typically be paid for by the trader.

If you have a trader wanting to make a pitch booking at GOD, they’re almost certainly far too late- Escalate to a head of department.

If you have a trader wanting to buy tickets for some of their crew, process that as a normal booking at the gate price per '''''The Complex case'''''. The trader may already have funds in their account to pay for the ticket, in which case there will be no need to take payment. If they don’t, they may want to leave the debt on their account rather than paying immediately; that’s probably fine, but check with a head of department (who will probably want to check with Graeme).

===Caterer Bookings===

Caterer bookings are always handled by Graeme. If you have someone from one of the caterers looking to make a booking or get a character pack or similar, escalate to a head of department or to Graeme directly

===Converting Open Tickets===

PD sell “open tickets” which aren’t tied to a particular event. Occasionally people will come to GOD saying they’re booked, but it’ll turn out they haven’t converted their open ticket to a booking for the specific event. If this happens, there’s a £10 charge for converting an open ticket to a regular booking at the event. '''Escalate this to a head of department''', as it’s reasonably likely to become a complaint.

===Price List===

In case you need them, here’s the full list of prices as of 2023. PD honours prices from when bookings were first made provided they were paid for promptly, so if a player made a booking a while ago, the correct price might not be the one below:
<box>
* Adult early booking: £75 (£55 concession)
* Adult late booking: £80 (£60 concession)
* Adult gate booking: £90 (£70 concession)
* 16/17 year olds: as adult prices, but will generally be eligible for a concession
* 11–15 year olds: £20 (£10 if a responsible adult gets a concession)
* 7–10 year olds: £10 (£5 if a responsible adult gets a concession)
* Under-7s: free
* Day tickets: ask a head of department (who will probably need to ask Graeme)
</box>

''Players may also have a £15 credits on their account if they were introduced by another player or have introduced another player. This doesn’t affect the ticket price directly.''

For day tickets, the most common prices are:
<box>
* Adult full price for all Saturday: £60
* Adult concession for all Saturday: £45
* Adult full price for Friday or Sunday: £45
* Adult concession for Friday or Sunday: £35
</box>

The rules for working out the day ticket prices (ask one of the heads of department if you’re not sure):

1. Find out how long the player is at the event: the categories we care about are broadly “a full day” (probably all Saturday),
“less than that” (e.g. Friday only, or Saturday but leaving by 6pm) or “more than that” (e.g. arriving Saturday morning
and staying the full event.

2. Find out the normal gate price for the full event, e.g. £90 for adult full price, £70 adult concession.

3. For the “a full day” category, apply a 33% discount. For the “less than that” category, apply a 50% discount. For the
“more than that” category, charge full price.

4. Round to £5.

===Thursday Nights===

There’s a £5 charge for players people staying on Thursday night. The vast majority of the time, this will be handled by the folk on the gate, but we do occasionally get people turning up at GOD to pay.

If someone wants to pay for Thursday night camping:

* If they’re paying by cash, pass the cash off to a head of department or to whoever has the cash box. Make sure it’s tallied that the money is for Thursday night camping – that cash needs to be kept (or at least counted) separately – and '''do not record it on the player account.'''
* If they’re paying by card, follow the instructions at 14.3.3 Operating the card reader. Again, '''do not record the payment on the player account'''.
[[Category:GOD manual]]

Taking payments

2023-07-06T11:14:03Z

Jmabb:

===Recording a payment===
Generally, you’ll record payments at the point you’re taking a booking. The process is outlined there, but if you need to take a payment separately for some reason:
<box>
Once you’re logged in to the website and you’ve clicked “Crew” from the home page:

1. Click “Players” in the top bar.

2. Ask the player if they know their PID.

* If they do, put their PID in the PID box, then press Tab or Enter or click somewhere else on the page. Confirm the player’s name on your screen matches what they tell your their name is.
* If they don’t know their PID, click the “Search” button, and get some information from the player to be able to find their details; surname is normally best. Find and select the relevant player.
3. Click the “Bookings” tab, then click “Take Payment”

4. Enter the appropriate amount in the “Amount” box.

5. Ask the player how they want to pay:
* For cash, take the cash off them, check it’s the right amount, hand the cash off to a head of department or whoever has the cash box at the time, and select “Cash” in the Method dropdown.
* For card payments, follow the instructions below at Operating the card reader, and once the payment has been processed, select “Sumup” in the Method dropdown.

6. Don’t change any of the other values without first checking with a head of department: PID should already be correct, we never use any of the other payment methods, and the date and VAT rate should be automatically correct.

7. Click “Save”.

</box>

===Taking Donations===

Donations are rare; if someone wants to make a donation:
* If it’s a donation of credit that’s already on their account, thank them, make a note of the PID, player name, and donation amount, and raise it with a head of department. Don’t record anything in the database.
* If it’s a donation of cash, thank them, and either hand the cash off to a head of department or whoever has the cash box at the time. In either case, make a note of the PID, player name and donation amount, and raise it with a head of department.
* If it’s a donation by some other mechanism (e.g. card payment) '''pass it straight off to a head of department'''.

===Operating the card reader===
<box>
1. Fetch the card reader from the heads of department’s desk.

2. Select “Add note” and enter the PID of the person paying.

3. Enter the amount to be paid.

4. Select VAT at 20%.

5. Wait for the card reader to contemplate life, the universe, and ''everything''. Hope that the signal on site is good enough.

6. When the screen changes to say Present Card, invite the player to tap their card or phone on the card reader, or to insert their card in the slot on top, and follow all the instructions.

7. If the payment fails, either try again, or ask the player if they can pay cash or with a different card. If you’re getting repeated failures and the player can’t pay any other way, escalate to a head of department.

8. Once you’re done with the card reader, record any payments in the database that need recording, and return the card reader to its charging cradle. Make sure it’s actually charging; you need to be fairly firm putting it in the cradle.
</box>
[[Category:GOD manual]]

Taking payments

2023-07-06T11:13:31Z

Jmabb: bookings and payment section added

Bookings

2023-07-06T11:04:14Z

Jmabb: pesky god manual code

===Bookings taken at site entrance===

The process for taking bookings at the site entrance is mostly not one GOD is involved with, but it’s outlined here for context:

1. The gate team take a payment from someone arriving on site, and note down the player’s details as best they can.

2. The gate team send a runner from the gate to the Matt Cave on a semi-regular basis to drop off cash and paperwork. (Occasionally we get asked to send a runner ourselves, depending on who can spare the crew more easily.)

3. Graeme, in the Matt Cave, processes the paperwork and books players in.

4. The GOD heads of department do intermittent print runs of new character packs, which will get made up and put in the matrix per [[Player Packs- GOD]].

If someone appears and tells you they’ve paid on the gate, this means their pack may be in the matrix ready for them to collect, but that relies on them having got through this entire process.

<box>
What you need to do with someone who turns up at GOD who has paid at the gate depends on a variety of details:
* Check they’ve actually paid. They should have a receipt they can show you. Sometimes players will say something like “I’m here for a gate booking”, meaning they’ve already paid and they want to pick up their pack, and sometimes they’ll say something more-or-less identical but meaning that they want to make a booking now, in which case
see '''Front desk bookings'''.
* Check they have an account. Sometimes the first contact someone has with PD will be when they turn up at the gate, and we need them to have an account before we can help them. If they don’t have an account, send them to create one on the player PCs or using their own device connected to the PD Wi-Fi. Once they’ve done that, fill out a query form, add it to the HoD Player Waiting inbox, and send them to the heads of department to sort out.
* Check when they paid, and check with the heads of department how up-to-date we are with gate bookings. If we’re sufficiently up-to-date, they can just be treated like any other player coming to pick up their pack. If not, depending on the backlog, we might be able to sort their pack straight away, or we might need to tell them to come back later.
</box>

===Front desk bookings===

'''''The Simple case'''''

This should cover the majority of cases where someone wants to buy a ticket in GOD, that is: they’re an adult who needs either a crew or gate ticket for the current event, they already have an account, they’re buying the ticket for themselves, and they’re paying the balance due immediately. For more complex cases, refer to ''The complex case.''

<box>

To create a booking, once you’re logged in to the website and you’ve clicked “Crew” from the home page:

1. Click “GOD” in the top bar, then click “Gate Booking”

2. Ask the player if they know their PID.

* If they do, put their PID in the PID box, then press Tab or Enter or click somewhere else on the page. Confirm the player’s name on your screen matches what they tell your their name is.
* If they don’t know their PID, click the “Search” button, and get some information from the player to be able to find their details; surname is normally best. Find and select the relevant player.

3. Check with the player which character they want to play, and select the character name from the “Character” drop-down menu.

4. Select the appropriate ticket type from the “Ticket” drop-down. This will normally be “Gate Booking” unless they’re crew, in which case select “Crew”.

5. If it’s a gate booking rather than a crew booking, ask the player if they’re entitled to a concession.
* If they’re not entitled to a concession, select “No” from the “Concession” drop-down.
* If they’re entitled to a concession and show you evidence of that, select “Yes” from the “Concession” drop-down.
* If they claim they’re entitled to a concession but aren’t able to show evidence, leave the Concession checkboxes blank. Tell them that you’ll need to charge full price, but that if they email in after the event, PD will refund the concession discount.

6. Check how the player wants to pay:
* For cash, take the cash off them, check it’s the right amount, hand the cash off to a head of department or whoever has the cash box at the time, and select “Cash” in the Method dropdown.
* For card payments, follow the instructions at ('''TODO'''Operating the card reader), and once the payment has been processed, select “Sumup” in the Method dropdown.
* If the player isn’t able or willing to pay for some reason, escalate to a head of department.

7. Click “Create Booking”

8. Check with the heads of department whether we’re creating packs on demand or if there’s a queue, and either have the player wait while you prepare their pack per 9.2 Making up, or come back later and collect their pack from the Matrix.

</box>

'''''The Complex case'''''

Bookings following this process should be relatively rare, but it allows us to sell any type of ticket (e.g. children’s tickets), to purchase multiple tickets at once, and to process tickets that one person is buying on someone else’s behalf (e.g. parents buying for their children, or traders paying for tickets for their crew).

<box>
To create bookings, once you’re logged in to the website and you’ve clicked “Crew” from the home page:
1. Click “Players” in the top bar.

2. Ask the player if they know their PID. If you have one person buying tickets for someone else, it’s the PID of the buyer we care about at this point, and since it’s their account we’re charging, their should either be present or the person you’re talking to should be an authorised proxy for them.
* If they do, put their PID in the PID box, then press Tab or Enter or click somewhere else on the page. Confirm the player’s name on your screen matches what they tell your their name is.
* If they don’t know their PID, click the “Search” button, and get some information from the player to be able to find their details; surname is normally best. Find and select the relevant player.
3. Click the “Bookings” tab, then click “Create Booking”

4. The “Purchase Details” section should already be filled out correctly, with the PID and name of the player buying the tickets, today’s date, and no introducer.

5. Change the Event drop-down if necessary (this should very rarely be necessary; we only take bookings for the current event at the event)

6. In the Ticket drop-down, select the appropriate ticket type. This will normally be “Gate Booking”, but may be “Crew” or one of the children’s tickets. Don’t select “Early Booking” or “Late Booking” without first checking with a head of department; don’t select “Crew” unless the person is actually crew.

7. In the Recipient box, select the person who is receiving the ticket. This will normally be the same person as is buying the ticket, but might be different if, for example, this is a ticket being bought by a parent for a child, or a ticket being bought by a trader for one of their staff.

8. Check with the player which character they want to be playing, and select it in the Character drop-down.

9. Never select the Complimentary checkbox unless either (a) you’ve been told to by a head of department, or (b) this is a booking for a child and all their responsible adults are crew.

10. If it’s a gate booking, ask the player if they’re entitled to a concession.
* If they’re not entitled to a concession, leave the Concession checkboxes blank.
* If they’re entitled to a concession and show you evidence, select both “Concession” and “Concession Seen”.
('''TODO''' Confirming concessions for more information about acceptable evidence.)
* If they claim they’re entitled to a concession but aren’t able to show evidence, leave the Concession checkboxes blank. Tell them that you’ll need to charge full price, but that if they email in after the event, PD will refund the concession discount. Examples of acceptable evidence are given in ('''TODO''' Confirming concessions.)

'''''Note:''' in GOD, you should never select one of the Concession checkboxes but not the other.''

11. Check that the amount in the “Amount” box is as expected. Don’t change this without first checking with a head of department.

12. Click “Add Ticket”.

13. If the buyer wants to buy multiple tickets at the same time, go back to step 5.

14. Click “Create Booking”.

15. You should now be returned to the player bookings page; note the balance at the top of the table, then click “Take Payment”.

16. Enter the appropriate amount in the “Amount” box.

17. Ask the player how they want to pay:
* For cash: take the cash off them, check the right amount, and select “Cash” in the Method dropdown. Hand the cash to a head of department (or whoever is in charge of the real-world cash box).
* For card payments: follow the instructions at ('''TODO''' Operating the card reader. Once the payment has been processed, select “Sumup” in the Method dropdown.
* If the player isn’t able or willing to pay for some reason, escalate to a head of department.

18. Don’t change any of the other values without first checking with a head of department: PID should already be correct, we never use any of the other payment methods, and the date and VAT rate will be automatically correct.

19. Click “Save”.

</box>

===Day Tickets===

Very occasionally, someone wants to attend for just one day of the event, normally turning up in the morning and leaving in the evening. They can, and they don’t have to pay full price. If someone asks for this, pass them off to one of the heads of department.

===Trader Bookings===

In principle, trader bookings are no different from player bookings: we expect traders to pay for tickets at the regular player prices. The two key differences are that '''(a)''' some of our traders also book and pay for trader pitches, and '''(b)''' some of our traders have their own crew, who also have regular player tickets, but which will typically be paid for by the trader.

If you have a trader wanting to make a pitch booking at GOD, they’re almost certainly far too late- Escalate to a head of department.

If you have a trader wanting to buy tickets for some of their crew, process that as a normal booking at the gate price per '''''The Complex case'''''. The trader may already have funds in their account to pay for the ticket, in which case there will be no need to take payment. If they don’t, they may want to leave the debt on their account rather than paying immediately; that’s probably fine, but check with a head of department (who will probably want to check with Graeme).

===Caterer Bookings===

Caterer bookings are always handled by Graeme. If you have someone from one of the caterers looking to make a booking or get a character pack or similar, escalate to a head of department or to Graeme directly

===Converting Open Tickets===

PD sell “open tickets” which aren’t tied to a particular event. Occasionally people will come to GOD saying they’re booked, but it’ll turn out they haven’t converted their open ticket to a booking for the specific event. If this happens, there’s a £10 charge for converting an open ticket to a regular booking at the event. '''Escalate this to a head of department''', as it’s reasonably likely to become a complaint.

===Price List===

In case you need them, here’s the full list of prices as of 2023. PD honours prices from when bookings were first made provided they were paid for promptly, so if a player made a booking a while ago, the correct price might not be the one below:
<box>
* Adult early booking: £75 (£55 concession)
* Adult late booking: £80 (£60 concession)
* Adult gate booking: £90 (£70 concession)
* 16/17 year olds: as adult prices, but will generally be eligible for a concession
* 11–15 year olds: £20 (£10 if a responsible adult gets a concession)
* 7–10 year olds: £10 (£5 if a responsible adult gets a concession)
* Under-7s: free
* Day tickets: ask a head of department (who will probably need to ask Graeme)
</box>

''Players may also have a £15 credits on their account if they were introduced by another player or have introduced another player. This doesn’t affect the ticket price directly.''

For day tickets, the most common prices are:
<box>
* Adult full price for all Saturday: £60
* Adult concession for all Saturday: £45
* Adult full price for Friday or Sunday: £45
* Adult concession for Friday or Sunday: £35
</box>

The rules for working out the day ticket prices (ask one of the heads of department if you’re not sure):

1. Find out how long the player is at the event: the categories we care about are broadly “a full day” (probably all Saturday),
“less than that” (e.g. Friday only, or Saturday but leaving by 6pm) or “more than that” (e.g. arriving Saturday morning
and staying the full event.

2. Find out the normal gate price for the full event, e.g. £90 for adult full price, £70 adult concession.

3. For the “a full day” category, apply a 33% discount. For the “less than that” category, apply a 50% discount. For the
“more than that” category, charge full price.

4. Round to £5.

===Thursday Nights===

There’s a £5 charge for players people staying on Thursday night. The vast majority of the time, this will be handled by the folk on the gate, but we do occasionally get people turning up at GOD to pay.

If someone wants to pay for Thursday night camping:

* If they’re paying by cash, pass the cash off to a head of department or to whoever has the cash box. Make sure it’s tallied that the money is for Thursday night camping – that cash needs to be kept (or at least counted) separately – and '''do not record it on the player account.'''
* If they’re paying by card, follow the instructions at 14.3.3 Operating the card reader. Again, '''do not record the payment on the player account'''.
[[Category:GOD manual]]

Bookings

2023-07-06T11:02:55Z

Jmabb: added the rest

===Bookings taken at site entrance===

The process for taking bookings at the site entrance is mostly not one GOD is involved with, but it’s outlined here for context:

1. The gate team take a payment from someone arriving on site, and note down the player’s details as best they can.

2. The gate team send a runner from the gate to the Matt Cave on a semi-regular basis to drop off cash and paperwork. (Occasionally we get asked to send a runner ourselves, depending on who can spare the crew more easily.)

3. Graeme, in the Matt Cave, processes the paperwork and books players in.

4. The GOD heads of department do intermittent print runs of new character packs, which will get made up and put in the matrix per [[Player Packs- GOD]].

If someone appears and tells you they’ve paid on the gate, this means their pack may be in the matrix ready for them to collect, but that relies on them having got through this entire process.

<box>
What you need to do with someone who turns up at GOD who has paid at the gate depends on a variety of details:
* Check they’ve actually paid. They should have a receipt they can show you. Sometimes players will say something like “I’m here for a gate booking”, meaning they’ve already paid and they want to pick up their pack, and sometimes they’ll say something more-or-less identical but meaning that they want to make a booking now, in which case
see '''Front desk bookings'''.
* Check they have an account. Sometimes the first contact someone has with PD will be when they turn up at the gate, and we need them to have an account before we can help them. If they don’t have an account, send them to create one on the player PCs or using their own device connected to the PD Wi-Fi. Once they’ve done that, fill out a query form, add it to the HoD Player Waiting inbox, and send them to the heads of department to sort out.
* Check when they paid, and check with the heads of department how up-to-date we are with gate bookings. If we’re sufficiently up-to-date, they can just be treated like any other player coming to pick up their pack. If not, depending on the backlog, we might be able to sort their pack straight away, or we might need to tell them to come back later.
</box>

===Front desk bookings===

'''''The Simple case'''''

This should cover the majority of cases where someone wants to buy a ticket in GOD, that is: they’re an adult who needs either a crew or gate ticket for the current event, they already have an account, they’re buying the ticket for themselves, and they’re paying the balance due immediately. For more complex cases, refer to ''The complex case.''

<box>

To create a booking, once you’re logged in to the website and you’ve clicked “Crew” from the home page:

1. Click “GOD” in the top bar, then click “Gate Booking”

2. Ask the player if they know their PID.

* If they do, put their PID in the PID box, then press Tab or Enter or click somewhere else on the page. Confirm the player’s name on your screen matches what they tell your their name is.
* If they don’t know their PID, click the “Search” button, and get some information from the player to be able to find their details; surname is normally best. Find and select the relevant player.

3. Check with the player which character they want to play, and select the character name from the “Character” drop-down menu.

4. Select the appropriate ticket type from the “Ticket” drop-down. This will normally be “Gate Booking” unless they’re crew, in which case select “Crew”.

5. If it’s a gate booking rather than a crew booking, ask the player if they’re entitled to a concession.
* If they’re not entitled to a concession, select “No” from the “Concession” drop-down.
* If they’re entitled to a concession and show you evidence of that, select “Yes” from the “Concession” drop-down.
* If they claim they’re entitled to a concession but aren’t able to show evidence, leave the Concession checkboxes blank. Tell them that you’ll need to charge full price, but that if they email in after the event, PD will refund the concession discount.

6. Check how the player wants to pay:
* For cash, take the cash off them, check it’s the right amount, hand the cash off to a head of department or whoever has the cash box at the time, and select “Cash” in the Method dropdown.
* For card payments, follow the instructions at ('''TODO'''Operating the card reader), and once the payment has been processed, select “Sumup” in the Method dropdown.
* If the player isn’t able or willing to pay for some reason, escalate to a head of department.

7. Click “Create Booking”

8. Check with the heads of department whether we’re creating packs on demand or if there’s a queue, and either have the player wait while you prepare their pack per 9.2 Making up, or come back later and collect their pack from the Matrix.

</box>

'''''The Complex case'''''

Bookings following this process should be relatively rare, but it allows us to sell any type of ticket (e.g. children’s tickets), to purchase multiple tickets at once, and to process tickets that one person is buying on someone else’s behalf (e.g. parents buying for their children, or traders paying for tickets for their crew).

<box>
To create bookings, once you’re logged in to the website and you’ve clicked “Crew” from the home page:
1. Click “Players” in the top bar.

2. Ask the player if they know their PID. If you have one person buying tickets for someone else, it’s the PID of the buyer we care about at this point, and since it’s their account we’re charging, their should either be present or the person you’re talking to should be an authorised proxy for them.
* If they do, put their PID in the PID box, then press Tab or Enter or click somewhere else on the page. Confirm the player’s name on your screen matches what they tell your their name is.
* If they don’t know their PID, click the “Search” button, and get some information from the player to be able to find their details; surname is normally best. Find and select the relevant player.
3. Click the “Bookings” tab, then click “Create Booking”

4. The “Purchase Details” section should already be filled out correctly, with the PID and name of the player buying the tickets, today’s date, and no introducer.

5. Change the Event drop-down if necessary (this should very rarely be necessary; we only take bookings for the current event at the event)

6. In the Ticket drop-down, select the appropriate ticket type. This will normally be “Gate Booking”, but may be “Crew” or one of the children’s tickets. Don’t select “Early Booking” or “Late Booking” without first checking with a head of department; don’t select “Crew” unless the person is actually crew.

7. In the Recipient box, select the person who is receiving the ticket. This will normally be the same person as is buying the ticket, but might be different if, for example, this is a ticket being bought by a parent for a child, or a ticket being bought by a trader for one of their staff.

8. Check with the player which character they want to be playing, and select it in the Character drop-down.

9. Never select the Complimentary checkbox unless either (a) you’ve been told to by a head of department, or (b) this is a booking for a child and all their responsible adults are crew.

10. If it’s a gate booking, ask the player if they’re entitled to a concession.
* If they’re not entitled to a concession, leave the Concession checkboxes blank.
* If they’re entitled to a concession and show you evidence, select both “Concession” and “Concession Seen”.
('''TODO''' Confirming concessions for more information about acceptable evidence.)
* If they claim they’re entitled to a concession but aren’t able to show evidence, leave the Concession checkboxes blank. Tell them that you’ll need to charge full price, but that if they email in after the event, PD will refund the concession discount. Examples of acceptable evidence are given in ('''TODO''' Confirming concessions.)

'''''Note:''' in GOD, you should never select one of the Concession checkboxes but not the other.''

11. Check that the amount in the “Amount” box is as expected. Don’t change this without first checking with a head of department.

12. Click “Add Ticket”.

13. If the buyer wants to buy multiple tickets at the same time, go back to step 5.

14. Click “Create Booking”.

15. You should now be returned to the player bookings page; note the balance at the top of the table, then click “Take Payment”.

16. Enter the appropriate amount in the “Amount” box.

17. Ask the player how they want to pay:
* For cash: take the cash off them, check the right amount, and select “Cash” in the Method dropdown. Hand the cash to a head of department (or whoever is in charge of the real-world cash box).
* For card payments: follow the instructions at ('''TODO''' Operating the card reader. Once the payment has been processed, select “Sumup” in the Method dropdown.
* If the player isn’t able or willing to pay for some reason, escalate to a head of department.

18. Don’t change any of the other values without first checking with a head of department: PID should already be correct, we never use any of the other payment methods, and the date and VAT rate will be automatically correct.

19. Click “Save”.

</box>

===Day Tickets===

Very occasionally, someone wants to attend for just one day of the event, normally turning up in the morning and leaving in the evening. They can, and they don’t have to pay full price. If someone asks for this, pass them off to one of the heads of department.

===Trader Bookings===

In principle, trader bookings are no different from player bookings: we expect traders to pay for tickets at the regular player prices. The two key differences are that '''(a)''' some of our traders also book and pay for trader pitches, and '''(b)''' some of our traders have their own crew, who also have regular player tickets, but which will typically be paid for by the trader.

If you have a trader wanting to make a pitch booking at GOD, they’re almost certainly far too late- Escalate to a head of department.

If you have a trader wanting to buy tickets for some of their crew, process that as a normal booking at the gate price per '''''The Complex case'''''. The trader may already have funds in their account to pay for the ticket, in which case there will be no need to take payment. If they don’t, they may want to leave the debt on their account rather than paying immediately; that’s probably fine, but check with a head of department (who will probably want to check with Graeme).

===Caterer Bookings===

Caterer bookings are always handled by Graeme. If you have someone from one of the caterers looking to make a booking or get a character pack or similar, escalate to a head of department or to Graeme directly

===Converting Open Tickets===

PD sell “open tickets” which aren’t tied to a particular event. Occasionally people will come to GOD saying they’re booked, but it’ll turn out they haven’t converted their open ticket to a booking for the specific event. If this happens, there’s a £10 charge for converting an open ticket to a regular booking at the event. '''Escalate this to a head of department''', as it’s reasonably likely to become a complaint.

===Price List===

In case you need them, here’s the full list of prices as of 2023. PD honours prices from when bookings were first made provided they were paid for promptly, so if a player made a booking a while ago, the correct price might not be the one below:
<box>
* Adult early booking: £75 (£55 concession)
* Adult late booking: £80 (£60 concession)
* Adult gate booking: £90 (£70 concession)
* 16/17 year olds: as adult prices, but will generally be eligible for a concession
* 11–15 year olds: £20 (£10 if a responsible adult gets a concession)
* 7–10 year olds: £10 (£5 if a responsible adult gets a concession)
* Under-7s: free
* Day tickets: ask a head of department (who will probably need to ask Graeme)
</box>

''Players may also have a £15 credits on their account if they were introduced by another player or have introduced another player. This doesn’t affect the ticket price directly.''

For day tickets, the most common prices are:
<box>
* Adult full price for all Saturday: £60
* Adult concession for all Saturday: £45
* Adult full price for Friday or Sunday: £45
* Adult concession for Friday or Sunday: £35
</box>

The rules for working out the day ticket prices (ask one of the heads of department if you’re not sure):

1. Find out how long the player is at the event: the categories we care about are broadly “a full day” (probably all Saturday),
“less than that” (e.g. Friday only, or Saturday but leaving by 6pm) or “more than that” (e.g. arriving Saturday morning
and staying the full event.

2. Find out the normal gate price for the full event, e.g. £90 for adult full price, £70 adult concession.

3. For the “a full day” category, apply a 33% discount. For the “less than that” category, apply a 50% discount. For the
“more than that” category, charge full price.

4. Round to £5.

===Thursday Nights===

There’s a £5 charge for players people staying on Thursday night. The vast majority of the time, this will be handled by the folk on the gate, but we do occasionally get people turning up at GOD to pay.

If someone wants to pay for Thursday night camping:

* If they’re paying by cash, pass the cash off to a head of department or to whoever has the cash box. Make sure it’s tallied that the money is for Thursday night camping – that cash needs to be kept (or at least counted) separately – and '''do not record it on the player account.'''
* If they’re paying by card, follow the instructions at 14.3.3 Operating the card reader. Again, '''do not record the payment on the player account'''.

Bookings

2023-07-06T10:50:27Z

Jmabb: bookings page- saving partway through as server keeps logging me out and deleting unsaved additions

Visions

2023-07-06T10:25:30Z

Jmabb: adding god manual link

Sometimes players will get visions. Telling players they should get visions isn’t something GOD ''typically'' needs to do proactively – you’ll be told if you need to tell a player they’re getting a vision – but players do frequently come to GOD to pick up visions they’ve been told they should receive, e.g. because they cast The Somnolent Wanderer the day before.

Typically Plot will put visions up on the [https://www.profounddecisions.co.uk/empireplotwiki Plot Wiki] which you may or may not have access to. Erin and Adam both have access; ask them if they’re available. The Plot team don’t have a clear naming scheme for these pages, but they’ll typically be called something like “Visions E2-2023” and will link to the specific documents to print. If the documents aren’t on the wiki yet, or you’re not able to get access or find someone who has access, either ask the Plot team on the radio or just go down to the Matt Cave to ask if the specific vision is available.

You also may be asked for [https://www.profounddecisions.co.uk/empire-wiki/Infusions_of_Feathers#Goosewhisper_Infusion Goosewhisper visions] which are usually stored on the ref desk in a plastic bag. Ideally ask the player for proof that they've taken the infusion (they will often have the ripped up lammy) and then let them pick out a piece of paper from the bag. The player gets to look at it for as long as they want but must not speak, show the paper to anyone or write anything down until they've given the vision back. The lovely refs on the ref desk will be able to explain this process/show you/ do it themselves if you'd rather.

'''TODO- check its okay for GOD crew to hand out goosewhisper visions, the last paragraph was added at my own discretion''' ''-Jess :)''
[[Category:GOD manual]]

Visions

2023-07-06T10:24:38Z

Jmabb: visions page added!

Printing

2023-07-06T10:02:30Z

Jmabb: printing guide transfer done

===Printing things===

Actually making the printers print is an arcane art, and is the only part of our job that still uses a creaking, old Microsoft Access interface. It’s also not something we’ve fully documented yet.
In the meantime, here are a few pointers:

* Don’t close the Access window with the document(s) you’re printing until you’ve actually printed them.
* Do close the Access window with the document(s) you’ve printed as soon as you have printed them, and '''remember to confirm that they have printed'''.
* For printing night pouches, use the specific night pouch report, page through it until you find the CID of the person who has the night pouch, then select that page for printing by page number.
* If the ribbon printer goes awry, '''stop it printing as quickly as possible''': either just turn it off (switch on the right hand side) or eject the ink foil (lift the lid, then pull the two white toggles on either side of the foil feeder).
* You can check if a character pack or passport has printed by looking at the player page on the web interface, on the “Documents” tab. If you click the “Details” button, you can tick or untick the “Document Printed” box: ticking it when it isn’t ticked will remove it from the print queue without actually printing anything, while unticking it will add the document back to the print queue based on what would currently be printed for that character.

<box>

'''To print player packs and ribbons:'''

1. Add the document to the print queue, from any computer where you are logged in to the PD crew interface.

* '''''For newly-created characters:'''''
(a) Navigate to the character page.

(b) Click “Play Character” from the buttons on the right hand side of the page.

(c) Click “Confirm” in the dialogue box.

(d) Click “Event Pack” from the buttons on the right hand side of the page.

(e) Click “Confirm”.

'''''Note''': at this point, either ask the player to wait while you proceed to the next steps and make up their pack immediately (see [[Player Packs- GOD]]) while they wait, or fill out a query slip (including CID to make sure the pack for the right character gets printed!).''

* '''''For missing packs:'''''
(a) Confirm that you really can’t find the pack anywhere.

(b) Look up the player.

(c) Confirm that they are booked for the event by checking the “Events” and “Bookings” tabs. If they aren’t, a booking will need to be processed – escalate if you’re not sure how to do this.

(d) Confirm that they have an active character, i.e. that under the “Characters” tab they have a character set to “Played”. If they’re not, see For newly-created characters.

* '''''For ribbons:'''''

(a) Navigate to the ribbon page.

(b) Click “Print ribbon” from the buttons on the right hand side of the page.

2. Print the documents, from a computer connected to the printers.

(a) If it’s not already open, launch the Access database frontend.

(b) From the row of buttons and the like across the top of the screen, click “Print Queue”. If the “Print Queue” window is already open, refresh it by closing it and then reopening it using this button.

(c) In the “Print Queue” window, click the line corresponding to the document you want to print.

(d) In the “Print Queue” window, click “Print” from the buttons on the right-hand side. A new window will open up, showing a preview of documents of the selected type that are in the queue to print.

(e) Press Ctrl + P on the keyboard, or right-click on the print preview and then click Print.

(f ) Make any necessary adjustments to the printer settings (e.g. which printer and tray to use – exactly what these are varies between events but is usually written down and next to the printing PC).

(g) Click “OK”.

(h) For the ribbon printer, press the “Feed” button a couple of times to get you the extra length you need to cut the ribbon.

(i) Check the documents produced by the printers. Once you’re satisfied they’ve come out correctly, close the print preview window and confirm that all documents have printed.

</box>

[[Category:GOD manual]]

GOD checklists

2023-07-06T09:51:36Z

Jmabb: putting into god manaul

===At a loose end?===

* have a drink or a snack or a stretch or a break!
* offer to get other people a drink or a snack :)
* make up waiting packs (see [[Player Packs- GOD]])
* condense packs down to fewer crates
* tidy up paper and plastic scraps around the lamination station
* move abandoned stationery back to the drawers
* make up herb and mana gardens (see [[Cards & Lammies]])
* laminate potions (see [[Potions desk]])
* sort incoming resources
* check whether the bins need emptying (& then do it!)
* arrange the ribbons in numerical order
* rotate the radio batteries (green light into the charged box, empties onto the chargers)
* sort card resources and potions into labelled batches of 50 or 100 for end-of-event stocktake

===Overnight===

In the Before Times, the GOD tent had walls and all the in-game resources got left out overnight. In the Plague Times ''(and post plague times)'', the GOD tent does not have walls, so valuable in-game resources need to be transferred to the GOD Crate at night, and brought back out in the morning.

Items that need to be locked away and then set back up are:
* materials ([[Materials]])
* card resources (potions, vis, herbs, mana, liao), including spares (under the tables)
* Bourse resources
* potions and potions manuals
* any coin boxes that doesn’t lock
* player packs (stacked neatly, and at least approximately in numerical order!)
* lost property, especially valuable lost property
* real-world cash
Everything else – including electronics, locking coin boxes, blank potions sheets, and virtue/anointing cards – can stay out.

===Before opening===

Only worry about this if you’re on shift first thing!
One of the heads of department should be up early to unlock the GOD Crate and turn on the power. Once that’s happened…

* get everything back out of the Crate and into place (see [[GOD physical organisation]])
– it’s often helpful to chain this, with one person inside the Crate getting boxes to the entrance, and several people ferrying boxes from the entrance to the tent
– materials go in alphabetical order, with one crate each of 1s, 3s and 5s
– herbs go together and in alphabetical order; same for potions and vis
* get the IC cash boxes out of the big coin boxes
* boot up the PCs, log into them, and get the PD website up
* make sure each PC has a notepad, a writing implement, and some hand sanitiser
* check the stock of Freddos (and other snacks!)
* consolidate the bins, get rid of any full bin bags, and replace with new bin bags as necessary
* catch up on any packs that needed making and get them into the matrix

===Before going to bed===

Only worry about these if you’re on shift last thing!

* get everything that needs to go away into the Crate ('''Overnight''')
– it’s often helpful to chain this, with some people ferrying boxes to the Crate and one person inside the Crate getting things onto shelves
* tidy any stray stationery away into its drawers
* turn off the laminators
* throw away any rubbish that’s accumulated on the tables
* consolidate the bins, get rid of any full bin bags, and replace with new bin bags as necessary
* shut down all of the PCs and turn off the monitors
Heads of department are then responsible for turning off the lights and power, and making sure the coin boxes and the Crate are locked.

===Stocktaking and Packing weekend prep===

It’s always useful to know how much we have of everything we need, both in terms of in-game resources (running out of 1 ring pieces is a pain!) and in terms of all the tools and stationery that GOD needs to run. In general we don’t care about exact numbers – knowing we have exactly 241 five-Weltsilver ingots is definitely not worth the time versus “a couple of hundred-ish” – but having enough lead-time to order replacements means we don’t need to come up with last-minute excuses for why we’ve had to substitute things we’re lacking stock of.

Making resources up into bundles of well-known size is partly useful for the stock count, and is also useful for the packing weekend. There are a lot of players with basic congregations, basic mana sites or basic herb gardens, in particular, which means a lot of players whose packs will contain a standard set of resources. If those players can just get a single bundle of pre-counted
cards, it makes running the packing weekend much easier.

If you have some spare time, bundling things up is useful:

* Make up herb gardens (6 True Vervain, 2 Bladeroot, 2 Cerulean Mazzarine, 2 Imperial Roseweald, 2 Marrowort), in labelled stacks of 25 or 50
* Make up mana sites (7 Mana), in labelled stacks of 25 or 50
* Bundle up herbs, mana, liao, philtres, &c. into (labelled!) sets of 50 and 100 If you’re doing stock-take, make sure you’re checking with someone who’s coordinating – we don’t want to accidentally get two people counting the same things – and get estimates of how many of each of the below we have:
* In-game resources
– Each of the herb cards that make up the herb gardens

– Mana cards

– Liao cards

– Each of the six types of Vis card

– Each of the seven types of anointing card

– Artisan’s Oil cards

– Each of the philtres (the potions that are printed on cards)

– Each of the non-philtre potions (these will be in lammy pouches; it’s normal to have few-to-none of a lot of these)

– Each of the eight coin denominations

– Each of the three sizes of the eight materials

– The three sizes of ilium

– The little fish effigies used for Swim Leviathan’s Depth

– The three types of Bourse certificate

• GOD miscellany.
– Laminator pouches, in A4, A3 and credit-card/potion sizes

– Paper
* White
*Vellum
*Pre-printed potion slips
– C5 envelopes

– Anything else you notice is in short supply

===Tear Down===

* get packs booked in and broken down
* sort resources into their boxes
* finish packing weekend prep
* return all stationery to its drawers and boxes
* fold all the tables
* empty all the bins, and then collapse and secure the semi-rigid outers
* hand to Graeme:
– The card payment machine
* into the GOD crate (things that stay on site and won’t be seen again until next event):
– any non-valuable and non-identifiable lost property

– computers, tech, &c. that isn’t going to Enfield

– tables and chairs

– non-paper stationery that isn’t going to Enfield or Preston

– '''⁇? TODO Check with Erin'''
* for the Preston pile (things that will be wanted by MattP between events or for packing weekend):
– resource boxes (including cards, potions, &c.)
– hand-in slips

– any unused paper

– '''⁇? TODO Check with Erin'''
* for the Enfield pile (things that will be wanted by Adam between events):
– stationary and printing stuff (Adam should have an up-to-date list of what he wants)

– any valuable or identifiable lost property

– any of Adam’s stuff that he’s going to pick up with the Enfield pile
[[Category:GOD manual]]

GOD checklists

2023-07-06T09:46:22Z

Jmabb: bad god link fixed

GOD checklists

2023-07-06T09:44:44Z

Jmabb: checklists page added

===At a loose end?===

* have a drink or a snack or a stretch or a break!
* offer to get other people a drink or a snack :)
* make up waiting packs (see [[Player Packs- GOD]])
* condense packs down to fewer crates
* tidy up paper and plastic scraps around the lamination station
* move abandoned stationery back to the drawers
* make up herb and mana gardens (see [[Cards & Lammies]])
* laminate potions (see [[Potions desk]])
* sort incoming resources
* check whether the bins need emptying (& then do it!)
* arrange the ribbons in numerical order
* rotate the radio batteries (green light into the charged box, empties onto the chargers)
* sort card resources and potions into labelled batches of 50 or 100 for end-of-event stocktake

===Overnight===

In the Before Times, the GOD tent had walls and all the in-game resources got left out overnight. In the Plague Times ''(and post plague times)'', the GOD tent does not have walls, so valuable in-game resources need to be transferred to the GOD Crate at night, and brought back out in the morning.

Items that need to be locked away and then set back up are:
* materials ([[Materials]])
* card resources (potions, vis, herbs, mana, liao), including spares (under the tables)
* Bourse resources
* potions and potions manuals
* any coin boxes that doesn’t lock
* player packs (stacked neatly, and at least approximately in numerical order!)
* lost property, especially valuable lost property
* real-world cash
Everything else – including electronics, locking coin boxes, blank potions sheets, and virtue/anointing cards – can stay out.

===Before opening===

Only worry about this if you’re on shift first thing!
One of the heads of department should be up early to unlock the GOD Crate and turn on the power. Once that’s happened…

* get everything back out of the Crate and into place (see [[GOD- physical organisation]])
– it’s often helpful to chain this, with one person inside the Crate getting boxes to the entrance, and several people ferrying boxes from the entrance to the tent
– materials go in alphabetical order, with one crate each of 1s, 3s and 5s
– herbs go together and in alphabetical order; same for potions and vis
* get the IC cash boxes out of the big coin boxes
* boot up the PCs, log into them, and get the PD website up
* make sure each PC has a notepad, a writing implement, and some hand sanitiser
* check the stock of Freddos (and other snacks!)
* consolidate the bins, get rid of any full bin bags, and replace with new bin bags as necessary
* catch up on any packs that needed making and get them into the matrix

===Before going to bed===

Only worry about these if you’re on shift last thing!

* get everything that needs to go away into the Crate ('''Overnight''')
– it’s often helpful to chain this, with some people ferrying boxes to the Crate and one person inside the Crate getting things onto shelves
* tidy any stray stationery away into its drawers
* turn off the laminators
* throw away any rubbish that’s accumulated on the tables
* consolidate the bins, get rid of any full bin bags, and replace with new bin bags as necessary
* shut down all of the PCs and turn off the monitors
Heads of department are then responsible for turning off the lights and power, and making sure the coin boxes and the Crate are locked.

===Stocktaking and Packing weekend prep===

It’s always useful to know how much we have of everything we need, both in terms of in-game resources (running out of 1 ring pieces is a pain!) and in terms of all the tools and stationery that GOD needs to run. In general we don’t care about exact numbers – knowing we have exactly 241 five-Weltsilver ingots is definitely not worth the time versus “a couple of hundred-ish” – but having enough lead-time to order replacements means we don’t need to come up with last-minute excuses for why we’ve had to substitute things we’re lacking stock of.

Making resources up into bundles of well-known size is partly useful for the stock count, and is also useful for the packing weekend. There are a lot of players with basic congregations, basic mana sites or basic herb gardens, in particular, which means a lot of players whose packs will contain a standard set of resources. If those players can just get a single bundle of pre-counted
cards, it makes running the packing weekend much easier.

If you have some spare time, bundling things up is useful:

* Make up herb gardens (6 True Vervain, 2 Bladeroot, 2 Cerulean Mazzarine, 2 Imperial Roseweald, 2 Marrowort), in labelled stacks of 25 or 50
* Make up mana sites (7 Mana), in labelled stacks of 25 or 50
* Bundle up herbs, mana, liao, philtres, &c. into (labelled!) sets of 50 and 100 If you’re doing stock-take, make sure you’re checking with someone who’s coordinating – we don’t want to accidentally get two people counting the same things – and get estimates of how many of each of the below we have:
* In-game resources
– Each of the herb cards that make up the herb gardens

– Mana cards

– Liao cards

– Each of the six types of Vis card

– Each of the seven types of anointing card

– Artisan’s Oil cards

– Each of the philtres (the potions that are printed on cards)

– Each of the non-philtre potions (these will be in lammy pouches; it’s normal to have few-to-none of a lot of these)

– Each of the eight coin denominations

– Each of the three sizes of the eight materials

– The three sizes of ilium

– The little fish effigies used for Swim Leviathan’s Depth

– The three types of Bourse certificate

• GOD miscellany.
– Laminator pouches, in A4, A3 and credit-card/potion sizes

– Paper
* White
*Vellum
*Pre-printed potion slips
– C5 envelopes

– Anything else you notice is in short supply

===Tear Down===

* get packs booked in and broken down
* sort resources into their boxes
* finish packing weekend prep
* return all stationery to its drawers and boxes
* fold all the tables
* empty all the bins, and then collapse and secure the semi-rigid outers
* hand to Graeme:
– The card payment machine
* into the GOD crate (things that stay on site and won’t be seen again until next event):
– any non-valuable and non-identifiable lost property

– computers, tech, &c. that isn’t going to Enfield

– tables and chairs

– non-paper stationery that isn’t going to Enfield or Preston

– '''⁇? TODO Check with Erin'''
* for the Preston pile (things that will be wanted by MattP between events or for packing weekend):
– resource boxes (including cards, potions, &c.)
– hand-in slips

– any unused paper

– '''⁇? TODO Check with Erin'''
* for the Enfield pile (things that will be wanted by Adam between events):
– stationary and printing stuff (Adam should have an up-to-date list of what he wants)

– any valuable or identifiable lost property

– any of Adam’s stuff that he’s going to pick up with the Enfield pile

GOD checklists

2023-07-06T09:12:09Z

Jmabb: GOD checklist page- saved partway through completing as I got booted halfway through doing it last time and lost it :(

Player Packs- GOD

2023-07-06T08:44:11Z

Jmabb:

===Set up===

<box>
Packing weekend has hopefully happened, at which the majority of packs – for bookings made in advance – will have been prepared. These packs will have been arranged, in order of PID, in folding crates, to form the Matrix.
* A list of pack corrections will have been provided via a webform and printed out and ''hopefully'' attached to a clipboard. '''Cross them out as you do them''' so we don’t duplicate effort.
* Some players will have provided proof that they’re entitled to a concession between packing weekend and arrival in the field. Graeme or Matt P will likely have provided the list of relevant PIDs, hopefully via the webform. Go through the Matrix, identify the relevant envelopes, scribble out “Confirm Concession” on the front of them, and replace them in the Matrix. Also cross the PIDs off the list of packs to pull to put in the Concessions crate.
* Concessions that still need to be confirmed need separating out from the Matrix into their own crate(s). '''Keep them in numerical order by PID!''' These want to end up living to the left end of the front desk. There should be a printed out list of PIDs to separate.
* Crew packs need separating out from the main Matrix into their own crate(s), kept in numerical order by PID, and moved to the right end of the front desk.
– Some crew packs will need to go into individual departmental boxes – see the departmental lists (which should
be printed out).

– The rest will want separating into crates to get handed out from GOD, and there’s a list for those, too.
* Plot will need to go into envelopes as it arrives. We’ll get printouts and lists of packs, and will need to go through the Matrix stuffing things into envelopes.

</box>

===Making packs up===

Over the course of the event, we’ll need to make up new packs for players, whether they booked after packing weekend or after characters die in the big battles on Saturday and Sunday mornings. A player pack consists of an envelope, a passport, and some number of resources. The front of the envelope is printed with a list of items the envelope should contain.
<box>

1. The passport and the envelope should come off the printer fairly close together. Fold up the passport (''if A4'') and place it in the envelope.

2. Add coins to the pack to the given value, according to the listed denominations (see [[Currency]] for help).

3. Add materials, card resources, and Bourse resources in the stated quantities.

4. Some packs will contain items that are listed as a five-digit number followed by a brief description. These are unique ID numbers for Ribbons. Check whether the ribbon in question has already been printed out, by looking through the great big board of ribbons. If not, print it, and add it to the pack.

5. Put the pack wherever the pack needs to go, probably either directly into the player’s hands, or into the box for players who are going to come back to pick items up later.

</box>

===Hand out===

<box>

1. A player will get to the front of the queue. Ask them their PID.

2. If they don’t know their PID, ask them if they have their ticket; everyone should have a ticket, either printed or on their phone, which has their PID on it.

3. If they still don’t have their PID, to speak to somebody at a computer, or someone with a clipboard of names and PIDs if one exists, and then come back to the pack handout queue.

4. Find their pack.

5. Ask them to confirm their name – either of their player/wallet name or character name is fine!

6. Hand over their pack.

7. Circle back to the head of the queue and repeat.

Some players will have '''proxies''' registered in the system. If this is the case, their pack will have the PIDs of their proxies printed on the envelope. If someone comes to pick up a pack for another player, first ask if they are registered as a proxy.

*If they say yes:
1. If they say yes, ask for the PID of the player whose pack they are collecting.

2. Find the pack, as above.

3. Ask for the PID of the player who is collecting the pack. Check that it is printed on the envelope as a registered
proxy.

4. Confirm the name of the player whose pack is being collected.

5. Hand over the pack, and ask if the player needs to collect any other packs. :)

* If they say no, they are not registered as a proxy:
1. Explain about the proxy system: between events, the player who wants to nominate a proxy should e-mail admin@profounddecisions.co.uk with their PID and the PIDs of any proxies they want to set up.

2. Ask what their relationship to the player whose pack they wish to collect is.

* If they have the other person’s ticket – either on a print-out or on a phone or similar – we can take that as proof that they’re allowed the pack, so hand it out.
* If they are a parent, this should be recorded in the computer system. Double-check, or get someone else to, and then hand over the pack.
* Otherwise, explain that you will need to see proof that they have the other player’s permission to collect their pack on their behalf, e.g. photo ID of or a note from the other player. (This is to avoid theft of in-game resources, which would otherwise be very easy!)
* If you’re at all unsure, escalate to a head of department.
</box>

===Missing Packs===

Despite everyone’s best efforts, packs sometimes wind up in the wrong place. It is actually pretty rare for them to just not get printed at all, though, so there’s several things to check first. This process can also be found on the back of the query slips:
[[File:Query form back.png|thumb|right|Query slip (back)]]

<box>

1. Ask whether the player is '''crew or a concession'''. If yes, check those matrices.
*Depending on which crew team they are, their pack might have gone to their team leader/Head of Department already, so they’ll need to go check there. There will normally be someone specifically handling the crew desk, who should have a list.

2. Ask whether the player was asked to come back later. If yes, '''check the query slips boxes''' to see if there’s a query slip tracking this already.

3. Numbers are tricksy and packs hide. Get someone else to double-check the PID with the player, confirm it’s the number you looked for, and look for that number.

4. Even if the player isn’t crew or a concession, check those matrices.

5. Check whether the player has got their PID correct by looking them up on the computer system ''(If they haven't, repeat from step 1!)''

6. If the player’s PID was correct and you still can’t find their pack, it’s time to start checking whether they were ''actually'' booked

7. If they seem to be booked and there’s no pack, write their details down on a query slip and – depending on the queues – either ask them to come back later or get them to wait while a head of department investigates further.

</box>

===Break Down===

At some point, we start assuming that any packs that haven’t been collected yet aren’t going to be, and begin breaking them back down. This is a task that involves working with computers, so ''technically'' belongs in Online Processes but involves packs and makes more sense here.

Typically this happens once we get to a lull on Saturday morning; we don’t want to do it earlier, as we’d rather have players take their packs away than have to break them down, but we also want to get the job done when we have a suitable quiet period, and ideally in time to let Plot know about things they need to re-plan because plot hooks haven’t been delivered. As part of this, if any character packs have been delivered to other crew departments, someone with a radio should get in touch with the heads of those departments to get any uncollected packs back from them.

<box>
Once you’re logged in to the website and you’ve clicked “Crew” from the home page:

1. Click “Character” in the tabs across the top of the screen.

2. In the CID search box, enter the PID from the top right of the player pack you are working on, and press Tab or Enter. (You don’t need to enter the full CID!)

3. Click “Inventory” from the tabs underneath the character name.

4. Click “Not Collected” from the buttons down the right-hand side of the screen.

5. Click “Confirm” on the pop-up that appears.

6. Dump the resources into your big crate of for someone else (possibly your future self!) to sort.

7. If there are any plot documents or arcane projections in the envelope, note the PID (if it isn’t printed on the documents already), and pass to a head of department.
*Arcane Projections will get filed to deliver at a future event.
*Plot documents get handed to someone in the Plot department; they can then decide if they need to re-write some of their plots on the fly to account for some of the documents not having been delivered.

8. Click “Save”.

9. Repeat from Step 2 with the next pack.

</box>

===Resource Hand-in===

'''GOD is not a bank.'''

In general, players are encouraged to keep hold of their resources, for two reasons. The first is that this makes more opportunity for game play: it increases the chances for in-game loss or theft, and the consequences of same. The second is it means we don’t have to count everything in, find the space to store stuff, then count everything out again. This also means that in general players are discouraged from handing resources in at GOD, with two main exceptions:

'''1.''' They want to use the resource immediately: for example, they want to deposit three Iridescent Gloaming so that they
can perform a specific ritual ''or''

'''2.''' They want to use the resources during downtime, to create items or perform actions.

In the first case, the player should be directed to the queue for computer-based queries. In the second case, hand-in of resources for use over downtime isn’t accepted before Sunday, unless the player is leaving site before Sunday. Players should be given a hand-in slip and a plastic bag, told to deposit only the resources they actually want to use, and asked to fill out the form, then return to deposit their bag and completed hand-in slip.

===Processing Hand-in bags===

Properly, this section belongs in [[GOD manual| Online Processes]], but alas it makes more sense to put it here, so here it is.

<box>
Once you’re logged in to the website and you’ve clicked “Crew” from the home page:

1. Click “GOD”. You will land on the “Book-in Baggy” page.

2. Enter the PID in the CID box, and press Tab or Enter. (You don’t have to actually bother with the full CID!) The correct event should automatically be selected in the dropdown box.
* If the PID doesn’t match the name, you’ll have to look it up.

3. Check that the quantity of each resource in the baggy matches the quantity written on the slip, and enter the quantity into the relevant field on the computer.
* If there is a discrepancy between the hand-in slip and the contents of the baggy, call someone else over to double-count. Amend the slip as necessary, and initial the amendments to make it clear that you’re the one who made them.

4. If there is anything else odd (e.g. ribbons, herbs) in the bag, keep it separate and flag with a head of department.

5. Dump the resources into your in-crate for someone else to take away and sort as you go.

6. Save the Book-in Baggy form.

7. '''DO NOT''' click “Confirm” until you have copied the '''reference number''' into the field on the hand-in slip.

8. Ideally, keep the slips in order by PID.

9. Repeat from step 2 with the next baggy.

When you finish processing hand-in baggies, hand over the pile of slips to one of the heads of department. Let them
know if the slips aren’t in order by PID.

</box>
[[Category:GOD manual]]

File:Query form back.png

2023-07-06T08:42:13Z

Jmabb:

query slip on missing pack checklist side

Task Tracking

2023-07-06T08:40:07Z

Jmabb: added query slip

If you’re dealing with a query of any sort, and either sending the player away or sending them to talk to one of the heads of department, you need to write this down on one of the pre printed forms, and put that form in the relevant inbox. This reduces the risk of players waiting around forgotten, or of them needing to come back multiple times for the same issue.

[[File:Query form (front).png|thumb|Query slip (front)]]

===Before sending a player away===
<box>

Before sending a player away, or sending them to wait for a head of department:

1. On one of the A5 query sheets, record:
* Your name
* The PID and name of the player
* The current time and date
* Any other involved PIDs or ribbon IDs
* A description of what needs doing to resolve the query

2. Is someone currently triaging query sheets?
* If there is:
(a) Pass the sheet to them and give them a chance to review it.

(b) They’ll make a quick call about what needs to happen next, including where to file the ticket and whether
to ask the player to come back later or to wait while we fix things.

* If there isn’t:
(a) If the issue is urgent, ask the player to wait and put the ticket in the “HoD Player Waiting” box.

(b) If the issue isn’t urgent, ask the player to come back later, and put the ticket in the inbox on the triage
desk.

</box>

===Handling returning players===

<box>

If you have a player returning with a query, this process means you ''should'' be able to find the status of the player’s query
fairly easily:

1. Check the various ticket outboxes. If the ticket is in an outbox, that should mean we’ve done as much as we can with it; hopefully there will be a final result attached, but it might be that we need more information. Check what the ticket says and handle accordingly.

2. Check the other ticket-in-progress boxes. If you can find a ticket but it’s not in an outbox, that means we’ve not finished handling the ticket. Consider whether the ticket is still in the right place, make sure the notes are up-to-date (''including that the player has returned'') and consider moving it to the “HoD Player Waiting” box for us to handle ASAP.

3. If you still can’t find a ticket, that implies we’ve dropped a ball. Create a new ticket and handle the new ticket appropriately, but if this is a returning player that probably means the urgency will be higher than it might otherwise be.

</box>
[[Category:GOD manual]]

File:Query form (front).png

2023-07-06T08:36:38Z

Jmabb:

screenshot example of a query slip

File:Query form 2-up (1).pdf

2023-07-06T08:29:25Z

Jmabb:

Query Forms

GOD physical organisation

2023-07-06T08:27:47Z

Jmabb: god layout & opening hours page

===Tent Layout===

If you’re interested in playing around with the layout, the tables we use are 6’×2.5’ (and 75cm tall).

'''TODO:''' add dimensions for the tent itself.

'''TODO:''' add an up-to-date image.

===Opening Hours===

These are aspirational, and subject to change according to conditions on the ground:

'''Thursday'''

12:00–18:00 set-up

18:00–22:00 pack hand-out (maybe!)

'''Friday'''

10:00–12:00 training

12:00–18:00 pack hand-out & OOC queries

18:00–01:00 full service

'''Saturday'''

09:30–01:00 full service

'''Sunday'''

09:30–15:00 full service

15:00–17:00 pack hand-in, tear-down

Potions desk

2023-07-06T08:19:15Z

Jmabb: potion making/brewing page added

===Brewing Potions===

During the event players will come in to make potions. There are potion guides behind the desk - '''you don’t have to memorise the recipes!'''. There is a potion guide that can be lent to players making potions and there is also a GOD crew only guide with sensitive in-game information that must not be handed out.

<box>
1. The player will give the name of the potion. We don’t have a great way of checking if someone knows how to brew any given potion; use your discretion amongst the following options:
* '''Use a nearby computer or tablet to look up the player’s character''' and see what potion skills that character has.
* '''Ask the player to show you their passport'''. If a player has this, it will show you what potions their character knew how to make at the time the passport was printed, which is very likely to be the same as the potions their character knows how to make now.
* '''Note down the player’s CID and the potions they’re making, then check them on the computers when you have free time later.''' This means that we might give out potions that we oughtn’t, but the vast majority of players are honest, so not being able to spot cheating until later in the day isn’t a big deal.
* '''Just take the player’s word for it'''. The vast majority of players are honest, and particularly if you’re busy it may not be worth the effort of doing anything more involved (although we also don’t want to encourage the few players who do cheat to come in at our busiest times to take advantage of this…).

2. Check that the player has handed in the correct resources. If an item is being used to allow resource substitutions, check that the correct amounts have been substituted.

3. Pick the potions from the potions matrix.

4. Issue the player with their potions.

</box>

===Making up more potions===

<box>

1. Get one of the heads of department to print out the potions needed.

2. Use the guillotines to cut the potions down to size.

3. Fold the potion slips in half.

4. Place the potion slips into small laminator pouches, with the folded-over RIP HERE end sticking out.

5. Feed pouches through the laminator starting with the pre-sealed/connected end of the pouch.

*'''Note: keep track of how many potions you’re feeding in vs getting out of the laminator!''' If a pouch doesn’t emerge, stop the laminator immediately and grab somebody (preferably Erin) to do emergency surgery.

</box>

[[Category:GOD manual]]

Lost property

2023-07-06T08:11:37Z

Jmabb:

Lost property is kept for 4 events after hand-in. If unclaimed after this period items will get moved in to “freecycle”, which will take place on the Sunday of each event. Monster get first dibs, followed by GOD, followed by a free-for-all. Lost property items are labelled, ribbon colour-coded and stored according to the event at which they were handed in.

All valuable lost property (jewellery, watches, wallets, phones, iPads &c.) should be logged by a department head and kept in a secure location.
All identifiable and valuable property should be returned to a player ASAP by contacting their nation’s Egregore.

Players are '''not allowed to rummage through lost property themselves '''– they must be able to accurately describe the missing item and a member of GOD crew must be present to assist with finding it.

'''TODO:'''
* Detailed process for freecycle
* Colour coding table
* Arrow handling

[[Category:GOD manual]]

Lost property

2023-07-06T08:11:13Z

Jmabb: lost property summary

Player Packs- GOD

2023-07-06T08:08:36Z

Jmabb:

===Set up===

<box>
Packing weekend has hopefully happened, at which the majority of packs – for bookings made in advance – will have been prepared. These packs will have been arranged, in order of PID, in folding crates, to form the Matrix.
* A list of pack corrections will have been provided via a webform and printed out and ''hopefully'' attached to a clipboard. '''Cross them out as you do them''' so we don’t duplicate effort.
* Some players will have provided proof that they’re entitled to a concession between packing weekend and arrival in the field. Graeme or Matt P will likely have provided the list of relevant PIDs, hopefully via the webform. Go through the Matrix, identify the relevant envelopes, scribble out “Confirm Concession” on the front of them, and replace them in the Matrix. Also cross the PIDs off the list of packs to pull to put in the Concessions crate.
* Concessions that still need to be confirmed need separating out from the Matrix into their own crate(s). '''Keep them in numerical order by PID!''' These want to end up living to the left end of the front desk. There should be a printed out list of PIDs to separate.
* Crew packs need separating out from the main Matrix into their own crate(s), kept in numerical order by PID, and moved to the right end of the front desk.
– Some crew packs will need to go into individual departmental boxes – see the departmental lists (which should
be printed out).

– The rest will want separating into crates to get handed out from GOD, and there’s a list for those, too.
* Plot will need to go into envelopes as it arrives. We’ll get printouts and lists of packs, and will need to go through the Matrix stuffing things into envelopes.

</box>

===Making packs up===

Over the course of the event, we’ll need to make up new packs for players, whether they booked after packing weekend or after characters die in the big battles on Saturday and Sunday mornings. A player pack consists of an envelope, a passport, and some number of resources. The front of the envelope is printed with a list of items the envelope should contain.
<box>

1. The passport and the envelope should come off the printer fairly close together. Fold up the passport (''if A4'') and place it in the envelope.

2. Add coins to the pack to the given value, according to the listed denominations (see [[Currency]] for help).

3. Add materials, card resources, and Bourse resources in the stated quantities.

4. Some packs will contain items that are listed as a five-digit number followed by a brief description. These are unique ID numbers for Ribbons. Check whether the ribbon in question has already been printed out, by looking through the great big board of ribbons. If not, print it, and add it to the pack.

5. Put the pack wherever the pack needs to go, probably either directly into the player’s hands, or into the box for players who are going to come back to pick items up later.

</box>

===Hand out===

<box>

1. A player will get to the front of the queue. Ask them their PID.

2. If they don’t know their PID, ask them if they have their ticket; everyone should have a ticket, either printed or on their phone, which has their PID on it.

3. If they still don’t have their PID, to speak to somebody at a computer, or someone with a clipboard of names and PIDs if one exists, and then come back to the pack handout queue.

4. Find their pack.

5. Ask them to confirm their name – either of their player/wallet name or character name is fine!

6. Hand over their pack.

7. Circle back to the head of the queue and repeat.

Some players will have '''proxies''' registered in the system. If this is the case, their pack will have the PIDs of their proxies printed on the envelope. If someone comes to pick up a pack for another player, first ask if they are registered as a proxy.

*If they say yes:
1. If they say yes, ask for the PID of the player whose pack they are collecting.

2. Find the pack, as above.

3. Ask for the PID of the player who is collecting the pack. Check that it is printed on the envelope as a registered
proxy.

4. Confirm the name of the player whose pack is being collected.

5. Hand over the pack, and ask if the player needs to collect any other packs. :)

* If they say no, they are not registered as a proxy:
1. Explain about the proxy system: between events, the player who wants to nominate a proxy should e-mail admin@profounddecisions.co.uk with their PID and the PIDs of any proxies they want to set up.

2. Ask what their relationship to the player whose pack they wish to collect is.

* If they have the other person’s ticket – either on a print-out or on a phone or similar – we can take that as proof that they’re allowed the pack, so hand it out.
* If they are a parent, this should be recorded in the computer system. Double-check, or get someone else to, and then hand over the pack.
* Otherwise, explain that you will need to see proof that they have the other player’s permission to collect their pack on their behalf, e.g. photo ID of or a note from the other player. (This is to avoid theft of in-game resources, which would otherwise be very easy!)
* If you’re at all unsure, escalate to a head of department.
</box>

===Missing Packs===

Despite everyone’s best efforts, packs sometimes wind up in the wrong place. It is actually pretty rare for them to just not get printed at all, though, so there’s several things to check first.
<box>

1. Ask whether the player is '''crew or a concession'''. If yes, check those matrices.
*Depending on which crew team they are, their pack might have gone to their team leader/Head of Department already, so they’ll need to go check there. There will normally be someone specifically handling the crew desk, who should have a list.

2. Ask whether the player was asked to come back later. If yes, '''check the query slips boxes''' to see if there’s a query slip tracking this already.

3. Numbers are tricksy and packs hide. Get someone else to double-check the PID with the player, confirm it’s the number you looked for, and look for that number.

4. Even if the player isn’t crew or a concession, check those matrices.

5. Check whether the player has got their PID correct by looking them up on the computer system ''(If they haven't, repeat from step 1!)''

6. If the player’s PID was correct and you still can’t find their pack, it’s time to start checking whether they were ''actually'' booked

7. If they seem to be booked and there’s no pack, write their details down on a query slip and – depending on the queues – either ask them to come back later or get them to wait while a head of department investigates further.

</box>

===Break Down===

At some point, we start assuming that any packs that haven’t been collected yet aren’t going to be, and begin breaking them back down. This is a task that involves working with computers, so ''technically'' belongs in Online Processes but involves packs and makes more sense here.

Typically this happens once we get to a lull on Saturday morning; we don’t want to do it earlier, as we’d rather have players take their packs away than have to break them down, but we also want to get the job done when we have a suitable quiet period, and ideally in time to let Plot know about things they need to re-plan because plot hooks haven’t been delivered. As part of this, if any character packs have been delivered to other crew departments, someone with a radio should get in touch with the heads of those departments to get any uncollected packs back from them.

<box>
Once you’re logged in to the website and you’ve clicked “Crew” from the home page:

1. Click “Character” in the tabs across the top of the screen.

2. In the CID search box, enter the PID from the top right of the player pack you are working on, and press Tab or Enter. (You don’t need to enter the full CID!)

3. Click “Inventory” from the tabs underneath the character name.

4. Click “Not Collected” from the buttons down the right-hand side of the screen.

5. Click “Confirm” on the pop-up that appears.

6. Dump the resources into your big crate of for someone else (possibly your future self!) to sort.

7. If there are any plot documents or arcane projections in the envelope, note the PID (if it isn’t printed on the documents already), and pass to a head of department.
*Arcane Projections will get filed to deliver at a future event.
*Plot documents get handed to someone in the Plot department; they can then decide if they need to re-write some of their plots on the fly to account for some of the documents not having been delivered.

8. Click “Save”.

9. Repeat from Step 2 with the next pack.

</box>

===Resource Hand-in===

'''GOD is not a bank.'''

In general, players are encouraged to keep hold of their resources, for two reasons. The first is that this makes more opportunity for game play: it increases the chances for in-game loss or theft, and the consequences of same. The second is it means we don’t have to count everything in, find the space to store stuff, then count everything out again. This also means that in general players are discouraged from handing resources in at GOD, with two main exceptions:

'''1.''' They want to use the resource immediately: for example, they want to deposit three Iridescent Gloaming so that they
can perform a specific ritual ''or''

'''2.''' They want to use the resources during downtime, to create items or perform actions.

In the first case, the player should be directed to the queue for computer-based queries. In the second case, hand-in of resources for use over downtime isn’t accepted before Sunday, unless the player is leaving site before Sunday. Players should be given a hand-in slip and a plastic bag, told to deposit only the resources they actually want to use, and asked to fill out the form, then return to deposit their bag and completed hand-in slip.

===Processing Hand-in bags===

Properly, this section belongs in [[GOD manual| Online Processes]], but alas it makes more sense to put it here, so here it is.

<box>
Once you’re logged in to the website and you’ve clicked “Crew” from the home page:

1. Click “GOD”. You will land on the “Book-in Baggy” page.

2. Enter the PID in the CID box, and press Tab or Enter. (You don’t have to actually bother with the full CID!) The correct event should automatically be selected in the dropdown box.
* If the PID doesn’t match the name, you’ll have to look it up.

3. Check that the quantity of each resource in the baggy matches the quantity written on the slip, and enter the quantity into the relevant field on the computer.
* If there is a discrepancy between the hand-in slip and the contents of the baggy, call someone else over to double-count. Amend the slip as necessary, and initial the amendments to make it clear that you’re the one who made them.

4. If there is anything else odd (e.g. ribbons, herbs) in the bag, keep it separate and flag with a head of department.

5. Dump the resources into your in-crate for someone else to take away and sort as you go.

6. Save the Book-in Baggy form.

7. '''DO NOT''' click “Confirm” until you have copied the '''reference number''' into the field on the hand-in slip.

8. Ideally, keep the slips in order by PID.

9. Repeat from step 2 with the next baggy.

When you finish processing hand-in baggies, hand over the pile of slips to one of the heads of department. Let them
know if the slips aren’t in order by PID.

</box>
[[Category:GOD manual]]

Player Packs- GOD

2023-07-06T08:06:34Z

Jmabb:

===Set up===

<box>
Packing weekend has hopefully happened, at which the majority of packs – for bookings made in advance – will have been prepared. These packs will have been arranged, in order of PID, in folding crates, to form the Matrix.
* A list of pack corrections will have been provided via a webform and printed out and ''hopefully'' attached to a clipboard. '''Cross them out as you do them''' so we don’t duplicate effort.
* Some players will have provided proof that they’re entitled to a concession between packing weekend and arrival in the field. Graeme or Matt P will likely have provided the list of relevant PIDs, hopefully via the webform. Go through the Matrix, identify the relevant envelopes, scribble out “Confirm Concession” on the front of them, and replace them in the Matrix. Also cross the PIDs off the list of packs to pull to put in the Concessions crate.
* Concessions that still need to be confirmed need separating out from the Matrix into their own crate(s). '''Keep them in numerical order by PID!''' These want to end up living to the left end of the front desk. There should be a printed out list of PIDs to separate.
* Crew packs need separating out from the main Matrix into their own crate(s), kept in numerical order by PID, and moved to the right end of the front desk.
– Some crew packs will need to go into individual departmental boxes – see the departmental lists (which should
be printed out).

– The rest will want separating into crates to get handed out from GOD, and there’s a list for those, too.
* Plot will need to go into envelopes as it arrives. We’ll get printouts and lists of packs, and will need to go through the Matrix stuffing things into envelopes.

</box>

===Making packs up===

Over the course of the event, we’ll need to make up new packs for players, whether they booked after packing weekend or after characters die in the big battles on Saturday and Sunday mornings. A player pack consists of an envelope, a passport, and some number of resources. The front of the envelope is printed with a list of items the envelope should contain.
<box>

1. The passport and the envelope should come off the printer fairly close together. Fold up the passport (''if A4'') and place it in the envelope.

2. Add coins to the pack to the given value, according to the listed denominations (see [[Currency]] for help).

3. Add materials, card resources, and Bourse resources in the stated quantities.

4. Some packs will contain items that are listed as a five-digit number followed by a brief description. These are unique ID numbers for Ribbons. Check whether the ribbon in question has already been printed out, by looking through the great big board of ribbons. If not, print it, and add it to the pack.

5. Put the pack wherever the pack needs to go, probably either directly into the player’s hands, or into the box for players who are going to come back to pick items up later.

</box>

===Hand out===

<box>

1. A player will get to the front of the queue. Ask them their PID.

2. If they don’t know their PID, ask them if they have their ticket; everyone should have a ticket, either printed or on their phone, which has their PID on it.

3. If they still don’t have their PID, to speak to somebody at a computer, or someone with a clipboard of names and PIDs if one exists, and then come back to the pack handout queue.

4. Find their pack.

5. Ask them to confirm their name – either of their player/wallet name or character name is fine!

6. Hand over their pack.

7. Circle back to the head of the queue and repeat.

Some players will have '''proxies''' registered in the system. If this is the case, their pack will have the PIDs of their proxies printed on the envelope. If someone comes to pick up a pack for another player, first ask if they are registered as a proxy.

*If they say yes:
1. If they say yes, ask for the PID of the player whose pack they are collecting.

2. Find the pack, as above.

3. Ask for the PID of the player who is collecting the pack. Check that it is printed on the envelope as a registered
proxy.

4. Confirm the name of the player whose pack is being collected.

5. Hand over the pack, and ask if the player needs to collect any other packs. :)

* If they say no, they are not registered as a proxy:
1. Explain about the proxy system: between events, the player who wants to nominate a proxy should e-mail admin@profounddecisions.co.uk with their PID and the PIDs of any proxies they want to set up.

2. Ask what their relationship to the player whose pack they wish to collect is.

* If they have the other person’s ticket – either on a print-out or on a phone or similar – we can take that as proof that they’re allowed the pack, so hand it out.
* If they are a parent, this should be recorded in the computer system. Double-check, or get someone else to, and then hand over the pack.
* Otherwise, explain that you will need to see proof that they have the other player’s permission to collect their pack on their behalf, e.g. photo ID of or a note from the other player. (This is to avoid theft of in-game resources, which would otherwise be very easy!)
* If you’re at all unsure, escalate to a head of department.
</box>

===Missing Packs===

Despite everyone’s best efforts, packs sometimes wind up in the wrong place. It is actually pretty rare for them to just not get printed at all, though, so there’s several things to check first.
<box>

1. Ask whether the player is '''crew or a concession'''. If yes, check those matrices.
*Depending on which crew team they are, their pack might have gone to their team leader/Head of Department already, so they’ll need to go check there. There will normally be someone specifically handling the crew desk, who should have a list.

2. Ask whether the player was asked to come back later. If yes, '''check the query slips boxes''' to see if there’s a query slip tracking this already.

3. Numbers are tricksy and packs hide. Get someone else to double-check the PID with the player, confirm it’s the number you looked for, and look for that number.

4. Even if the player isn’t crew or a concession, check those matrices.

5. Check whether the player has got their PID correct by looking them up on the computer system ''(If they haven't, repeat from step 1!)''

6. If the player’s PID was correct and you still can’t find their pack, it’s time to start checking whether they were ''actually'' booked

7. If they seem to be booked and there’s no pack, write their details down on a query slip and – depending on the queues – either ask them to come back later or get them to wait while a head of department investigates further.

</box>

===Break Down===

At some point, we start assuming that any packs that haven’t been collected yet aren’t going to be, and begin breaking them back down. This is a task that involves working with computers, so ''technically'' belongs in Online Processes but involves packs and makes more sense here.

Typically this happens once we get to a lull on Saturday morning; we don’t want to do it earlier, as we’d rather have players take their packs away than have to break them down, but we also want to get the job done when we have a suitable quiet period, and ideally in time to let Plot know about things they need to re-plan because plot hooks haven’t been delivered. As part of this, if any character packs have been delivered to other crew departments, someone with a radio should get in touch with the heads of those departments to get any uncollected packs back from them.

<box>
Once you’re logged in to the website and you’ve clicked “Crew” from the home page:

1. Click “Character” in the tabs across the top of the screen.

2. In the CID search box, enter the PID from the top right of the player pack you are working on, and press Tab or Enter. (You don’t need to enter the full CID!)

3. Click “Inventory” from the tabs underneath the character name.

4. Click “Not Collected” from the buttons down the right-hand side of the screen.

5. Click “Confirm” on the pop-up that appears.

6. Dump the resources into your big crate of for someone else (possibly your future self!) to sort.

7. If there are any plot documents or arcane projections in the envelope, note the PID (if it isn’t printed on the documents already), and pass to a head of department.
*Arcane Projections will get filed to deliver at a future event.
*Plot documents get handed to someone in the Plot department; they can then decide if they need to re-write some of their plots on the fly to account for some of the documents not having been delivered.

8. Click “Save”.

9. Repeat from Step 2 with the next pack.

</box>

===Resource Hand-in===

'''GOD is not a bank.'''

In general, players are encouraged to keep hold of their resources, for two reasons. The first is that this makes more opportunity for game play: it increases the chances for in-game loss or theft, and the consequences of same. The second is it means we don’t have to count everything in, find the space to store stuff, then count everything out again. This also means that in general players are discouraged from handing resources in at GOD, with two main exceptions:

'''1.''' They want to use the resource immediately: for example, they want to deposit three Iridescent Gloaming so that they
can perform a specific ritual ''or''

'''2.''' They want to use the resources during downtime, to create items or perform actions.

In the first case, the player should be directed to the queue for computer-based queries. In the second case, hand-in of resources for use over downtime isn’t accepted before Sunday, unless the player is leaving site before Sunday. Players should be given a hand-in slip and a plastic bag, told to deposit only the resources they actually want to use, and asked to fill out the form, then return to deposit their bag and completed hand-in slip.

===Processing Hand-in bags===

Properly, this section belongs in [[GOD manual| Online Processes]], but alas it makes more sense to put it here, so here it is.

<box>
Once you’re logged in to the website and you’ve clicked “Crew” from the home page:

1. Click “GOD”. You will land on the “Book-in Baggy” page.

2. Enter the PID in the CID box, and press Tab or Enter. (You don’t have to actually bother with the full CID!) The correct event should automatically be selected in the dropdown box.
* If the PID doesn’t match the name, you’ll have to look it up.

3. Check that the quantity of each resource in the baggy matches the quantity written on the slip, and enter the quantity into the relevant field on the computer.
* If there is a discrepancy between the hand-in slip and the contents of the baggy, call someone else over to double-count. Amend the slip as necessary, and initial the amendments to make it clear that you’re the one who made them.

4. If there is anything else odd (e.g. ribbons, herbs) in the bag, keep it separate and flag with a head of department.

5. Dump the resources into your in-crate for someone else to take away and sort as you go.

6. Save the Book-in Baggy form.

7. '''DO NOT''' click “Confirm” until you have copied the '''reference number''' into the field on the hand-in slip.

8. Ideally, keep the slips in order by PID.

9. Repeat from step 2 with the next baggy.

When you finish processing hand-in baggies, hand over the pile of slips to one of the heads of department. Let them
know if the slips aren’t in order by PID.

</box>

Player Packs- GOD

2023-07-04T16:31:50Z

Jmabb: pack handling GOD

GOD manual

2023-07-04T15:56:25Z

Jmabb: /* Contents */

== Introduction ==

<blockquote>
"In the beginning, there was nothing. Which exploded."
Terry Pratchett, ''"Lords and Ladies"''
</blockquote>

'''The ''GOD manual'' tells GOD crew how to do things.''' It's the repository of knowledge that describes the majority of processes that are followed at (and occasionally between) events.

Historically, the GOD manual took the form of a PDF. As of July 2023, we're in the process of migrating it to this wiki. If you'd like to help, get in touch with Adam. Until that process is completed, you will likely need to check both this wiki and the PDF manual.

{{Caution|'''This wiki is publicly accessible.''' The vast majority of things that GOD do are fine to publish here, but be careful not to reference details of plot that aren't generally available. You can talk about the existence of (say) [https://www.profounddecisions.co.uk/empire-wiki/Children_in_bloom#Chaos_Fruit chaos fruit], since that's available on the player wiki, and you can talk about how we organise them and print them, but don't give any details about how they work from a plot or game mechanic perspective. Equally, if you want to provide screenshots or similar, make sure you don't use a real player account; use Crew Room (PID 0) or Ref Dummy Character (CID 0.1).}}

== Contents ==

* [[Welcome to GOD]]
*[[Currency]]
*[[Materials]]
*[[Cards & Lammies]]
*[[Bourse Resources]]
*[[Task Tracking]]
*[[Player Packs- GOD]]

== Editing this manual ==

* <del>'''Create subpages to this one''' with a name like with names like [[GOD manual/Potions]] when you're documenting new things. The exception to this guideline is if the topic is likely to be widely applicable to non-GOD crew, in which case create a new top level page (or link to the appropriate existing one.)</del>

* '''Give pages clear, unambiguous, non-conflicting names'''. This may require some careful wordsmithing as we're operating in the same namespace as the rest of the crew wiki.

* '''Cross-linking is good.''' Try to avoid repeating yourself – having the same information in multiple places is a good way to have multiple bits of information fall out of sync with each other – and instead write something once and link to it anywhere else it's useful.

* '''Make things easy to link to''' by breaking things up into discrete bite-sized chunks. Done well, we should be able to link directly to relevant pages from various parts of the crew website interface, so that the wiki provides effective context-sensitive help for all tasks.

* '''Put all the manual pages in the <code>GOD manual</code> category''' to make sure all pages can be found easily. This is done by putting the code <code><nowiki>[[Category:GOD manual]]</nowiki></code> at the bottom of each page.

* '''Document the 'why' as well as the 'what''''. There are competing goals to everything we're writing here: we want things that are quick and easy and straightforward to follow, and we ''also'' want to document why we do things the way we do them, so if we want to change things in future we have half a chance of understanding why things are the way they are now. Consider having separate sections in any process documentation for (a) a process overview for folk who know what they're doing but want a reminder of some specifics, (b) a detailed step-by-step guide for folk who aren't familiar with the process, and (c) a final section explaining the reasoning behind anything that isn't obvious.

[[Category:GOD manual]]

GOD manual

2023-07-04T15:55:31Z

Jmabb: /* Contents */

== Introduction ==

<blockquote>
"In the beginning, there was nothing. Which exploded."
Terry Pratchett, ''"Lords and Ladies"''
</blockquote>

'''The ''GOD manual'' tells GOD crew how to do things.''' It's the repository of knowledge that describes the majority of processes that are followed at (and occasionally between) events.

Historically, the GOD manual took the form of a PDF. As of July 2023, we're in the process of migrating it to this wiki. If you'd like to help, get in touch with Adam. Until that process is completed, you will likely need to check both this wiki and the PDF manual.

{{Caution|'''This wiki is publicly accessible.''' The vast majority of things that GOD do are fine to publish here, but be careful not to reference details of plot that aren't generally available. You can talk about the existence of (say) [https://www.profounddecisions.co.uk/empire-wiki/Children_in_bloom#Chaos_Fruit chaos fruit], since that's available on the player wiki, and you can talk about how we organise them and print them, but don't give any details about how they work from a plot or game mechanic perspective. Equally, if you want to provide screenshots or similar, make sure you don't use a real player account; use Crew Room (PID 0) or Ref Dummy Character (CID 0.1).}}

== Contents ==

* [[Welcome to GOD]]
*[[Currency]]
*[[Materials]]
*[[Cards & Lammies]]
*[[Bourse Resources]]
*[[Task Tracking]]
*[[Player Packs]]

== Editing this manual ==

* <del>'''Create subpages to this one''' with a name like with names like [[GOD manual/Potions]] when you're documenting new things. The exception to this guideline is if the topic is likely to be widely applicable to non-GOD crew, in which case create a new top level page (or link to the appropriate existing one.)</del>

* '''Give pages clear, unambiguous, non-conflicting names'''. This may require some careful wordsmithing as we're operating in the same namespace as the rest of the crew wiki.

* '''Cross-linking is good.''' Try to avoid repeating yourself – having the same information in multiple places is a good way to have multiple bits of information fall out of sync with each other – and instead write something once and link to it anywhere else it's useful.

* '''Make things easy to link to''' by breaking things up into discrete bite-sized chunks. Done well, we should be able to link directly to relevant pages from various parts of the crew website interface, so that the wiki provides effective context-sensitive help for all tasks.

* '''Put all the manual pages in the <code>GOD manual</code> category''' to make sure all pages can be found easily. This is done by putting the code <code><nowiki>[[Category:GOD manual]]</nowiki></code> at the bottom of each page.

* '''Document the 'why' as well as the 'what''''. There are competing goals to everything we're writing here: we want things that are quick and easy and straightforward to follow, and we ''also'' want to document why we do things the way we do them, so if we want to change things in future we have half a chance of understanding why things are the way they are now. Consider having separate sections in any process documentation for (a) a process overview for folk who know what they're doing but want a reminder of some specifics, (b) a detailed step-by-step guide for folk who aren't familiar with the process, and (c) a final section explaining the reasoning behind anything that isn't obvious.

[[Category:GOD manual]]

Bourse Resources

2023-07-04T15:45:37Z

Jmabb:

Three materials are “too bulky to easily transport to Anvil”, so “the Imperial civil service provide Bourse certificates for every wain” of '''Mithril''', '''Weirwood''', and '''White Granite'''.

Bourse certificates resemble large banknotes; there have been several printings, and Bourse certificates in which the Throne is matte black are just as valid as Bourse certificates in which the Throne is sparkly and silver. When these are handed in, return them to the big box. You might, ''very occasionally'', have players hand in very old, very battered Bourse certificates printed on vellum. These should be treated as valid, but instead of returning them to the main stock of Bourse resources, rip them up and put them in the bin.

*[https://www.profounddecisions.co.uk/empire-wiki/Mithril Mithril- Player wiki]
*[https://www.profounddecisions.co.uk/empire-wiki/Weirwood Weirwood- Player wiki]
*[https://www.profounddecisions.co.uk/empire-wiki/White_granite White granite- Player wiki]

[[Category:GOD manual]]

Task Tracking

2023-07-04T15:45:16Z

Jmabb:

If you’re dealing with a query of any sort, and either sending the player away or sending them to talk to one of the heads of department, you need to write this down on one of the pre printed forms, and put that form in the relevant inbox. This reduces the risk of players waiting around forgotten, or of them needing to come back multiple times for the same issue.

===Before sending a player away===
<box>

Before sending a player away, or sending them to wait for a head of department:

1. On one of the A5 query sheets, record:
* Your name
* The PID and name of the player
* The current time and date
* Any other involved PIDs or ribbon IDs
* A description of what needs doing to resolve the query

2. Is someone currently triaging query sheets?
* If there is:
(a) Pass the sheet to them and give them a chance to review it.

(b) They’ll make a quick call about what needs to happen next, including where to file the ticket and whether
to ask the player to come back later or to wait while we fix things.

* If there isn’t:
(a) If the issue is urgent, ask the player to wait and put the ticket in the “HoD Player Waiting” box.

(b) If the issue isn’t urgent, ask the player to come back later, and put the ticket in the inbox on the triage
desk.

</box>

===Handling returning players===

<box>

If you have a player returning with a query, this process means you ''should'' be able to find the status of the player’s query
fairly easily:

1. Check the various ticket outboxes. If the ticket is in an outbox, that should mean we’ve done as much as we can with it; hopefully there will be a final result attached, but it might be that we need more information. Check what the ticket says and handle accordingly.

2. Check the other ticket-in-progress boxes. If you can find a ticket but it’s not in an outbox, that means we’ve not finished handling the ticket. Consider whether the ticket is still in the right place, make sure the notes are up-to-date (''including that the player has returned'') and consider moving it to the “HoD Player Waiting” box for us to handle ASAP.

3. If you still can’t find a ticket, that implies we’ve dropped a ball. Create a new ticket and handle the new ticket appropriately, but if this is a returning player that probably means the urgency will be higher than it might otherwise be.

</box>
[[Category:GOD manual]]

Task Tracking

2023-07-04T15:43:57Z

Jmabb: Task tracking/ query handling

If you’re dealing with a query of any sort, and either sending the player away or sending them to talk to one of the heads of department, you need to write this down on one of the pre printed forms, and put that form in the relevant inbox. This reduces the risk of players waiting around forgotten, or of them needing to come back multiple times for the same issue.

===Before sending a player away===
<box>

Before sending a player away, or sending them to wait for a head of department:

1. On one of the A5 query sheets, record:
* Your name
* The PID and name of the player
* The current time and date
* Any other involved PIDs or ribbon IDs
* A description of what needs doing to resolve the query

2. Is someone currently triaging query sheets?
* If there is:
(a) Pass the sheet to them and give them a chance to review it.

(b) They’ll make a quick call about what needs to happen next, including where to file the ticket and whether
to ask the player to come back later or to wait while we fix things.

* If there isn’t:
(a) If the issue is urgent, ask the player to wait and put the ticket in the “HoD Player Waiting” box.

(b) If the issue isn’t urgent, ask the player to come back later, and put the ticket in the inbox on the triage
desk.

</box>

===Handling returning players===

<box>

If you have a player returning with a query, this process means you ''should'' be able to find the status of the player’s query
fairly easily:

1. Check the various ticket outboxes. If the ticket is in an outbox, that should mean we’ve done as much as we can with it; hopefully there will be a final result attached, but it might be that we need more information. Check what the ticket says and handle accordingly.

2. Check the other ticket-in-progress boxes. If you can find a ticket but it’s not in an outbox, that means we’ve not finished handling the ticket. Consider whether the ticket is still in the right place, make sure the notes are up-to-date (''including that the player has returned'') and consider moving it to the “HoD Player Waiting” box for us to handle ASAP.

3. If you still can’t find a ticket, that implies we’ve dropped a ball. Create a new ticket and handle the new ticket appropriately, but if this is a returning player that probably means the urgency will be higher than it might otherwise be.

</box>

GOD manual

2023-07-04T15:14:27Z

Jmabb: /* Contents */

== Introduction ==

<blockquote>
"In the beginning, there was nothing. Which exploded."
Terry Pratchett, ''"Lords and Ladies"''
</blockquote>

'''The ''GOD manual'' tells GOD crew how to do things.''' It's the repository of knowledge that describes the majority of processes that are followed at (and occasionally between) events.

Historically, the GOD manual took the form of a PDF. As of July 2023, we're in the process of migrating it to this wiki. If you'd like to help, get in touch with Adam. Until that process is completed, you will likely need to check both this wiki and the PDF manual.

{{Caution|'''This wiki is publicly accessible.''' The vast majority of things that GOD do are fine to publish here, but be careful not to reference details of plot that aren't generally available. You can talk about the existence of (say) [https://www.profounddecisions.co.uk/empire-wiki/Children_in_bloom#Chaos_Fruit chaos fruit], since that's available on the player wiki, and you can talk about how we organise them and print them, but don't give any details about how they work from a plot or game mechanic perspective. Equally, if you want to provide screenshots or similar, make sure you don't use a real player account; use Crew Room (PID 0) or Ref Dummy Character (CID 0.1).}}

== Contents ==

* [[Welcome to GOD]]
*[[Currency]]
*[[Materials]]
*[[Cards & Lammies]]
*[[Bourse Resources]]
*[[Task Tracking]]

== Editing this manual ==

* <del>'''Create subpages to this one''' with a name like with names like [[GOD manual/Potions]] when you're documenting new things. The exception to this guideline is if the topic is likely to be widely applicable to non-GOD crew, in which case create a new top level page (or link to the appropriate existing one.)</del>

* '''Give pages clear, unambiguous, non-conflicting names'''. This may require some careful wordsmithing as we're operating in the same namespace as the rest of the crew wiki.

* '''Cross-linking is good.''' Try to avoid repeating yourself – having the same information in multiple places is a good way to have multiple bits of information fall out of sync with each other – and instead write something once and link to it anywhere else it's useful.

* '''Make things easy to link to''' by breaking things up into discrete bite-sized chunks. Done well, we should be able to link directly to relevant pages from various parts of the crew website interface, so that the wiki provides effective context-sensitive help for all tasks.

* '''Put all the manual pages in the <code>GOD manual</code> category''' to make sure all pages can be found easily. This is done by putting the code <code><nowiki>[[Category:GOD manual]]</nowiki></code> at the bottom of each page.

* '''Document the 'why' as well as the 'what''''. There are competing goals to everything we're writing here: we want things that are quick and easy and straightforward to follow, and we ''also'' want to document why we do things the way we do them, so if we want to change things in future we have half a chance of understanding why things are the way they are now. Consider having separate sections in any process documentation for (a) a process overview for folk who know what they're doing but want a reminder of some specifics, (b) a detailed step-by-step guide for folk who aren't familiar with the process, and (c) a final section explaining the reasoning behind anything that isn't obvious.

[[Category:GOD manual]]

Bourse Resources

2023-07-04T15:09:19Z

Jmabb: bourse resource summary and links

GOD manual

2023-07-04T15:02:24Z

Jmabb: /* Contents */

== Introduction ==

<blockquote>
"In the beginning, there was nothing. Which exploded."
Terry Pratchett, ''"Lords and Ladies"''
</blockquote>

'''The ''GOD manual'' tells GOD crew how to do things.''' It's the repository of knowledge that describes the majority of processes that are followed at (and occasionally between) events.

Historically, the GOD manual took the form of a PDF. As of July 2023, we're in the process of migrating it to this wiki. If you'd like to help, get in touch with Adam. Until that process is completed, you will likely need to check both this wiki and the PDF manual.

{{Caution|'''This wiki is publicly accessible.''' The vast majority of things that GOD do are fine to publish here, but be careful not to reference details of plot that aren't generally available. You can talk about the existence of (say) [https://www.profounddecisions.co.uk/empire-wiki/Children_in_bloom#Chaos_Fruit chaos fruit], since that's available on the player wiki, and you can talk about how we organise them and print them, but don't give any details about how they work from a plot or game mechanic perspective. Equally, if you want to provide screenshots or similar, make sure you don't use a real player account; use Crew Room (PID 0) or Ref Dummy Character (CID 0.1).}}

== Contents ==

* [[Welcome to GOD]]
*[[Currency]]
*[[Materials]]
*[[Cards & Lammies]]
*[[Bourse Resources]]

== Editing this manual ==

* <del>'''Create subpages to this one''' with a name like with names like [[GOD manual/Potions]] when you're documenting new things. The exception to this guideline is if the topic is likely to be widely applicable to non-GOD crew, in which case create a new top level page (or link to the appropriate existing one.)</del>

* '''Give pages clear, unambiguous, non-conflicting names'''. This may require some careful wordsmithing as we're operating in the same namespace as the rest of the crew wiki.

* '''Cross-linking is good.''' Try to avoid repeating yourself – having the same information in multiple places is a good way to have multiple bits of information fall out of sync with each other – and instead write something once and link to it anywhere else it's useful.

* '''Make things easy to link to''' by breaking things up into discrete bite-sized chunks. Done well, we should be able to link directly to relevant pages from various parts of the crew website interface, so that the wiki provides effective context-sensitive help for all tasks.

* '''Put all the manual pages in the <code>GOD manual</code> category''' to make sure all pages can be found easily. This is done by putting the code <code><nowiki>[[Category:GOD manual]]</nowiki></code> at the bottom of each page.

* '''Document the 'why' as well as the 'what''''. There are competing goals to everything we're writing here: we want things that are quick and easy and straightforward to follow, and we ''also'' want to document why we do things the way we do them, so if we want to change things in future we have half a chance of understanding why things are the way they are now. Consider having separate sections in any process documentation for (a) a process overview for folk who know what they're doing but want a reminder of some specifics, (b) a detailed step-by-step guide for folk who aren't familiar with the process, and (c) a final section explaining the reasoning behind anything that isn't obvious.

[[Category:GOD manual]]

Cards & Lammies

2023-07-04T15:00:56Z

Jmabb: cards and lammies

Most cards are used to indicate in-game items with special properties. In-game, the cards don’t exist, so players should always have some physical object to represent the actual item, as well as any card or lammy.

===Herbs===
[https://www.profounddecisions.co.uk/empire-wiki/Herb Herbs- Player wiki]

Herbs are '''all cards'''; players largely receive these in their event packs, and we refer to the basic pack of herbs that goes into an event pack as a “herb garden”: 2 bladeroot, 2 cerulean mazzarine, 2 imperial roseweald, 2 marrowort, 6 true vervain.

===Potions===
[https://www.profounddecisions.co.uk/empire-wiki/Potion Potions-Player Wiki]

Represented as a '''mixture of cards and lammies'''. Players will come to GOD to mix potions

===Mana Crystals & Vis===
[https://www.profounddecisions.co.uk/empire-wiki/Mana_site Mana Site- Player wiki]

[https://www.profounddecisions.co.uk/empire-wiki/Vis Vis- Player wiki]

'''Both are represented as cards'''

Crystallised mana is used in some potion recipes and in magic. As with herbs, mana mostly gets given to players in their event packs, and we refer to the basic pack of mana crystals as a “mana site” ''(seven cards)''.

There are six types of “vis”, one for each of the magical realms. One vis is worth three crystallised mana, but only when used for a ritual in the relevant realm. The realm is helpfully included in the first line of small text on the cards.

===Liao===
[https://www.profounddecisions.co.uk/empire-wiki/Liao Liao- Player wiki]

'''Represented as cards''', and used in ceremonies performed by priests.
The basic set of liao cards that goes into event packs is five.

'''''Not to be confused with True Liao, which is much rarer and is represented by Ribbons'''''

===Anointing Cards===
[https://www.profounddecisions.co.uk/empire-wiki/Anointing Anointing- Player wiki]

Also referred to as “virtue cards” or "aura cards"

Anointing cards don’t represent real items- they’re used by priests who are performing the “Anointing” ceremony, who can then give the cards out to the folk they’ve anointed. The cards are specific to each of the in-game virtues, and tell the player the roleplaying effect of the anointing they’ve received.

===Wounds===
[https://www.profounddecisions.co.uk/empire-wiki/Combat#Traumatic_Wounds Traumatic Wounds- Player wiki]

Wound lammies are given out by refs in certain circumstances, to provide details of a wound a character has suffered. They’re very rarely relevant to GOD, but they do exist, and you may see them or need to laminate them sometimes.

[[Category:GOD manual]]

Cards & Lammies

2023-07-04T14:52:21Z

Jmabb: Created page with "Most cards are used to indicate in-game items with special properties. In-game, the cards don’t exist, so players should always have some physical object to represent the ac..."

Materials

2023-07-04T14:35:12Z

Jmabb:

[[https://www.profounddecisions.co.uk/empire-wiki/Materials Materials- Player Wiki]]

The big eight exist in denominations of 1, 3, and 5. They’re different sizes, and they’re all also marked in some way, though some of these marks are clearer and easier to see than others. See illustration for an idea of what you’re looking for and where to look for it.

[[File:Screen Shot 2023-07-04 at 15.27.02.png|thumb|Resource cheat sheet]]

[[Category:GOD manual]]