Editing Talk:Broken Cooking God

Jump to navigation Jump to search
You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 48: Line 48:
:The problem is that the Divine Cooking Tool (EU and JP) is already an alternate version of the Broken Food Master (US). In fact, they are the very same object, whereas the Broken Cooking God is a unique object in the series. &mdash; '''{''[[User:Espyo|Espyo]]''<sup>[[User talk:Espyo|T]]</sup>}''' 10:39, April 9, 2022 (EDT)
:The problem is that the Divine Cooking Tool (EU and JP) is already an alternate version of the Broken Food Master (US). In fact, they are the very same object, whereas the Broken Cooking God is a unique object in the series. &mdash; '''{''[[User:Espyo|Espyo]]''<sup>[[User talk:Espyo|T]]</sup>}''' 10:39, April 9, 2022 (EDT)
:I disagree, in fact, I think the Divine Cooking Tool should be merged with the Broken Food Master instead. The Broken Cooking God has a different model and name, meanwhile the Divine Cooking Tool, while found in a slightly different location, is basically a renamed Broken Food Master. Also, while merging the Divine Cooking Tool would be easy, the Broken Cooking God would be a lot more difficult due to having different model, icon and values. &mdash; [[User:GGabryy|'''GGabryy''']]<sub>[[User talk:GGabryy|''(talk)'']]</sub> 14:08, March 7, 2024 (CET)
:I disagree, in fact, I think the Divine Cooking Tool should be merged with the Broken Food Master instead. The Broken Cooking God has a different model and name, meanwhile the Divine Cooking Tool, while found in a slightly different location, is basically a renamed Broken Food Master. Also, while merging the Divine Cooking Tool would be easy, the Broken Cooking God would be a lot more difficult due to having different model, icon and values. &mdash; [[User:GGabryy|'''GGabryy''']]<sub>[[User talk:GGabryy|''(talk)'']]</sub> 14:08, March 7, 2024 (CET)
::I disagree with that argument. After all, the US version of the [[Endless Repository]] has the same "model, icon and values" as the [[Perfect Container]], but that doesn't mean the US info on the former should be moved to the latter's article, does it? [[User:2 B|2 B]] ([[User talk:2 B|talk]]) 16:43, March 8, 2024 (EST)
:::I think that the Endless Repository and Perfect Container should be different pages, but that's more due to the fact that Endless Repository is used to refer to two different treasures, so if you were to merge the information about the US version in the Perfect Container, the page would still exist and so it makes more sense for that info to be there. Even if you don't want to merge Broken Food Master and Divine Cooking Tool, I still don't think the Broken Cooking God should be merged. Aside from its location, it has a different name, model and notes from the Broken Food Master. &mdash; [[User:GGabryy|'''GGabryy''']]<sub>[[User talk:GGabryy|''(talk)'']]</sub> 23:08, March 8, 2024 (CET)
::::Different name and notes? Not really. The so-called Broken Cooking God only appears in the original Japanese version, where it has the exact same notes that the Broken Food Master has in the Japanese version of the Switch port. The former has no English notes to compare, so the only name/notes we have are the same. [[User:2 B|2 B]] ([[User talk:2 B|talk]]) 17:44, March 8, 2024 (EST)
:[[User:PopitTart|PopitTart]] made a good diagram in the Discord to explain the situation, which I'll now try to recreate here in a table:
{| style="text-align:center"
| [[File:BrokenCookingGod.png|100px]] <br> 折れた食神 <br> (Broken Cooking God) (JP)
| –
| Name <br> Notes <br> Location
| –
| [[File:Thumb brokenfoodmaster.jpg|100px]] <br> Broken Food Master (NA)
|-
| || || || / || <nowiki>|</nowiki>
|-
|
|
| Appearance <br> Weight <br> Value <br> Series
|
| Appearance <br> Weight <br> Value <br> Series
|-
| || / || || || <nowiki>|</nowiki>
|-
| [[File:Thumb brokenfoodmaster.jpg|100px]] <br> 自炊の神器 <br> (Divine Self-Catering Tool) (JP)
| –
| Appearance <br> Weight <br> Value <br> Series <br> Name <br> Notes <br> Location
| –
| [[File:Thumb brokenfoodmaster.jpg|100px]] <br> Divine Cooking Tool (EU)
|}
: I think the most logical way to resolve this complex situation would be to split the table vertically, prioritizing the similarity in name and notes over the similarity in appearance. &mdash; [[User:Soprano|'''Soprano''']]<sub>[[User talk:Soprano|''(talk)'']]</sub> 19:07, March 8, 2024 (EST)
::Makes sense. By the way, the following US-or-UK treasures have the same Japanese name in the Switch port as the following Japanese treasures and I think should definitely be merged (I added merge templates to them a while back):
::*[[Broken Cooking God]] to [[Broken Food Master]]
::*[[Lightning Bolt]] to [[Impediment Scourge]]
::*[[Love and Courage Reactor]] to [[Courage Reactor]]
::*[[Omegatron]] to [[Durable Energy Cell]]
::*[[Proton X]] to [[Proton AA]]
::*[[Universally Best Art]] to [[Abstract Masterpiece]]
::*[[Yell Battery]] to [[Fuel Reservoir]]
::While the following have very names and notes that are remarkably similar, but not identical:
::*[[Milk Lid]] and [[Massive Lid]]
::*[[Idea Assistant]] and [[Creative Inspiration]]
::*[[Understood Person Symbol]] and [[Optical Illustration]]
::*[[Seat of Enlightenment]] and [[Pondering Emblem]]
::What do you think should be done with these last ones? Keep them split like with the the Munge/Venom Dweevil situation?
::[[User:2 B|2 B]] ([[User talk:2 B|talk]]) 09:23, March 9, 2024 (EST)

Please note that all contributions to Pikipedia are considered to be released under the Attribution-ShareAlike 4.0 International license (see Pikipedia:Copyrights for details). Your changes will be visible immediately. Please enter a summary of your changes above.

Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)

Template used on this page: