While the trivia tid-bit is technically correct, there is no mention of such characters or relations in the game content itself. I have rephrased the information to be more relevant.
TiTs Wiki Thread
- Thread starter SeriousBlueJewel
- Start date
Hey there esteemed gamers, just the other day I was restoring my character using [ https://start-5.github.io/TiTS.JS-Save-Editor/ ] a save editor owing to my save file pulling a disappearing act then forgetting that it needs to reappear. Well it's questionable talents as a magician aside, I found a couple perks called nine-tails, enlightened nine-tails and a corrupted nine-tails in the perks section. Is this something todo with the kineticist? Figured that I should ask here.
They're remnants of Corruption of Champions, Fenoxo's previous game. There are a number of things like that.
SBJ started it, i think. i looked at previous revisions and as far as i could tell, its just cleaned up formatting internally
i believe B has made most of the Frostwyrm related documents public so they can be used to update the wiki. That being said, how should the addition of Flurry be handled in terms of page organization?
my initial thought is to change the current Frostwyrm page to a disambiguation listing both Frosty, the original frostwyrm, and Flurry, the second B recently wrote. this page could also include a brief summary and explanation of the content* and unlocking them. I am hesitant to only create pages under Frosty and Flurry as its very possible that many players aren't aware that those are the generic names the frostwyrms are referred to as.
the other option would be to have pages titled Frosty (Frostwyrm) and Flurry (Frostwyrm)
* dont know if the discourse ever reached the forums but the addition of Flurry did spark some amount of outrage in discord as many players dislike the idea of NPC's having sex with anybody but them, despite B explaining it quite well, and adding several "are you sure you want to opt in" moments
my initial thought is to change the current Frostwyrm page to a disambiguation listing both Frosty, the original frostwyrm, and Flurry, the second B recently wrote. this page could also include a brief summary and explanation of the content* and unlocking them. I am hesitant to only create pages under Frosty and Flurry as its very possible that many players aren't aware that those are the generic names the frostwyrms are referred to as.
the other option would be to have pages titled Frosty (Frostwyrm) and Flurry (Frostwyrm)
* dont know if the discourse ever reached the forums but the addition of Flurry did spark some amount of outrage in discord as many players dislike the idea of NPC's having sex with anybody but them, despite B explaining it quite well, and adding several "are you sure you want to opt in" moments
At the least, you'd want to indicate which is the one you fight. I'd guess that's what a lot of people would initially go to the Wiki for. Unfortunately, Nova and the generic Grey Goo aren't a good template for this.
The Rework Armor table contains mostly things that are actually Clothing in-game (they're flagged as Armor on the Wiki).
Is it worth moving all the armors up to the Rework or not? I'm not sure what the difference is. I'd like to clean up that page, one way or another.
The Rework Armor table contains mostly things that are actually Clothing in-game (they're flagged as Armor on the Wiki).
Is it worth moving all the armors up to the Rework or not? I'm not sure what the difference is. I'd like to clean up that page, one way or another.
my main concern is giving people a way to actually navigate to the pages. not everybody knows the frostwyrms are referred to as the names that they are.
having used the wiki for a very long time, there's a number of formatting things i'd like to unify across the board but the wiki as a whole is so behind its difficult to figure out where to start
all i noticed was backend formatting things. something to do with the method the text in the tables was being centered
I'm going one step further and saying most people are probably going to be there for Frosty first, but not know which Frostwyrm that is. If you make Frostwyrm a disambiguation page, you'll have to change all the links that actually are specifically Frosty.
Indeed.
I see it now. Weird.
mediawiki has a tool to show all the pages that link to a given page so while tedious, this won't be difficult.
i think i'll go through with making the original page a disambiguation which will include:
- an explanation that there are two frostwyrms, explaining which is which, and linking to their respective pages under Frosty and Flurry
- explaining how each frostwyrm's content is gated
B's submission doc on Flurry included an explanation on the relationship dynamics between Flurry and Frosty that I will briefly mention on this page but probably will leave the longer explanation on Flurry's page. ive also discovered that flurry's doc isn't quite as complete as I thought, but B's content thread seems to have a lot of the missing pieces. page will just take a bit longer to set up since i'll have to dig through his posts,
should the name Valrynn remain in the Frosty page as is or moved into a trivia section? imo changing mentions to Frosty will remain consistent with the name of the page
Last edited:
If B uses 'Valrynn', why are we using 'Frosty'? If we're keeping 'Frosty', it should probably be in Trivia.
I've developed the mutant power to read the Code. Accordingly, I did some work on Ancient Warbot and Shalin Shaman. Want to give them a once-over for formatting?
Should the Hyrax Bike Raider and the Glowing Hyrax Raider be separate pages? I'm thinking yes.
Frosty and Flurry are used in the majority of cases when referring to the wyrms, including the official changelogs. Valrynn and Alrythe are considered the canon names but are pretty much only mentioned where relevant (ie in the descriptions of the wyrm that use her name) or when someone specifically asks.
admittedly, i've done no phaedra content. old habits of avoiding areas that aren't mostly complete. in terms of wiki work, i'm prioritizing content that's currently outdated
i've heard of this, and i've done it a bit myself but i felt like what i was able to access was incomplete
everything seems good. i think only pages with massive amounts of content, ie anno, kiro, are major outliers in terms of format
well, since I'm making one for the Frostwyrms and we need the formatting unified, should disambiguation pages use warning banners like for gush or just a simple statement on the page
tangential, but in my experience, many other wikis have a much higher usage of aforementioned banners with warnings such as spoiler warnings, source requests and warnings about incomplete content. should we consider adding these for cases such as backer content (which could be a bit tedious to manage over time) and content based on original submission documents that still needs to be confirmed by testing or looking at code?
tangential, but in my experience, many other wikis have a much higher usage of aforementioned banners with warnings such as spoiler warnings, source requests and warnings about incomplete content. should we consider adding these for cases such as backer content (which could be a bit tedious to manage over time) and content based on original submission documents that still needs to be confirmed by testing or looking at code?
donkey recently pointed out in discord that players have no way of inspecting enemy armor flags, ie the ganrael's all have the mirrored flag. he showed the enemies that have mirrored specifically, but this does mean that all the other armor flags that apply to enemies are missing
I think most of the enemies with Armor flags are those who use defined armor. Most of them seem to use PlaceholderArmor with overridden stats.
I've been trying to get Bhakar to show up on the main page. I added some categories and he shows up under those. As far as I can tell, the main page is supposed to auto populate. But it doesn't.
I've been trying to get Bhakar to show up on the main page. I added some categories and he shows up under those. As far as I can tell, the main page is supposed to auto populate. But it doesn't.
noticed that coc2 wiki editors use their thread as a changelog so i figured i may as well do the same, since i imagine many people just aren't checking the wiki under the assumption its never being updated again. this particular list is in no particular order
From about August 2023 (Kineticist release) until September 8, 2024
- Dame Xhanni (private party event following Feruze taxi event)
- Steele Tech Probe page now has a more detailed walkthrough for Dhaal
- Carmelita - just missing scene variations and some more details on modding
- Nimue
- Dhaal afterparty documentation
- Dracow Family
- Twilit
- Anno's sex scene variations are now collapsible
- Finished Mitch's page
- Tainted Rusher
- Jasvalla's combat info
- Synth Sap
- The original Frostwyrm page is now a disambiguation. Frosty refers to the original Frostwyrm, Flurry is the second, male identifying Frostwyrm
- Identified all chameleon silk clothing
- Crew Toy interactions on the Captain Steele page
- The save editing and cheats pages now reflect the JS conversion changes
- Janeria Spawn
- Scales of Color
- Pickmentation's color table is now accurate
- Info on Sam's crew expansion
- Most of Vermillion's content
- Updated pregnancy info for Selarith, Dr. Teyaal, Amber, and Sam
- Morghenn - still missing some stuff
- Narc's quest
- Level 13 info
- Theron has been doing a bunch of things regarding items, including acquisition and mechanics
- Theron has also done most of the things regarding Kineticist and combat interactions for all classes
- Tail Me More
- Shalin Shaman
- Several other users have done haphazard edits, bust uploads, and contributions
Next on my personal to-do list:
- Train dungeon and its enemies
Last edited:
Since September 8, 2024
- Various busts have been uploaded
- The Steele Tech Probe page has a simple basic walkthrough for the main story
- Credit farming methods are updated
- Selene and Neil's combat information has been added
- Snake Shake and Snake Shake with Bobas were added
- Various other minor fixes and adjustments for clarity and/or correctness
the status effects category already has them, no? or do you mean you dont like the category where they currently exist
They're listed, but 'can inflict X status' is
1. Pretty self-explanatory.
2. There are some interesting nuances.
Like Burn/Deep Freeze/Blind bypassing the stat check on a Critical (but not Stun/Trip/Stagger).
Or the fact that Power Strike can inflict Deep Freeze on enemies it otherwise wouldn't work on.
Edit: So can Molten Shot. That's hilarious.
Maybe add references to the pages of Snake Shake and Snake Boba to their respective others to avoid possible confusion.
to be honest, i'm not quite sure what you want to do, but i don't think it'd be unreasonable to have the status effects section be simple overview that leads to a dedicated page that explains each in depth