The Wandering Inn Wiki:Class Overhaul

From The Wandering Inn Wiki

This is a draft! Let's discuss!

Info we have from the List of Classes/A pages

  • Name
  • Characters who have/had that class
  • Class Type deemed not needed)
  • Class Requirements (1-n classes)
  • Specialization
  • Chapters the class was mentionned in (1-n chapters)

From that information, can we create a Class Page template?

Let's take Alchemist as an example for class:

I'd see something like this on a page. 

= Alchemist =

(Sections or Infobox with class type + requirements + specialization?)

(description)

== Requirements ==

* (link to another class) 

== Specializations ==

* List of classes derivating from that class (using Cargo/our classes database))

== References ==

(chapter list)

== Characters ==

* Use CategoryTree to display characters of that class inside the page itself(by adding a "s" to the category name)
* For unique classes we can just name the character who has it.


How to proceed[edit | edit source]

  1. Make a good template for a page
  2. Make a google doc with the List of Classes/A and so on pages.
  3. Manually review the document
    • Verify Class names
    • Add characters that should belong to the class
    • Add a column with "base classes" which should point to the base class this class is from. Magical Innkeeper should ahve Innkeeper in there. If it's a consolidation, it should have several names separated by a | (pipe)

Once the document is completed, a script can be written by leveraging the mediawiki API and do the following for us :

  • Create a page per class with the aforementionned template
  • Add a link to this page somewhere on each character mentionned (or make sure it exists.)

Other things you'd like it to do ?

Retrieved from "https://wiki.wanderinginn.com/index.php?title=The_Wandering_Inn_Wiki:Class_Overhaul&oldid=93653"
Add comment
AxelTerizaki
Template
Axel Terizaki | Posted on Feb 26, 2024 at 12:56 pm

So who's good with making templates that we could use to automatically create the pages via a script?

Or should we wait for Torenity's tests with Cargo/SMW?

Reply
Torenity
My thoughts
Torenity | Posted on Feb 20, 2024 at 1:35 am | Last edited on Feb 20, 2024 at 6:37 am

My understanding from reading the post is each generic base class would get their own page. It sounds like this is to prevent bloat of overly special classes having their own page, and their data should be under their base class' page instead.
Just a note that doing it the above way, may make it difficult for readers to search for those specialized classes by typing in the search bar (assuming specialized classes are not having their own page).

I'm for each class having their own page (even the specialized classes, if only to store their relevant consolidations/advancement/character info).

As an aside, I just want to note that Innworld's class system seems to be very organic. I.e. there aren't hard-and-set rules on how someone receives a class, which class advances into which, or whether a class is a base class or not (i.e. [Alchemist] may have a class that advances into it someday, like if a character were to go from [Mixer] -> [Alchemist] because the System or Pirateaba felt it appropriate for the story. The wiki's Class overhaul should be flexible to things like that. That wasn't a comment on Axel's post, just something I want us to keep in mind when going forward with this.

My thoughts on the data mentioned in Axel's post.

  • Class Type -- I don't see a way for us to classify this kind of data. Are Class Types a fanon idea or canon to the Innverse?
  • Class Requirements -- Is this for classes required to obtain this class? Maybe we can call these Preceding Class(es). "Base Class(es)"? or "Known Base Classes". "Class Requirements" seem to imply this is a rigid class requirement to obtain the next class, when the System/Pirateaba could just give the class to a character
    • Can be None for cases like [Alchemist], up until pirateaba reveals that another class can advance into [Alchemist], which we can update.
  • Specializations -- Nothing to say on this, seems straight forward.
    • i.e. [Silversteel Armsmistress] is a known derivative class of [Wounded Warrior]. Chapter and character should be noted.
    • [Conditions Met: Wounded Warrior → Silversteel Armsmistress Class!]
  • Chapters the class was mentioned in -- I think that's useful! But may be a LOT to keep track of, if we need to update each class for every chapter that comes out. Pallandor's tool would make manual verification of each mention faster at least. Or we can link to a service like Pallandor's who's already done this sort of querying on the TWI chapters. I'm unsure of a good way for wiki editors to input class chapter mentions without asking too much of them at the same time.
    • Adding a "Classes" field in each Chapter page, much like "Characters" and "Locations" we already have in each Chapter. Editors add the class mention, it gets pushed to the Class's chapter mentions page. Should be possible with Cargo or Semantic MediaWiki. Do we want to ask editors to note that kind of granular data though?
    • A MediaWiki API bot to update this field is another idea, if we really want that data stored on the wiki's own db.


I'm proposing a separate section to show all the Class Consolidations we've found throughout the series:

  • Class Consolidations: a list for known consolidations this particular class is involved in. where multiple classes are removed and then one new class is added, as we discover them
    • Type 1 Consolidation: The class is removed to advance to a different class. Chapter and character.
    • Type 2 Consolidation: The class is added as a result of removing other classes. Chapter and character.


To summarize my ideas above, each Class's page looks like this, in my mind:
Base Class(es) <--This Class's page --> Specializations/derivative Classes(es) Character and Chapter Reference for each class advancement event
List of known consolidations
Chapters the class was mentioned
References


AxelTerizaki
Axel Terizaki | Posted on Feb 20, 2024 at 10:55 am

First of all I totally agree on the point about not making life of editors harder. That's a **requirement** for this new overhaul to work. And I can't emphasize **requirement** enough. There's no point if it's not easy enough.

Second, something good about TWI is that classes don't change overnight : once it's written, it shouldn't change. So it make take some time to set up but adding a new class shouldn't be that difficult. We need to aim for that. The how depends on what SMW/Cargo can offer us

Now about your other points :

  • About class spec/reqs : I agree this is more organic than systemic so establishing a full diagram of classes is going to be impossible. There are however some classes where we're pretty sure they have requirements or specializations and they should be noted (Necromancer -> Deathbane Necromancer and so on).
  • No class type then, fine with me (I was thinking something simple like Combat/Non-combat classes but that's not very helpful, in hindsight)
  • Consolidations : they're pretty organic but then again we would need some kind of relational database for that to work out right. Then again like I mentionned earlier, once the information is there, it should not be updated any time soon.
  • For chapters : we need to decide if we want that in the wiki or if we want to rely on pallandor's tool and link users there. Maybe pallandor can make it automatic like, you link a chapter there (https://site/chapter/6.65) and it displays all classes there, and doing the reverse with classes. Then again we need to see if SMW/Cargo allows us to pull data from an API when you edit/create a page so it automatically generates wikicode that links the chapters correctly.

So if SMW/Cargo can pull info from an API upon editing/creating a page, we could use pallandor's tool to fill the information for us instead of linking to it.

Reply
Last modified
This page was last edited on 26 February 2024, at 11:56.
Copyright
Content is available under Creative Commons attribution – non commercial – share alike unless otherwise noted.
collapse
permalink
permalink
collapse
permalink