Goonhub
04-18-2019, 08:48 AM
My idea was going to boil down to having one table at the top:
- Name
- Cost
- Availability ("All" or "Non-Nuke Ops")
(list in alphabetical order, like the PDA)
===
- Name
- Cost
- Availability (specific jobs)
(list in alphabetical order, but grouped by job)
...then a section at the bottom that actually provides the details, like
== Items for most agents ==
=== Fake Moustache ===
(image)
* Cost: 1
* Not available for nuke ops.
A fake moustache.
Only for the most moustache-twirling of evildoers.
== Job-specific Items ==
=== Moustache Grenade ===
(image)
* Cost: 1
* Available to: Staff Assistants
It's a grenade that affixes a Fake Moustache to everyone in range. Fun and twirly for the whole family!
Until you need internals.
-----------------------------------------
That way, there's a quick ref at the top for what items are usable and by who, and then a detailed list at the bottom. The table's listings would link to the item headings, of course.
- Name
- Cost
- Availability ("All" or "Non-Nuke Ops")
(list in alphabetical order, like the PDA)
===
- Name
- Cost
- Availability (specific jobs)
(list in alphabetical order, but grouped by job)
...then a section at the bottom that actually provides the details, like
== Items for most agents ==
=== Fake Moustache ===
(image)
* Cost: 1
* Not available for nuke ops.
A fake moustache.
Only for the most moustache-twirling of evildoers.
== Job-specific Items ==
=== Moustache Grenade ===
(image)
* Cost: 1
* Available to: Staff Assistants
It's a grenade that affixes a Fake Moustache to everyone in range. Fun and twirly for the whole family!
Until you need internals.
-----------------------------------------
That way, there's a quick ref at the top for what items are usable and by who, and then a detailed list at the bottom. The table's listings would link to the item headings, of course.