Polavux
Joined 4 June 2024
mNo edit summary |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
Current projects: | Current projects: | ||
*Updating/adding stats | *Updating/adding stats | ||
*Finishing the rest of the cosmetics for | *Finishing the rest of the cosmetics for BTDB2 | ||
Fun facts about myself (one of these is false): | Fun facts about myself (one of these is false): | ||
| Line 15: | Line 15: | ||
*My wiki account password is <tt>planterrorsucks</tt> | *My wiki account password is <tt>planterrorsucks</tt> | ||
==Trying to figure out how to properly cover development information, prerelease information, and anything else behind-the-scenes-related== | |||
Currently we don't have pages for the launch versions of games (there's no BTD6 version 1.3 page, for example). This is because they wouldn't really serve a purpose. There's no changes to document, the release date information would be identical to what's in the infobox on the game's page, and there's no patch notes to quote from or link to. All you'd have is a list of content that was in the game at launch, which you could just make into a list page. | |||
We do have pages for [[Bloons Card Storm Firstlook test]] and [[Bloons Card Storm Full Playable test]], and there will be more pages on prototypes to cover in the future, like the leaked TestFlight builds of BTD5. There's also the matter of updates that have development builds, like that leaked build of BTD6 version 6.0 with different SciGwen voice lines and a different layout for Quad. Since these aren't really "updates", it doesn't make sense to cover them in the update namespace. | |||
*Create a new namespace for covering prototypes and other things of that nature | |||
*Pages on prototypes cover their differences from the following version, essentially the opposite of update pages (for example, the firstlook test page focuses on the differences from the full playable test, the full playable test focuses on the differences from build 1050, and the build 1050 page focuses on differences from the final) | |||
Other things that could be covered on this namespace: | |||
*Content that was introduced in an unused/unfinished state, and was made available later on, but with many differences (like the Dartling Gunner and Beast Handler's original upgrades, or the early version of Rogue Legends in 46.0) | |||
*Leaked asset bundles from development builds | |||
*Listing differences in early trailers and screenshots (of development builds that never made their way to the public) | |||
*Featured that were mentioned or planned, but never implemented | |||
*Development timelines of the game and individual features if applicable | |||
Things I'm not sure how to handle: | |||
*I'm not sure if these should include unused content, even if unused content can include things like debugging tools, which are development-related. . Unused content still exists within the game, just not in an accessible state, unlike the other development-related stuff that is outside the game itself. Also, content that was in the game and later removed, but still remains in the game files, is also unused content, but I wouldn't call that development-related per se. Note that prototypes can also have unused content of their own, and content that was unused then but became used in later versions. | |||
*I'm not sure how this would affect "pre-release" sections that focus more on things like early access videos and promotional material. I feel like that stuff should be separate since it isn't very development-related, but sometimes that stuff has development-related info worth covering (like the early version of [[Three Mines 'Round]]). | |||
Another idea I had was to structure "development" sections on pages to be more like update histories. For [[Robo Monkey (BCS)#Development]] for example, that would mean splitting it into subsections, one for the robo monkey in the beta tests, one for the changes at launch (which made it no longer functional), one for the changes in 4.0, one for the changes in 4.4, one for the differences when it released in 5.0, and one for the 5.2 playtest notes. This would also be where we list changes to cards in the closed beta. | |||
One question I have is if builds from soft-launch phases should count as prototypes. Right now Bloons Blitz is unfinished and hasn't rolled out globally yet. However, it is a commercial product and is expected to get consistent updates. This is different from BCS's closed betas because only people who registered could play them, they weren't commercial products, and there weren't many updates. | |||
As for the name of this namespace, I have some ideas: | |||
*"Development": Straightforward, though maybe a little overly broad. Personally, I think it's awkward to use this term to describe things like playtester feedback, but maybe it'll work. NK uses terms like "developer diary" for updates, after all. | |||
*"Behind the scenes": Too flowery in my opinion, but maybe it's more intuitive? Combine Overwiki uses this. | |||
==Work to be done== | ==Work to be done== | ||
* | *finish redoing the BTD6 stats system, and use it as the basis for other games | ||
*Finish all the policy and guideline pages | *Finish all the policy and guideline pages | ||
**Write guidelines for galleries, update pages, and citations | **Write guidelines for galleries, update pages, and citations | ||
| Line 27: | Line 52: | ||
*Fix all incorrect uses of minus signs and en dashes currently on the wiki (minus signs are supposed to be used for subtractions or negatives, like -40%, while en dashes are supposed to be used for ranges, like 5–10) | *Fix all incorrect uses of minus signs and en dashes currently on the wiki (minus signs are supposed to be used for subtractions or negatives, like -40%, while en dashes are supposed to be used for ranges, like 5–10) | ||
*Missing BTDB2 cosmetics | *Missing BTDB2 cosmetics | ||
*Documenting the unused "Scoops Tale II" quest, now that it's been in the game files for over a year | |||
*bear5 | *bear5 | ||
| Line 105: | Line 131: | ||
*I just really like the idea of a support tower that focuses specifically on keeping bloons clumped up and moving them to places where aoe towers can maximize their damage, even more than glue and bottom path merm | *I just really like the idea of a support tower that focuses specifically on keeping bloons clumped up and moving them to places where aoe towers can maximize their damage, even more than glue and bottom path merm | ||
== | ==Unidentified and disputed Bloons== | ||
this is a random idea i had, i might add this to the [[Bloon]] page at some point | |||
this is a random idea i had, | |||
*The ghost bloons on [[Haunted Swamp]] | *The ghost bloons on [[Haunted Swamp]] | ||
| Line 116: | Line 139: | ||
*The blimp in [[Hot Air Bloon]] | *The blimp in [[Hot Air Bloon]] | ||
*The "Energy Bloons" that make up the boss arenas in [[Bloons Blitz]] | *The "Energy Bloons" that make up the boss arenas in [[Bloons Blitz]] | ||
==app ids== | ==app ids== | ||
| Line 175: | Line 159: | ||
| | | | ||
|- | |- | ||
|rowspan= | |rowspan=4|2 | ||
|rowspan= | |rowspan=4|[[Bloons TD Battles (multiplatform)]] | ||
|4 | |4 | ||
| | | | ||
| Line 184: | Line 168: | ||
|- | |- | ||
|6 | |6 | ||
| | |||
|- | |||
|10 | |||
| | | | ||
|- | |- | ||
|rowspan=3|3 | |rowspan=3|3 | ||
|rowspan=3|SAS: Zombie Assault 4 ( | |rowspan=3|SAS: Zombie Assault 4 (multiplatform) | ||
|7 | |7 | ||
| | | | ||
| Line 232: | Line 219: | ||
|- | |- | ||
|rowspan=3|9 | |rowspan=3|9 | ||
|rowspan=3|[[Bloons TD 5 | |rowspan=3|[[Bloons TD 5 (multiplatform)]] | ||
|24 | |24 | ||
| | | | ||
| Line 307: | Line 294: | ||
|- | |- | ||
|12 | |12 | ||
| | |??? | ||
| | | | ||
| | | | ||
|- | |- | ||
|13 | |13 | ||
| | |??? | ||
| | | | ||
| | | | ||
| Line 331: | Line 318: | ||
|- | |- | ||
|15 | |15 | ||
| | |??? | ||
| | | | ||
| | | | ||
| Line 417: | Line 404: | ||
|- | |- | ||
|22 | |22 | ||
| | |??? | ||
| | | | ||
| | | | ||