MediaWiki:Maintenance
 | This page is under construction over the next few days as I get a fully working suite of tools for people to use, or complete automation to handle this anyways. This page is dedicated to those who have at least read some of my ramblings int the Discord about how I do what I do. This 99% likely applies to only User:ptown2, who I wish has the time and energy to maintain the wiki in the event of an absence on my end. |
Due to how the wiki now functions, it's fairly esoteric for anyone else to keep it up to date when it comes to unit information (complete card and skill data). Because of this, I should at least leave a "guide" on how to keep things up to date in the event I can't. First and foremost, Websamo is configured in a way that it can both depend on the real Housamo app for data and separate itself from it in the event it needs to. Almost all of the following revolves around endpoints that lets Websamo function (a good rule of thumb is if you need something else, consult Websamo's inner client workings).
Card data
- In the Discord's #wiki-discussion channel, the dog bot will announce data updates it detects. These happen either every new Japanese day (when the dailies change over), or whenever a change is detected through playing Websamo (simply opening the page will start the check).
- When the bot detects a change, an embed will be posted in #wiki-discussion. The title of the embed has a link to a bot endpoint to list what changes were made on the surface. Look for changes in the Card table (for example: table_name: Card, path:/NUMBER; entries with path:/ are blanket table updates and are kind of a problem to deal with.
- From here, you can throw in any new card IDs into https://app.housamo.xyz/card/CARDID/ to see who that ID corresponds to. There's other ways to do it, but validating a card ID is the easiest this way.
- Another way to obtain card IDs is through https://app.housamo.xyz/card/ itself, selecting a card, then pasting `gstate.scene.metadata.id` into your browser's console. The value returned is the card you're currently viewing's ID.
- After validating who the ID belongs to, consult Template:Transient extended infobox for how to set up a Transient page, and let the wiki handle the rest.
- Repeat for a unit's additional cards (for example, higher rarities).
An additional way is to sift through the tables given through Websamo. For data updates whose paths are "/", you can view the entire table through https://api.housamo.xyz/housamo/elb/transcription/?action=datas/get&path=TABLE./.
A way to completely forego using ID is to consult Template:Transient infobox. In short, simply providing the Japanese title should allow the wiki to query the bot to resolve the Japanese title to card data, as 99% of the time a Japanese title is unique to a card.
Quest (information) data
Use the above method, but pay attention to the Quest tables.
Skill and Status data
Again, consult the above.
Substitute the infobox template with Skill and Status, respectively. Substitute Japanese title with Japanese name.
Quest (battle) data
Sadly, detailed quest information (enemy and drop distributions) are currently only a me-thing; that is, my patched version of Housamo allows retrieving and parsing data sent to and from the app). Refer to the end on if this will ever be accessible to you.
Asset data
Assets such as sprites and voices require an additional bot endpoint to retrieve and parse. This can be manually invoked through https://api.housamo.xyz/housamo/api/assets/update/. This is called by the bot every new Japanese day and will make its rounds of retrieving and parsing assets. Avoid using this endpoint unless it's required.
Scenario data
Luckily, obtaining the scenario datas use the same means of obtaining and parsing as assets, but without the extra step of extracting. This can easily be be done manually, as a simple GET request to specific resources is just enough to get changes to propagate outward to the VN portion of Websamo. This will fall under the above method.
Cached wiki data
To ensure the wiki isn't completely dependent on the bot for resolving data IDs into wikitext, the wiki extension handling Housamo data caches responses from the bot. These cached responses have a TTL of one hour (I think). In other words, the wiki pages using this format is at most an hour out of date (ignoring other caches). I do not have an easy way to purge the extension's cache outside of manually `rm`ing it. I don't think I'll have a publicly accessible way of purging this cache due to the way it can easily be abused to place strain on the wiki. If this issue ever gets ran into, just wait an hour.
Notes
As a foreward on why this page exists, I feel it's required due to my growing apathy towards Housamo in the event something does happen. I assure you the wiki will remain in the event that something does happen, and when it does, I'll be sure to let the masses know, even though I'm 95% confident it'll die with me because no one else has the will or want to bear the burdens.
In the event I feel it's necessary to release details on how to do what I do, I'll have said details on /sysdoc/. Currently /sysdoc/ is hidden from the public.
As a message to LW or its affiliates: in the event of my complete absence, if you do feel my work is a detriment to Housamo, by all means feel free to prevent it; there's plenty of ways to do it, I'm sure you can find one that will break my work.
1 comment
[Show Comments]
The stories and information posted here are artistic works of fiction and falsehood. Only a fool would take anything posted here as fact.
Enable comment auto-refresher
Permalink |