Purpose of Thread

To collectively and comprehensively define an Adventurer's Guild, and determine how it can be run using npcs / opcs, game mechanic obstacles, and how to overcome those obstacles. This is a living document that will be updated as the concept is refined.

Core Arguments

Pro

reserved

Con

reserved

Game Mechanic Changes

Required

• Contracts (see link)

As contracts are written in ink, they cannot be modified once written on. If a person chooses to sign a blank contract or a contract with blank fields, then they accept the risk that such action entails. Fields can be permanently written on at any time. However, if either party disagrees with a field, then the contract is effectively wasted.

Suggested

Customized contracts that are simple for NPCs, but complex for PCs. Allowing for OPCs to offer contracts to NPCs and PCs

Currently Known Game Mechanics

Supporting

Contracts are not modifiable when signed by both parties.

Obstructing

"Contracts need to be signed by the parties in a single session" due to the potential of modifying the contract after one party has signed it.

Posted By Tarloch at 5:39 PM - Mon Nov 25 2019

That is certainly an ambitious project, good luck!

Aye it is. I hope that Contract 2 can be mostly automated by using the same npc employee rules that would be necessary to create a contract to go harvest 10 apples.

1. if possible, the npc/opc receptionist/desk receive the requester's requester signed Contract(1) and hold on to it.
2. The adventurer that has been promoted to be the branch, hub, hq master would ensure that Contract(1) is acceptable and sign, if it is.
3. The master would then create the necessary contract for Contract(2).
4. The npc/opc receptionist/desk would then offer Contract(2) to individuals with the proper identity and physical id.

Contracts

Requirement: Signing contracts when not in the presence of the other party.

Reasoning: Contracts need to be able to be signed without both parties being present. So that an offline guild official can review and sign a request when he or she comes online.

Obstructing Game Mechanic: "Contracts need to be signed by the parties in a single session" to prevent modifying the contract after one party has signed it and before the other party has signed it. -Snipe

Potential solution: As contracts are written in ink, they cannot be modified once written on. If a person chooses to sign a blank contract or a contract with blank fields, then they accept the risk that such action entails. Fields can be permanently written on at any time. However, if either party disagrees with a field, then the contract is effectively wasted.

Benefits of this solution: PCs can pre-write contracts for their npc / opc shopkeeper. Such as:

Examples of solution:

Simple Trade Contract created by a player owner of a shop and offered by npc/opc shopkeeper:

I, Avastar, the requester, agree to give 10e to blank in exchange for 100 apples.

Request expires in 1 eyr.

1e penalty for failure.

Signed Avastar.

Signed blank

Custom Rank-E Requester Contract sold by the guild for 1e:

I, Avastar agree to give 1e to Adventurer's Guild in exchange for 10 apples upto 100 times.

I agree to pay a non-refundable 1e posting fee, minus the cost of this contract, 1e.

I agree to pay a refundable deposit of 20% of the total reward, blank. This contract is void if the calculation is not correct to the nearest 1e.

Request expires in 1 eyr.

Refundable deposit is returned for failure, minus any successful portion.

Signed Avastar

Signed blank

In the above example. Because the deposit field is left blank, the guild could cheat Avastar by putting in an incorrect amount. However, the same clause protects Avastar.

Likewise, Avastar could put in an incorrect deposit amount, however the contract would not be accepted and Avastar would need to pay another 1e to buy a new contract. Effectively, the contract is free if submitted without mistake.

The guild would permanently fill in the italics information before selling the contract.

Custom Contracts: During contract creation, the scribe could mark which fields the story engine would keep track of. Contracts could be analyzed by scribes to determine each field's (story engine) effect, to ensure they were inscribed correctly. Or, custom contracts could be excluded from the story engine.

You normally wouldn't be able to keep one party's involvement blank. In order to make this situation happen you would have to no longer be completing the templated contracts, you would just be writing on paper. In such a situation the game wouldn't treat the object as a contract, but like a book.... just words on paper without any legal binding. You might be able to convince players of the legality, but NPCs wouldn't accept it.

Since NPCs hand out contracts, can an OPC do the same? If so, then how does the PC create the 'half-signed' contract for the OPC?

Posted By Avastar at 8:09 PM - Tue Nov 26 2019

Since NPCs hand out contracts, can an OPC do the same? If so, then how does the PC create the 'half-signed' contract for the OPC?

You wouldn't be able to create a half-signed contract. You would need to be able to program the script of your OPC to sign contracts. How intricate you can make that script remains to be seen. There has been talk of some things you can do regarding scripts, but how well it recognizes whether to sign a contract or not on certain conditions... not sure.

In DJ#7 it briefly mentions OPCs with regards to contracts.... but that was with "stock contracts".

Snipe hunter commented on that earlier today. Its not an official state.

What are the game mechanic differences between an association and a guild? For the brief information I found, it seems like a neutral organization, like an adventurer's 'guild', would be better as an association than a guild.