2024.05.19 04:35 Kevbone28 Not a bad record
Since my last leaderboard standings screenshot on 4/11/24, I’ve gone 106-9-13 submitted by Kevbone28 to pga2k21 [link] [comments] Beast mode!!!!! |
2024.05.19 03:43 The_Entheogenist Strasbourg WTA 500 Draw - Vondrousova, BHM, Collins, Keys, Navarro
submitted by The_Entheogenist to tennis [link] [comments] |
2024.05.19 01:18 bamzing Thursday Modern Challenges Results - May 16 2024
65 | Thursday Modern Challenge 1 (May 16 2024) | ||||
---|---|---|---|---|---|
1. | BR Grief | (8-2) Tubaba | |||
2. | Amulet Titan | (7-3) kanister | @kanister_mtg | [Twitch] | [YouTube] |
3. | Amulet Titan | (7-2) DrakeHaven | |||
4. | BG Yawgmoth | (6-3) Graciasportanto | @MauroSasso2 | ||
5. | 4c Living End | (6-2) manohito | |||
6. | BR Grief | (6-2) sokos13 | @sokos13_ | ||
7. | Temur Prowess [Jegantha] | (6-2) _Falcon_ | |||
8. | Hardened Scales | (5-3) LordEgg | |||
9. | BR Grief | (5-2) Martin_Dominguez | @RuloMTG | ||
10. | UR Murktide | (5-2) Alico | |||
11. | BG Yawgmoth | (5-2) lunaloveee | |||
12. | GW Emeria Control | (5-2) levunga21 | @levunga | ||
13. | 4c Goryo's Vengeance | (5-2) twister66 | |||
14. | BG Yawgmoth | (5-2) ARCll | |||
15. | RW Burn | (5-2) rastaf | @MtgRastaf | [Twitch] | |
16. | 4c Living End | (4-3) LucasG1ggs | @GiggsMtg | ||
17. | Jeskai Urza | (4-3) gyyby297 | @gyyby_mtg297 | ||
18. | UB Mill | (4-3) GingerGuy83 | |||
19. | 4c Omnath | (4-3) TrueHero | @IsThatTrueHero | ||
20. | Temur Prowess [Jegantha] | (4-3) Alan07 | @AlanLB07 | ||
21. | BR Grief | (4-3) _Batutinha_ | @_Batutinha_ | [Twitch] | |
22. | UR Murktide | (4-3) O_danielakos | |||
23. | UR Murktide | (4-3) Shiny_Beest | |||
24. | RW Burn | (4-3) rasvd | |||
25. | Domain Zoo [Jegantha] | (4-3) milikin | |||
26. | RG Crimes [Jegantha] | (3-3) grinderA | |||
27. | Mono B Rack | (4-3) medvedev | @m3dvedev | ||
28. | Mono W Hammer | (4-3) Akeel | |||
29. | 4c Living End | (3-4) MeninoNey | @MeninooNey | ||
30. | Amulet Titan | (3-4) Jumba | |||
31. | BR Grief | (2-3) KatieKat | |||
32. | BR Grief | (3-4) Capitano_CL | |||
33. | 4c Living End | (3-4) drVendigo | |||
34. | RW Midrange | (3-4) DragonFodder | @BrindRobert | ||
35. | 4c Omnath | (3-4) alemilan19 | @alemilan_19 | ||
36. | 4c Living End | (3-4) Linden_43 | |||
37. | Mono W Hammer | (3-4) CARLONEE | |||
38. | BR Grief | (2-4) JFoster | |||
39. | Mono B Rack | (3-4) Selfeisek | |||
40. | Jund Crimes [Jegantha] | (2-4) stefanocanclini | |||
41. | Mono B Rack | (2-3) Makitren | |||
42. | 4c Goryo's Vengeance | (2-3) 2radMTG | |||
43. | Affinity | (2-4) Dreddybajs | @PocketJacesCast | [Twitch] | [YouTube] |
44. | Domain Zoo [Jegantha] | (2-3) pepeteam | |||
45. | RG Tron | (2-4) AlpInco | @Alp_MTG | [Twitch] | [YouTube] |
46. | RW Burn | (2-5) FranMtg | |||
47. | 4c Living End | (2-4) Sven745 | |||
48. | Bant Living End | (2-5) DevinShave | @Opt_gg | [Twitch] | |
49. | 61-cards Mono G Stompy | (2-4) p00pInMyFacex3 | |||
50. | Jund Grief | (1-3) jeunejulio | |||
51. | 4c Omnath [Kaheera] | (1-2) McWinSauce | @McWinSauce | ||
52. | BG Asmo | (1-3) Trollolas | |||
53. | Domain Zoo [Jegantha] | (1-3) Venom1 | @OowashiAkatsuki | ||
54. | Esper Soulherder | (1-5) ChuckNoris43 | |||
55. | 4c Rhinos | (1-2) Hatsunelol | |||
56. | Glimpse | (0-3) Laranjinha-BR | |||
57. | 4c Living End | (0-2) magaramagara | |||
58. | Temur Prowess [Jegantha] | (0-2) k00p4 | |||
59. | Jund Creativity | (0-2) avb | |||
60. | Grixis Shadow | (0-2) Gernardi | |||
61. | 61-cards Amulet Titan | (0-2) Mistakenn | @Mistakenn1 | [Twitch] | |
62. | 4c Goryo's Vengeance | (0-2) ScoopDog | |||
63. | RG Crimes [Jegantha] | (0-2) hugtheaquilifer | |||
64. | Temur Prowess [Jegantha] | (0-1) Ale_Mtg | @Ale_mora_02 | ||
65. | BR Grief | (0-4) _ruda_ | |||
Amulet Titan | gurig | @TaintedOpt | |||
BG Coffers [Umori] | Walri | ||||
4c Living End | death_grips |
50 | Thursday Modern Challenge 2 (May 16 2024) | ||||
---|---|---|---|---|---|
1. | Amulet Titan | (7-2) Filho_do_MOL | |||
2. | RW Burn | (7-2) absoluteragez | |||
3. | BG Yawgmoth | (6-2) Nammersquats | @Nammersquats | [Twitch] | |
4. | Temur Prowess [Jegantha] | (5-3) AnothaPlaya | |||
5. | Amulet Titan | (6-1) HouseOfManaMTG | @HouseOfManaMTG | [Twitch] | [YouTube] |
6. | RW Burn | (5-2) izzy-wilde | |||
7. | RW Prowess | (5-2) Bosseidon | @BosseidonRed | [Twitch] | [YouTube] |
8. | Affinity [Jegantha] | (5-2) jfariv | |||
9. | Grixis Grief | (4-2) SinKarma | |||
10. | BR Grief | (4-2) Capitano_CL | |||
11. | Temur Prowess [Jegantha] | (4-2) mtgobazaar8 | |||
12. | Temur Prowess [Jegantha] | (4-2) Alan07 | @AlanLB07 | ||
13. | Temur Prowess [Jegantha] | (4-2) k00p4 | |||
14. | Domain Zoo [Jegantha] | (4-2) The_Kingpin | |||
15. | Amulet Titan | (4-2) Jumba | |||
16. | Domain Zoo [Jegantha] | (4-2) jcubby02100 | |||
17. | 4c Omnath [Kaheera] | (3-3) Viatt | |||
18. | BR Grief | (3-3) AmadeusPro | |||
19. | 61-cards Amulet Titan | (3-3) _EzMud1 | |||
20. | BR Grief | (3-3) jben | |||
21. | Amulet Titan | (3-3) Ivan_Draw_Go | @Ivan_Draw_Go | [Twitch] | |
22. | Abzan Amalia | (3-3) xerioc | |||
23. | Affinity | (3-3) TheNectar | |||
24. | BG Yawgmoth | (3-3) SleepingSnorunt | |||
25. | Amulet Titan | (3-3) gurig | @TaintedOpt | ||
26. | 4c Living End | (3-3) death_grips | |||
27. | UW Control [Kaheera] | (3-3) nahuel10 | @Nahuel10Mtg | ||
28. | UR Control | (3-3) Joryago | |||
29. | BR Grief | (3-3) No_e_that_knows | @Noe_leal_jr | ||
30. | BG Yawgmoth | (3-3) Zorro7x4 | |||
31. | BG Coffers [Jegantha] | (2-3) selesneal | @selesneal | ||
32. | Domain Zoo [Jegantha] | (1-4) _and_one_ | |||
33. | UW Control [Kaheera] | (2-4) bless_von | |||
34. | BR Grief | (2-4) jvidarte | |||
35. | UR Murktide | (1-4) Toki_85 | |||
36. | UW Control [Kaheera] | (2-4) vSUPREME973 | |||
37. | 4c Living End | (1-4) Oppa | |||
38. | RW Burn | (1-4) _BOI_ | |||
39. | 61-cards RG Ponza | (1-3) OrnatePuzzles | @Jaawls | ||
40. | Temur Prowess [Jegantha] | (1-3) jessy_samek | @Jessy_samek | ||
41. | Esper Control [Kaheera] | (1-3) 2805667 | |||
42. | RW Burn | (0-2) Cachorrowo | |||
43. | BR Grief | (0-3) DannyStarchild | |||
44. | BG Yawgmoth | (0-2) TheMeatMan | @MeatMTG | [Twitch] | [YouTube] |
45. | BR Grief | (0-3) f1shmagic | |||
46. | RG Crimes [Jegantha] | (0-2) bunnyfat | |||
47. | UG Infect | (0-2) ItsMattox | |||
48. | UR Breach | (0-2) YungDingo | @YungDingoMTG | [Twitch] | [YouTube] |
49. | Bant Living End | (0-2) WingedHussar | @WingedHussarMTG | [Twitch] | |
50. | Dice Factory | (0-3) Spy_1 |
9 Bx Grief (8 BR, 1 Jund) 8 Living End (7 4c, 1 Bant) 4 Amulet Titan 4 Temur Prowess 3 BG Yawgmoth 3 UR Murktide 3 4c Goryo's Vengeance 3 RW Burn 3 4c Omnath 3 Domain Zoo 3 Crimes (2 RG, 1 Jund) 3 Mono B Rack 2 Mono W Hammer 1 Hardened Scales 1 GW Emeria Control 1 Jeskai Urza 1 UB Mill 1 RW Midrange 1 Affinity 1 RG Tron 1 Mono G Stompy 1 BG Asmo 1 Esper Soulherder 1 4c Rhinos 1 Glimpse 1 Jund Creativity 1 Grixis Shadow
8 Bx Grief (7 BR, 1 Grixis) 6 Amulet Titan 6 Rx Prowess (5 Temur, 1 RW) 4 RW Burn 4 BG Yawgmoth 4 UWx Control (3 UW, 1 Esper) 3 Domain Zoo 3 Living End (2 4c, 1 Bant) 2 Affinity 1 4c Omnath 1 Abzan Amalia 1 UR Control 1 BG Coffers 1 UR Murktide 1 RG Ponza 1 RG Crimes 1 UG Infect 1 UR Breach 1 Dice Factory
3 Bx Grief (3 BR) 3 BG Yawgmoth 2 Amulet Titan 1 Living End (1 4c) 1 Temur Prowess 1 UR Murktide 1 4c Goryo's Vengeance 1 RW Burn 1 Hardened Scales 1 GW Emeria Control
5 Rx Prowess (4 Temur, 1 RW) 3 Amulet Titan 2 Bx Grief (1 Grixis, 1 BR) 2 RW Burn 2 Domain Zoo 1 BG Yawgmoth 1 Affinity
Caustic Bronco Roxanne, Starfall Savant Slickshot Show-Off Lavaspur Boots Honest Rutstein Magda, the Hoardmaster Freestrider Lookout Requisition Raid Satoru, the Infiltrator Assimilation Aegis Pillage the Bog Three Steps Ahead Fomori Vault Pest Control Simulacrum Synthesizer Lost Jitte
2024.05.19 00:29 Bazil2009 The Battle of Big Reel 💥💥💥 #StarlightDriveIn (No Mods)
(1/12) The Battle of Big Reel occurred on November 27th, 2295, during the Nuka War. After the fall of the institute in 2289, a new threat came to the Commonwealth: the Nuka-World Raider Gangs. On October 12, 2293, the Sunshine Massacre would occur after the Nuka-World Raider Gangs invaded the Minutemen Settlement, outnumbering its residents ten to one. The next morning, a group of Minutemen and a small militia from nearby settlements would arrive, only to meet the same fate as the Sunshine settlers. Mason would then send a small force of raiders to Diamomd City to deliver a declaration of war on the Commonwealth. submitted by Bazil2009 to fo4 [link] [comments] (2/12) After news spread on Diamond City radio, things escalated when the Rust Devils approached the Nuka-World Raiders Gangs for the first time and formed an alliance. (3/12) Eventually, the Raiders would push north for Abernathy to gain control of the settlement artillery. This led to the Battle of Farm Hill, which was the first major battle of the war. The Minutemen and the BOS both suffered major losses, and Abernathy fell on January 6, 2294. Much of the Raiders' success during the Battle of Farm Hill is due to their invention of mobile anti-aircraft missile turrets that practically annihilated the BOS's Vertibird Fleet. This made defeating the outnumbered Minutemen's ground troops a cakewalk. (4/12) Much of the war was then focused around Red Rocket and the City of Sanctuary. Many feared an artillery attack was coming at any given moment. A large army consisting of BOS, Minutement, and local militias was formed to prepare to defend the city from an invasion. Instead, the Raiders continued to surround Red Rocket and the City of Sanctuary, leaving a small route to the east going to Ten Pines as the only way in or out. This left most of the other settlements in the area to fend for themselves. Most settlements quickly realized this and started making preparations. (5/12) In larger settlements like Big Reel, everyone came together to fortify the city. Many believed that if the City of Sanctuary fell, Big Reel would be the next target. A patchwork army quickly formed, consisting of City Police, Minutemen, BOS, Merian Casino Security Robots, Undercover Railroad, Settlers, Synths, and Ghouls. (6/12) Big Reel's weak spot is the hill next to the city's north wall. However, if the Raiders are spotted to the south, the Church of Atom will ring its bell to alert the patchwork army to move south. (7/12) On November 27th, 2295, at 8:06 p.m., an artillery strike from Abernathy struck the top of Minutemen Tower, instantly destroying the city's vital communication antennas. The Raiders knew the best way into Big Reel would be the hill to the north, so William & Mags sent a small group of raiders to the south of the city to try to create a diversion, and it worked. The Church of Atom rang its bell upon seeing the raiders, drawing the patchwork army away from the north wall. The raider army then charged the north wall of the city. By the time the patchwork army realized what was happening, it was too late. (8/12) The Raiders had broken through several positions and were trying to gain control of the loop. The battle had begun, and though already outnumbered and outsmarted, the people of Big Reel fought with everything they had. (9/12) Once inside the city, the Raiders started releasing cages of muzzled ghouls and hordes of robots. Buildings were being set ablaze while the patchwork army did everything in their power to keep the raiders away from the city's power plant. Settlers started becoming trapped in highrise buildings as many residents fled to the upper floors to get away from the robots and feral ghouls. The Raiders eventually reached the power plant, and the city fell into darkness. (10/12) The Raiders were almost victorious when suddenly, a sound could be heard coming from the east. "Attention, people of the Commonwealth! I, the mechanist, have come to bring about an era of peace. Do not be alarmed." The mechanists and an army of her robots rush into the city and join the remains of the patchwork army to drive the Raiders out of Big Reel. (11/12) Though the war was not over, the resistance of the patchwork army during the Battle of Big Reel marked the turning point for the war and its eventual end on June 24, 2296. (12/12) After the Raiders were defeated, the city would rebuild, and the settlers would finally move forward. |
2024.05.19 00:10 Bazil2009 The Battle of Big Reel 💥💥💥 #StarlightDriveIn (No Mods)
(1/12) The Battle of Big Reel occurred on November 27th, 2295, during the Nuka War. After the fall of the institute in 2289, a new threat came to the Commonwealth: the Nuka-World Raider Gangs. On October 12, 2293, the Sunshine Massacre would occur after the Nuka-World Raider Gangs invaded the Minutemen Settlement, outnumbering its residents ten to one. The next morning, a group of Minutemen and a small militia from nearby settlements would arrive, only to meet the same fate as the Sunshine settlers. Mason would then send a small force of raiders to Diamomd City to deliver a declaration of war on the Commonwealth. submitted by Bazil2009 to falloutsettlements [link] [comments] (2/12) After news spread on Diamond City radio, things escalated when the Rust Devils approached the Nuka-World Raiders Gangs for the first time and formed an alliance. (3/12) Eventually, the Raiders would push north for Abernathy to gain control of the settlement artillery. This led to the Battle of Farm Hill, which was the first major battle of the war. The Minutemen and the BOS both suffered major losses, and Abernathy fell on January 6, 2294. Much of the Raiders' success during the Battle of Farm Hill is due to their invention of mobile anti-aircraft missile turrets that practically annihilated the BOS's Vertibird Fleet. This made defeating the outnumbered Minutemen's ground troops a cakewalk. (4/12) Much of the war was then focused around Red Rocket and the City of Sanctuary. Many feared an artillery attack was coming at any given moment. A large army consisting of BOS, Minutement, and local militias was formed to prepare to defend the city from an invasion. Instead, the Raiders continued to surround Red Rocket and the City of Sanctuary, leaving a small route to the east going to Ten Pines as the only way in or out. This left most of the other settlements in the area to fend for themselves. Most settlements quickly realized this and started making preparations. (5/12) In larger settlements like Big Reel, everyone came together to fortify the city. Many believed that if the City of Sanctuary fell, Big Reel would be the next target. A patchwork army quickly formed, consisting of City Police, Minutemen, BOS, Merian Casino Security Robots, Undercover Railroad, Settlers, Synths, and Ghouls. (6/12) Big Reel's weak spot is the hill next to the city's north wall. However, if the Raiders are spotted to the south, the Church of Atom will ring its bell to alert the patchwork army to move south. (7/12) On November 27th, 2295, at 8:06 p.m., an artillery strike from Abernathy struck the top of Minutemen Tower, instantly destroying the city's vital communication antennas. The Raiders knew the best way into Big Reel would be the hill to the north, so William & Mags sent a small group of raiders to the south of the city to try to create a diversion, and it worked. The Church of Atom rang its bell upon seeing the raiders, drawing the patchwork army away from the north wall. The raider army then charged the north wall of the city. By the time the patchwork army realized what was happening, it was too late. (8/12) The Raiders had broken through several positions and were trying to gain control of the loop. The battle had begun, and though already outnumbered and outsmarted, the people of Big Reel fought with everything they had. (9/12) Once inside the city, the Raiders started releasing cages of muzzled ghouls and hordes of robots. Buildings were being set ablaze while the patchwork army did everything in their power to keep the raiders away from the city's power plant. Settlers started becoming trapped in highrise buildings as many residents fled to the upper floors to get away from the robots and feral ghouls. The Raiders eventually reached the power plant, and the city fell into darkness. (10/12) The Raiders were almost victorious when suddenly, a sound could be heard coming from the east. "Attention, people of the Commonwealth! I, the mechanist, have come to bring about an era of peace. Do not be alarmed." The mechanists and an army of her robots rush into the city and join the remains of the patchwork army to drive the Raiders out of Big Reel. (11/12) Though the war was not over, the resistance of the patchwork army during the Battle of Big Reel marked the turning point for the war and its eventual end on June 24, 2296. (12/12) After the Raiders were defeated, the city would rebuild, and the settlers would finally move forward. |
2024.05.19 00:08 Bazil2009 The Battle of Big Reel 💥💥💥 #StarlightDriveIn (No Mods)
(1/12) The Battle of Big Reel occurred on November 27th, 2295, during the Nuka War. After the fall of the institute in 2289, a new threat came to the Commonwealth: the Nuka-World Raider Gangs. On October 12, 2293, the Sunshine Massacre would occur after the Nuka-World Raider Gangs invaded the Minutemen Settlement, outnumbering its residents ten to one. The next morning, a group of Minutemen and a small militia from nearby settlements would arrive, only to meet the same fate as the Sunshine settlers. Mason would then send a small force of raiders to Diamomd City to deliver a declaration of war on the Commonwealth. submitted by Bazil2009 to fallout4settlements [link] [comments] (2/12) After news spread on Diamond City radio, things escalated when the Rust Devils approached the Nuka-World Raiders Gangs for the first time and formed an alliance. (3/12) Eventually, the Raiders would push north for Abernathy to gain control of the settlement artillery. This led to the Battle of Farm Hill, which was the first major battle of the war. The Minutemen and the BOS both suffered major losses, and Abernathy fell on January 6, 2294. Much of the Raiders' success during the Battle of Farm Hill is due to their invention of mobile anti-aircraft missile turrets that practically annihilated the BOS's Vertibird Fleet. This made defeating the outnumbered Minutemen's ground troops a cakewalk. (4/12) Much of the war was then focused around Red Rocket and the City of Sanctuary. Many feared an artillery attack was coming at any given moment. A large army consisting of BOS, Minutement, and local militias was formed to prepare to defend the city from an invasion. Instead, the Raiders continued to surround Red Rocket and the City of Sanctuary, leaving a small route to the east going to Ten Pines as the only way in or out. This left most of the other settlements in the area to fend for themselves. Most settlements quickly realized this and started making preparations. (5/12) In larger settlements like Big Reel, everyone came together to fortify the city. Many believed that if the City of Sanctuary fell, Big Reel would be the next target. A patchwork army quickly formed, consisting of City Police, Minutemen, BOS, Merian Casino Security Robots, Undercover Railroad, Settlers, Synths, and Ghouls. (6/12) Big Reel's weak spot is the hill next to the city's north wall. However, if the Raiders are spotted to the south, the Church of Atom will ring its bell to alert the patchwork army to move south. (7/12) On November 27th, 2295, at 8:06 p.m., an artillery strike from Abernathy struck the top of Minutemen Tower, instantly destroying the city's vital communication antennas. The Raiders knew the best way into Big Reel would be the hill to the north, so William & Mags sent a small group of raiders to the south of the city to try to create a diversion, and it worked. The Church of Atom rang its bell upon seeing the raiders, drawing the patchwork army away from the north wall. The raider army then charged the north wall of the city. By the time the patchwork army realized what was happening, it was too late. (8/12) The Raiders had broken through several positions and were trying to gain control of the loop. The battle had begun, and though already outnumbered and outsmarted, the people of Big Reel fought with everything they had. (9/12) Once inside the city, the Raiders started releasing cages of muzzled ghouls and hordes of robots. Buildings were being set ablaze while the patchwork army did everything in their power to keep the raiders away from the city's power plant. Settlers started becoming trapped in highrise buildings as many residents fled to the upper floors to get away from the robots and feral ghouls. The Raiders eventually reached the power plant, and the city fell into darkness. (10/12) The Raiders were almost victorious when suddenly, a sound could be heard coming from the east. "Attention, people of the Commonwealth! I, the mechanist, have come to bring about an era of peace. Do not be alarmed." The mechanists and an army of her robots rush into the city and join the remains of the patchwork army to drive the Raiders out of Big Reel. (11/12) Though the war was not over, the resistance of the patchwork army during the Battle of Big Reel marked the turning point for the war and its eventual end on June 24, 2296. (12/12) After the Raiders were defeated, the city would rebuild, and the settlers would finally move forward. |
2024.05.19 00:06 Bazil2009 The Battle of Big Reel 💥💥💥 #StarlightDriveIn (No Mods)
(1/12) The Battle of Big Reel occurred on November 27th, 2295, during the Nuka War. After the fall of the institute in 2289, a new threat came to the Commonwealth: the Nuka-World Raider Gangs. On October 12, 2293, the Sunshine Massacre would occur after the Nuka-World Raider Gangs invaded the Minutemen Settlement, outnumbering its residents ten to one. The next morning, a group of Minutemen and a small militia from nearby settlements would arrive, only to meet the same fate as the Sunshine settlers. Mason would then send a small force of raiders to Diamomd City to deliver a declaration of war on the Commonwealth. submitted by Bazil2009 to Fallout [link] [comments] (2/12) After news spread on Diamond City radio, things escalated when the Rust Devils approached the Nuka-World Raiders Gangs for the first time and formed an alliance. (3/12) Eventually, the Raiders would push north for Abernathy to gain control of the settlement artillery. This led to the Battle of Farm Hill, which was the first major battle of the war. The Minutemen and the BOS both suffered major losses, and Abernathy fell on January 6, 2294. Much of the Raiders' success during the Battle of Farm Hill is due to their invention of mobile anti-aircraft missile turrets that practically annihilated the BOS's Vertibird Fleet. This made defeating the outnumbered Minutemen's ground troops a cakewalk. (4/12) Much of the war was then focused around Red Rocket and the City of Sanctuary. Many feared an artillery attack was coming at any given moment. A large army consisting of BOS, Minutement, and local militias was formed to prepare to defend the city from an invasion. Instead, the Raiders continued to surround Red Rocket and the City of Sanctuary, leaving a small route to the east going to Ten Pines as the only way in or out. This left most of the other settlements in the area to fend for themselves. Most settlements quickly realized this and started making preparations. (5/12) In larger settlements like Big Reel, everyone came together to fortify the city. Many believed that if the City of Sanctuary fell, Big Reel would be the next target. A patchwork army quickly formed, consisting of City Police, Minutemen, BOS, Merian Casino Security Robots, Undercover Railroad, Settlers, Synths, and Ghouls. (6/12) Big Reel's weak spot is the hill next to the city's north wall. However, if the Raiders are spotted to the south, the Church of Atom will ring its bell to alert the patchwork army to move south. (7/12) On November 27th, 2295, at 8:06 p.m., an artillery strike from Abernathy struck the top of Minutemen Tower, instantly destroying the city's vital communication antennas. The Raiders knew the best way into Big Reel would be the hill to the north, so William & Mags sent a small group of raiders to the south of the city to try to create a diversion, and it worked. The Church of Atom rang its bell upon seeing the raiders, drawing the patchwork army away from the north wall. The raider army then charged the north wall of the city. By the time the patchwork army realized what was happening, it was too late. (8/12) The Raiders had broken through several positions and were trying to gain control of the loop. The battle had begun, and though already outnumbered and outsmarted, the people of Big Reel fought with everything they had. (9/12) Once inside the city, the Raiders started releasing cages of muzzled ghouls and hordes of robots. Buildings were being set ablaze while the patchwork army did everything in their power to keep the raiders away from the city's power plant. Settlers started becoming trapped in highrise buildings as many residents fled to the upper floors to get away from the robots and feral ghouls. The Raiders eventually reached the power plant, and the city fell into darkness. (10/12) The Raiders were almost victorious when suddenly, a sound could be heard coming from the east. "Attention, people of the Commonwealth! I, the mechanist, have come to bring about an era of peace. Do not be alarmed." The mechanists and an army of her robots rush into the city and join the remains of the patchwork army to drive the Raiders out of Big Reel. (11/12) Though the war was not over, the resistance of the patchwork army during the Battle of Big Reel marked the turning point for the war and its eventual end on June 24, 2296. (12/12) After the Raiders were defeated, the city would rebuild, and the settlers would finally move forward. |
2024.05.18 22:54 ChessNOW Chess.com players need to stop abandoning players just because they are losing
I am sure when ever I play chess some guy like this always comes here to ruin my day! submitted by ChessNOW to Chesscom [link] [comments] So I am a rapid player and I recently switched to blitz after this. But believe me or not she made me wait till timer 0:00 from timer 7:00. I found that in game review and the other guy is better, when he knew he was losing then he gave away all the pieces and then made me wait like 5 minutes😭😭😭 Just see this > > https://preview.redd.it/034w2mhnz81d1.png?width=2560&format=png&auto=webp&s=6ee25223d1639d0ce7f598767214073e4366af3d https://preview.redd.it/9b3qtuvnz81d1.png?width=2560&format=png&auto=webp&s=b01c728a98f2d2cd36782301e381c96983967042 |
2024.05.18 17:56 Uncle_Freddy ACRA 2024 Day 2 Reactions
2024.05.18 13:49 Shaskais Interesting bits from the 10th Chaos Space Marine codex
2024.05.18 10:12 Professional_Prune11 Escape From Heavalun Section One: Devil With Metal Skin
2024.05.18 09:44 TheMrSanta Trying to use Create Fabric, getting this error
at net.fabricmc.loader.impl.FabricLoaderImpl.lambda$invokeEntrypoints$2(FabricLoaderImpl.java:388) at net.fabricmc.loader.impl.util.ExceptionUtil.gatherExceptions(ExceptionUtil.java:33) at net.fabricmc.loader.impl.FabricLoaderImpl.invokeEntrypoints(FabricLoaderImpl.java:386) at net.fabricmc.loader.impl.game.minecraft.Hooks.startClient(Hooks.java:52) at net.minecraft.class\_310.Caused by: java.lang.ExceptionInInitializerError(class\_310.java:458) at net.minecraft.client.main.Main.main(Main.java:211) at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:470) at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74) at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
at com.simibubi.create.foundation.data.CreateRegistrate.registerBlockModel(CreateRegistrate.java:267) at com.simibubi.create.foundation.data.CreateRegistrate.lambda$blockModel$11(CreateRegistrate.java:233) at com.tterrag.registrate.fabric.EnvExecutor.runWhenOn(EnvExecutor.java:10) at com.simibubi.create.foundation.data.CreateRegistrate.onClient(CreateRegistrate.java:255) at com.simibubi.create.foundation.data.CreateRegistrate.lambda$blockModel$13(CreateRegistrate.java:233) at com.tterrag.registrate.AbstractRegistrate$Registration.lambda$register$0(AbstractRegistrate.java:124) at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) at com.tterrag.registrate.AbstractRegistrate$Registration.register(AbstractRegistrate.java:124) at com.tterrag.registrate.AbstractRegistrate.onRegister(AbstractRegistrate.java:217) at com.tterrag.registrate.AbstractRegistrate.lambda$register$1(AbstractRegistrate.java:189) at com.tterrag.registrate.fabric.RegistryUtil.forAllRegistries(RegistryUtil.java:12) at com.tterrag.registrate.AbstractRegistrate.register(AbstractRegistrate.java:188) at com.simibubi.create.Create.onInitialize(Create.java:115) at net.fabricmc.loader.impl.FabricLoaderImpl.invokeEntrypoints(FabricLoaderImpl.java:384) ... 6 moreCaused by: java.lang.RuntimeException: Mixin transformation of com.simibubi.create.content.schematics.client.SchematicHotbarSlotOverlay failed
at net.fabricmc.loader.impl.launch.knot.KnotClassDelegate.getPostMixinClassByteArray(KnotClassDelegate.java:427) at net.fabricmc.loader.impl.launch.knot.KnotClassDelegate.tryLoadClass(KnotClassDelegate.java:323) at net.fabricmc.loader.impl.launch.knot.KnotClassDelegate.loadClass(KnotClassDelegate.java:218) at net.fabricmc.loader.impl.launch.knot.KnotClassLoader.loadClass(KnotClassLoader.java:119) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525) at com.simibubi.create.content.schematics.client.SchematicHandler.Caused by: org.spongepowered.asm.mixin.transformer.throwables.MixinTransformerError: An unexpected critical error was encountered(SchematicHandler.java:77) at com.simibubi.create.CreateClient. (CreateClient.java:70) ... 20 more
at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:392) at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClass(MixinTransformer.java:234) at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClassBytes(MixinTransformer.java:202) at net.fabricmc.loader.impl.launch.knot.KnotClassDelegate.getPostMixinClassByteArray(KnotClassDelegate.java:422) ... 26 moreCaused by: org.spongepowered.asm.mixin.throwables.MixinApplyError: Mixin [raised.mixins.json:mods.CreateMixin$SchematicHotbarSlotOverlayMixin from mod raised] from phase [DEFAULT] in config [raised.mixins.json] FAILED during APPLY
at org.spongepowered.asm.mixin.transformer.MixinProcessor.handleMixinError(MixinProcessor.java:638) at org.spongepowered.asm.mixin.transformer.MixinProcessor.handleMixinApplyError(MixinProcessor.java:589) at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:379) ... 29 moreCaused by: org.spongepowered.asm.mixin.injection.throwables.InvalidInjectionException: Critical injection failure: u/Redirect annotation on redirectRenderOn could not find any targets matching 'Lcom/simibubi/create/content/schematics/client/SchematicHotbarSlotOverlay;renderOn(Lnet/minecraft/class_4587;I)V' in com.simibubi.create.content.schematics.client.SchematicHotbarSlotOverlay. Using refmap raised.refmap.json [PREINJECT Applicator Phase -> raised.mixins.json:mods.CreateMixin$SchematicHotbarSlotOverlayMixin from mod raised -> Prepare Injections -> -> redirect$fnb000$raised$redirectRenderOn(Lnet/minecraft/class_1041;)I -> Parse]
at org.spongepowered.asm.mixin.injection.struct.InjectionInfo.validateTargets(InjectionInfo.java:658) at org.spongepowered.asm.mixin.injection.struct.InjectionInfo.findTargets(InjectionInfo.java:589) at org.spongepowered.asm.mixin.injection.struct.InjectionInfo.readAnnotation(InjectionInfo.java:330) at org.spongepowered.asm.mixin.injection.struct.InjectionInfo.A detailed walkthrough of the error, its code path and all known details is as follows:(InjectionInfo.java:316) at org.spongepowered.asm.mixin.injection.struct.InjectionInfo. (InjectionInfo.java:308) at org.spongepowered.asm.mixin.injection.struct.RedirectInjectionInfo. (RedirectInjectionInfo.java:44) at jdk.internal.reflect.GeneratedConstructorAccessor65.newInstance(Unknown Source) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480) at org.spongepowered.asm.mixin.injection.struct.InjectionInfo$InjectorEntry.create(InjectionInfo.java:149) at org.spongepowered.asm.mixin.injection.struct.InjectionInfo.parse(InjectionInfo.java:710) at org.spongepowered.asm.mixin.transformer.MixinTargetContext.prepareInjections(MixinTargetContext.java:1329) at org.spongepowered.asm.mixin.transformer.MixinApplicatorStandard.prepareInjections(MixinApplicatorStandard.java:1053) at org.spongepowered.asm.mixin.transformer.MixinApplicatorStandard.applyMixin(MixinApplicatorStandard.java:395) at org.spongepowered.asm.mixin.transformer.MixinApplicatorStandard.apply(MixinApplicatorStandard.java:327) at org.spongepowered.asm.mixin.transformer.TargetClassContext.apply(TargetClassContext.java:422) at org.spongepowered.asm.mixin.transformer.TargetClassContext.applyMixins(TargetClassContext.java:403) at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:363) ... 29 more
at net.fabricmc.loader.impl.FabricLoaderImpl.lambda$invokeEntrypoints$2(FabricLoaderImpl.java:388) at net.fabricmc.loader.impl.util.ExceptionUtil.gatherExceptions(ExceptionUtil.java:33) at net.fabricmc.loader.impl.FabricLoaderImpl.invokeEntrypoints(FabricLoaderImpl.java:386) at net.fabricmc.loader.impl.game.minecraft.Hooks.startClient(Hooks.java:52) at net.minecraft.class\_310.-- Initialization --(class\_310.java:458)
Modules: ADVAPI32.dll:Advanced Windows 32 Base API:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation COMCTL32.dll:User Experience Controls Library:6.10 (WinBuild.160101.0800):Microsoft Corporation CRYPT32.dll:Crypto API32:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation CRYPTBASE.dll:Base cryptographic API DLL:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation CRYPTSP.dll:Cryptographic Service Provider API:10.0.22621.2506 (WinBuild.160101.0800):Microsoft Corporation DBGHELP.DLL:Windows Image Helper:10.0.22621.3593 (WinBuild.160101.0800):Microsoft Corporation DNSAPI.dll:DNS Client API DLL:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation GDI32.dll:GDI Client DLL:10.0.22621.3085 (WinBuild.160101.0800):Microsoft Corporation IMM32.DLL:Multi-User Windows IMM32 API Client DLL:10.0.22621.3374 (WinBuild.160101.0800):Microsoft Corporation IPHLPAPI.DLL:IP Helper API:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation KERNEL32.DLL:Windows NT BASE API Client DLL:10.0.22621.3374 (WinBuild.160101.0800):Microsoft Corporation KERNELBASE.dll:Windows NT BASE API Client DLL:10.0.22621.3374 (WinBuild.160101.0800):Microsoft Corporation MpOav.dll:IOfficeAntiVirus Module:4.18.24040.4 (aa69a05caa955e1cebcc4d2dd249082d41b510c2):Microsoft Corporation NSI.dll:NSI User-mode interface DLL:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation NTASN1.dll:Microsoft ASN.1 API:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation OLEAUT32.dll:OLEAUT32.DLL:10.0.22621.3527 (WinBuild.160101.0800):Microsoft Corporation Ole32.dll:Microsoft OLE for Windows:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation POWRPROF.dll:Power Profile Helper DLL:10.0.22621.3374 (WinBuild.160101.0800):Microsoft Corporation PSAPI.DLL:Process Status Helper:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation Pdh.dll:Windows Performance Data Helper DLL:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation RPCRT4.dll:Remote Procedure Call Runtime:10.0.22621.2506 (WinBuild.160101.0800):Microsoft Corporation SHCORE.dll:SHCORE:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation SHELL32.dll:Windows Shell Common Dll:10.0.22621.2792 (WinBuild.160101.0800):Microsoft Corporation UMPDC.dll:User Mode Power Dependency Coordinator:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation USER32.dll:Multi-User Windows USER API Client DLL:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation USERENV.dll:Userenv:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation VCRUNTIME140.dll:Microsoft® C Runtime Library:14.29.30139.0 built by: vcwrkspc:Microsoft Corporation VERSION.dll:Version Checking and File Installation Libraries:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation WINHTTP.dll:Windows HTTP Services:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation WINMM.dll:MCI API DLL:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation WS2\_32.dll:Windows Socket 2.0 32-Bit DLL:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation WSOCK32.dll:Windows Socket 32-Bit DLL:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation amsi.dll:Anti-Malware Scan Interface:10.0.22621.3527 (WinBuild.160101.0800):Microsoft Corporation apphelp.dll:Application Compatibility Client Library:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation awt.dll:OpenJDK Platform binary:17.0.8.0:Microsoft bcrypt.dll:Windows Cryptographic Primitives Library:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation bcryptPrimitives.dll:Windows Cryptographic Primitives Library:10.0.22621.3374 (WinBuild.160101.0800):Microsoft Corporation clbcatq.dll:COM+ Configuration Catalog:2001.12.10941.16384 (WinBuild.160101.0800):Microsoft Corporation combase.dll:Microsoft COM for Windows:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation dbgcore.DLL:Windows Core Debugging Helpers:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation dhcpcsvc.DLL:DHCP Client Service:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation dhcpcsvc6.DLL:DHCPv6 Client:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation fwpuclnt.dll:FWP/IPsec User-Mode API:10.0.22621.2506 (WinBuild.160101.0800):Microsoft Corporation gdi32full.dll:GDI Client DLL:10.0.22621.3527 (WinBuild.160101.0800):Microsoft Corporation glfw.dll:GLFW 3.4.0 DLL:3.4.0:GLFW java.dll:OpenJDK Platform binary:17.0.8.0:Microsoft javaw.exe:OpenJDK Platform binary:17.0.8.0:Microsoft jemalloc.dll jimage.dll:OpenJDK Platform binary:17.0.8.0:Microsoft jli.dll:OpenJDK Platform binary:17.0.8.0:Microsoft jna4234201223904327453.dll:JNA native library:6.1.4:Java(TM) Native Access (JNA) jsvml.dll:OpenJDK Platform binary:17.0.8.0:Microsoft jvm.dll:OpenJDK 64-Bit server VM:17.0.8.0:Microsoft kernel.appcore.dll:AppModel API Host:10.0.22621.2715 (WinBuild.160101.0800):Microsoft Corporation lwjgl.dll management.dll:OpenJDK Platform binary:17.0.8.0:Microsoft management\_ext.dll:OpenJDK Platform binary:17.0.8.0:Microsoft msvcp140.dll:Microsoft® C Runtime Library:14.29.30139.0 built by: vcwrkspc:Microsoft Corporation msvcp\_win.dll:Microsoft® C Runtime Library:10.0.22621.3374 (WinBuild.160101.0800):Microsoft Corporation msvcrt.dll:Windows NT CRT DLL:7.0.22621.2506 (WinBuild.160101.0800):Microsoft Corporation mswsock.dll:Microsoft Windows Sockets 2.0 Service Provider:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation napinsp.dll:E-mail Naming Shim Provider:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation ncrypt.dll:Windows NCrypt Router:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation net.dll:OpenJDK Platform binary:17.0.8.0:Microsoft nio.dll:OpenJDK Platform binary:17.0.8.0:Microsoft nlansp\_c.dll:NLA Namespace Service Provider DLL:10.0.22621.3593 (WinBuild.160101.0800):Microsoft Corporation ntdll.dll:NT Layer DLL:10.0.22621.3374 (WinBuild.160101.0800):Microsoft Corporation perfos.dll:Windows System Performance Objects DLL:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation pfclient.dll:SysMain Client:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation pnrpnsp.dll:PNRP Name Space Provider:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation profapi.dll:User Profile Basic API:10.0.22621.3527 (WinBuild.160101.0800):Microsoft Corporation rasadhlp.dll:Remote Access AutoDial Helper:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation rsaenh.dll:Microsoft Enhanced Cryptographic Provider:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation sechost.dll:Host for SCM/SDDL/LSA Lookup APIs:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation shlwapi.dll:Shell Light-weight Utility Library:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation sunmscapi.dll:OpenJDK Platform binary:17.0.8.0:Microsoft ucrtbase.dll:Microsoft® C Runtime Library:10.0.22621.3593 (WinBuild.160101.0800):Microsoft Corporation vcruntime140\_1.dll:Microsoft® C Runtime Library:14.29.30139.0 built by: vcwrkspc:Microsoft Corporation verify.dll:OpenJDK Platform binary:17.0.8.0:Microsoft win32u.dll:Win32u:10.0.22621.3593 (WinBuild.160101.0800):Microsoft Corporation windows.storage.dll:Microsoft WinRT Storage API:10.0.22621.3527 (WinBuild.160101.0800):Microsoft Corporation winrnr.dll:LDAP RnR Provider DLL:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation wintypes.dll:Windows Base Types DLL:10.0.22621.1 (WinBuild.160101.0800):Microsoft Corporation wshbth.dll:Windows Sockets Helper DLL:10.0.22621.3374 (WinBuild.160101.0800):Microsoft Corporation zip.dll:OpenJDK Platform binary:17.0.8.0:MicrosoftStacktrace:
at net.minecraft.client.main.Main.main(Main.java:211) at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:470) at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74) at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)-- System Details --
Minecraft Version: 1.20.1 Minecraft Version ID: 1.20.1 Operating System: Windows 11 (amd64) version 10.0 Java Version: 17.0.8, Microsoft Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Microsoft Memory: 224617272 bytes (214 MiB) / 687865856 bytes (656 MiB) up to 11744051200 bytes (11200 MiB) CPUs: 32 Processor Vendor: GenuineIntel Processor Name: 13th Gen Intel(R) Core(TM) i9-13900KF Identifier: Intel64 Family 6 Model 183 Stepping 1 Microarchitecture: unknown Frequency (GHz): 3.00 Number of physical packages: 1 Number of physical CPUs: 24 Number of logical CPUs: 32 Graphics card #0 name: Virtual Desktop Monitor Graphics card #0 vendor: Virtual Desktop, Inc. Graphics card #0 VRAM (MB): 0.00 Graphics card #0 deviceId: unknown Graphics card #0 versionInfo: DriverVersion=15.39.56.845 Graphics card #1 name: NVIDIA GeForce RTX 4070 Ti Graphics card #1 vendor: NVIDIA (0x10de) Graphics card #1 VRAM (MB): 4095.00 Graphics card #1 deviceId: 0x2782 Graphics card #1 versionInfo: DriverVersion=31.0.15.5222 Memory slot #0 capacity (MB): 16384.00 Memory slot #0 clockSpeed (GHz): 4.80 Memory slot #0 type: Unknown Memory slot #1 capacity (MB): 16384.00 Memory slot #1 clockSpeed (GHz): 4.80 Memory slot #1 type: Unknown Virtual memory max (MB): 76441.78 Virtual memory used (MB): 21619.83 Swap memory total (MB): 43840.00 Swap memory used (MB): 148.09 JVM Flags: 4 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance\_javaw.exe\_minecraft.exe.heapdump -Xss1M -Xmx11200m -Xms256m Fabric Mods: advancementplaques: Advancement Plaques 1.4.11 ambientenvironment: Ambient Environment [11.0.0.1](http://11.0.0.1) animatica: Animatica 0.6+1.20 appleskin: AppleSkin 2.5.1+mc1.20 architectury: Architectury 9.1.12 balm-fabric: Balm 7.1.4 betteradvancements: Better Advancements [0.3.2.161](http://0.3.2.161) bettercombat: Better Combat 1.8.5+1.20.1 betterstats: Better Statistics Screen 3.0.0-alpha.2+fabric-1.20.1 tcdcommons: TCD Commons API 3.0.0-alpha.2+fabric-1.20.1 bettertaskbar: Better Taskbar 1.7.0 betterthirdperson: Better Third Person 1.9.0 bhmenu: BHMenu-Fabric 2.4.1 blur: Blur (Fabric) 3.1.0 midnightlib: MidnightLib 1.4.1 satin: Satin 1.13.0 bobby: Bobby 5.0.1 com\_typesafe\_config: config 1.4.2 io\_leangen\_geantyref\_geantyref: geantyref 1.3.13 org\_spongepowered\_configurate-core: configurate-core 4.1.2 org\_spongepowered\_configurate-hocon: configurate-hocon 4.1.2 bookshelf: Bookshelf 20.0.4 brandedlogs: Branded Logs Fabric 1.0.1 bsvsb: Better Sodium Video Settings Button 3.0.3 camerautils: Camera Utils 1.20.1-1.0.5 capes: Capes 1.5.2+1.20 chat\_heads: Chat Heads 0.10.20 cherishedworlds: Cherished Worlds 6.1.2+1.20.1 chunksfadein: Chunks Fade In 1.0.5-1.20.1 com\_moandjiezana\_toml\_toml4j: toml4j 0.7.2 crowdin-translate: CrowdinTranslate 1.4+1.19.3 citresewn: CIT Resewn 1.1.3+1.20 citresewn-defaults: CIT Resewn: Defaults 1.1.3+1.20 cleanview: CleanView 1.20.1-v1-fabric cleardespawn: Clear Despawn 1.1.13 clienttweaks: Client Tweaks 11.1.0 cloth-config: Cloth Config v11 11.1.106 cloth-basic-math: cloth-basic-math 0.6.1 collective: Collective 7.57 connectivity: Connectivity Mod 1.20.1-4.5 continuity: Continuity 3.0.0-beta.5+1.20.1 controlling: Controlling For Fabric 12.0.2 craterlib: CraterLib 1.0.2 create: Create 0.5.1-f-build.1417+mc1.20.1 com\_electronwill\_night-config\_core: core 3.6.6 com\_electronwill\_night-config\_toml: toml 3.6.6 com\_google\_code\_findbugs\_jsr305: jsr305 3.0.2 flywheel: Flywheel 0.6.10-2 milk: Milk Lib 1.2.60dripstone_fluid_lib: Dripstone Fluid Lib 3.0.2
porting\_lib\_accessors: Porting Lib Accessors 2.3.2+1.20.1 porting\_lib\_base: Porting Lib Base 2.3.2+1.20.1porting_lib_attributes: Porting Lib Attributes 2.3.2+1.20.1
porting\_lib\_brewing: Porting Lib Brewing 2.3.2+1.20.1 porting\_lib\_client\_events: Porting Lib Client Events 2.3.2+1.20.1 porting\_lib\_entity: Porting Lib Entity 2.3.2+1.20.1 porting\_lib\_extensions: Porting Lib Extensions 2.3.2+1.20.1 porting\_lib\_models: Porting Lib Models 2.3.2+1.20.1porting_lib_core: Porting Lib Core 2.3.2+1.20.1
porting\_lib\_networking: Porting Lib Networking 2.3.2+1.20.1 porting\_lib\_obj\_loader: Porting Lib Obj Loader 2.3.2+1.20.1 porting\_lib\_tags: Porting Lib Tags 3.0 porting\_lib\_tool\_actions: Porting Lib Tool Actions 2.3.2+1.20.1 porting\_lib\_transfer: Porting Lib Transfer 2.3.2+1.20.1 reach-entity-attributes: Reach Entity Attributes 2.4.0 registrate-fabric: Registrate for Fabric 1.3.62-MC1.20.1porting_lib_data: Porting Lib Data 2.1.1090+1.20
cupboard: cupboard 1.20.1-2.0 dark-loading-screen: Dark Loading Screen 1.6.14 dcch: DCCH 1.2 debugify: Debugify 1.20.1+2.0 detailab: Detail Armor Bar 2.6.3+1.20.1-fabric distanthorizons: Distant Horizons 2.0.4-a-dev dynamic\_fps: Dynamic FPS 3.1.0 e4mc\_minecraft: e4mc 4.0.1 easyanvils: Easy Anvils 8.0.2 easymagic: Easy Magic 8.0.1 eatinganimationid: Eating Animation 1.20+1.9.61 enchdesc: EnchantmentDescriptions 17.0.8 enhancedblockentities: Enhanced Block Entities 0.9+1.20 advanced\_runtime\_resource\_pack: Runtime Resource Pack 0.6.7 spruceui: SpruceUI 5.0.0+1.20 entity\_model\_features: Entity Model Features 2.0.2 entity\_texture\_features: Entity Texture Features 6.0.1 org\_apache\_httpcomponents\_httpmime: httpmime 4.5.10 entityculling: EntityCulling-Fabric 1.6.2-mc1.20.1 equipmentcompare: Equipment Compare 1.3.7 cardinal-components-base: Cardinal Components API (base) 5.2.0 cardinal-components-entity: Cardinal Components API (entities) 5.2.0 exordium: Exordium 1.2.1-mc1.20.1 fabric-api: Fabric API 0.92.0+1.20.1 fabric-api-base: Fabric API Base 0.4.31+1802ada577 fabric-api-lookup-api-v1: Fabric API Lookup API (v1) 1.6.36+1802ada577 fabric-biome-api-v1: Fabric Biome API (v1) 13.0.13+1802ada577 fabric-block-api-v1: Fabric Block API (v1) 1.0.11+1802ada577 fabric-block-view-api-v2: Fabric BlockView API (v2) 1.0.1+1802ada577 fabric-blockrenderlayer-v1: Fabric BlockRenderLayer Registration (v1) 1.1.41+1802ada577 fabric-client-tags-api-v1: Fabric Client Tags 1.1.2+1802ada577 fabric-command-api-v1: Fabric Command API (v1) 1.2.34+f71b366f77 fabric-command-api-v2: Fabric Command API (v2) 2.2.13+1802ada577 fabric-commands-v0: Fabric Commands (v0) 0.2.51+df3654b377 fabric-containers-v0: Fabric Containers (v0) 0.1.64+df3654b377 fabric-content-registries-v0: Fabric Content Registries (v0) 4.0.11+1802ada577 fabric-convention-tags-v1: Fabric Convention Tags 1.5.5+1802ada577 fabric-crash-report-info-v1: Fabric Crash Report Info (v1) 0.2.19+1802ada577 fabric-data-attachment-api-v1: Fabric Data Attachment API (v1) 1.0.0+de0fd6d177 fabric-data-generation-api-v1: Fabric Data Generation API (v1) 12.3.4+1802ada577 fabric-dimensions-v1: Fabric Dimensions API (v1) 2.1.54+1802ada577 fabric-entity-events-v1: Fabric Entity Events (v1) 1.6.0+1c78457f77 fabric-events-interaction-v0: Fabric Events Interaction (v0) 0.6.2+1802ada577 fabric-events-lifecycle-v0: Fabric Events Lifecycle (v0) 0.2.63+df3654b377 fabric-game-rule-api-v1: Fabric Game Rule API (v1) 1.0.40+1802ada577 fabric-item-api-v1: Fabric Item API (v1) 2.1.28+1802ada577 fabric-item-group-api-v1: Fabric Item Group API (v1) 4.0.12+1802ada577 fabric-key-binding-api-v1: Fabric Key Binding API (v1) 1.0.37+1802ada577 fabric-keybindings-v0: Fabric Key Bindings (v0) 0.2.35+df3654b377 fabric-lifecycle-events-v1: Fabric Lifecycle Events (v1) 2.2.22+1802ada577 fabric-loot-api-v2: Fabric Loot API (v2) 1.2.1+1802ada577 fabric-loot-tables-v1: Fabric Loot Tables (v1) 1.1.45+9e7660c677 fabric-message-api-v1: Fabric Message API (v1) 5.1.9+1802ada577 fabric-mining-level-api-v1: Fabric Mining Level API (v1) 2.1.50+1802ada577 fabric-model-loading-api-v1: Fabric Model Loading API (v1) 1.0.3+1802ada577 fabric-models-v0: Fabric Models (v0) 0.4.2+9386d8a777 fabric-networking-api-v1: Fabric Networking API (v1) 1.3.11+1802ada577 fabric-networking-v0: Fabric Networking (v0) 0.3.51+df3654b377 fabric-object-builder-api-v1: Fabric Object Builder API (v1) 11.1.3+1802ada577 fabric-particles-v1: Fabric Particles (v1) 1.1.2+1802ada577 fabric-recipe-api-v1: Fabric Recipe API (v1) 1.0.21+1802ada577 fabric-registry-sync-v0: Fabric Registry Sync (v0) 2.3.3+1802ada577 fabric-renderer-api-v1: Fabric Renderer API (v1) 3.2.1+1802ada577 fabric-renderer-indigo: Fabric Renderer - Indigo 1.5.1+1802ada577 fabric-renderer-registries-v1: Fabric Renderer Registries (v1) 3.2.46+df3654b377 fabric-rendering-data-attachment-v1: Fabric Rendering Data Attachment (v1) 0.3.37+92a0d36777 fabric-rendering-fluids-v1: Fabric Rendering Fluids (v1) 3.0.28+1802ada577 fabric-rendering-v0: Fabric Rendering (v0) 1.1.49+df3654b377 fabric-rendering-v1: Fabric Rendering (v1) 3.0.8+1802ada577 fabric-resource-conditions-api-v1: Fabric Resource Conditions API (v1) 2.3.8+1802ada577 fabric-resource-loader-v0: Fabric Resource Loader (v0) 0.11.10+1802ada577 fabric-screen-api-v1: Fabric Screen API (v1) 2.0.8+1802ada577 fabric-screen-handler-api-v1: Fabric Screen Handler API (v1) 1.3.30+1802ada577 fabric-sound-api-v1: Fabric Sound API (v1) 1.0.13+1802ada577 fabric-transfer-api-v1: Fabric Transfer API (v1) 3.3.4+1802ada577 fabric-transitive-access-wideners-v1: Fabric Transitive Access Wideners (v1) 4.3.1+1802ada577 fabric-language-kotlin: Fabric Language Kotlin 1.10.10+kotlin.1.9.10 org\_jetbrains\_kotlin\_kotlin-reflect: kotlin-reflect 1.9.10 org\_jetbrains\_kotlin\_kotlin-stdlib: kotlin-stdlib 1.9.10 org\_jetbrains\_kotlin\_kotlin-stdlib-jdk7: kotlin-stdlib-jdk7 1.9.10 org\_jetbrains\_kotlin\_kotlin-stdlib-jdk8: kotlin-stdlib-jdk8 1.9.10 org\_jetbrains\_kotlinx\_atomicfu-jvm: atomicfu-jvm 0.22.0 org\_jetbrains\_kotlinx\_kotlinx-coroutines-core-jvm: kotlinx-coroutines-core-jvm 1.7.3 org\_jetbrains\_kotlinx\_kotlinx-coroutines-jdk8: kotlinx-coroutines-jdk8 1.7.3 org\_jetbrains\_kotlinx\_kotlinx-datetime-jvm: kotlinx-datetime-jvm 0.4.0 org\_jetbrains\_kotlinx\_kotlinx-serialization-cbor-jvm: kotlinx-serialization-cbor-jvm 1.6.0 org\_jetbrains\_kotlinx\_kotlinx-serialization-core-jvm: kotlinx-serialization-core-jvm 1.6.0 org\_jetbrains\_kotlinx\_kotlinx-serialization-json-jvm: kotlinx-serialization-json-jvm 1.6.0 fabricloader: Fabric Loader 0.15.10 mixinextras: MixinExtras 0.3.5 fabricskyboxes: FabricSkyBoxes 0.7.2+mc1.20.1 fallingleaves: Falling Leaves 1.15.6 fancymenu: FancyMenu 2.14.9 fastload: Fast Load 3.4.0 conditional-mixin: conditional mixin 0.3.2 fastload-119-0-1-2-compat: Fastload 1.19-0-1-2 Compatibility 3.4.0 fastload-1193-compat: Fastload 1.19.3 Compatibility 3.4.0 fastload-1194-compat: Fastload 1.19.4 Compat 3.4.0 fastload\_fapi\_forward: Fastload Fabric-api Forwarding 1.0.2 fastquit: FastQuit 3.0.0+1.20+ ferritecore: FerriteCore 6.0.0 forgeconfigapiport: Forge Config API Port 8.0.0 iceberg: Iceberg 1.1.15 immersive\_aircraft: Immersive Aircraft 1.0.1+1.20.1 org\_mariuszgromada\_math\_mathparser\_org-mxparser: MathParser.org-mXparser 5.2.1 immersive\_melodies: Immersive Melodies 0.1.0+1.20.1 immersive\_paintings: Immersive Paintings 0.6.7+1.20.1 indium: Indium 1.0.30+mc1.20.4 inventoryprofilesnext: Inventory Profiles Next 1.10.7 iris: Iris 1.7.0+mc1.20.1 io\_github\_douira\_glsl-transformer: glsl-transformer 2.0.0-pre13 org\_anarres\_jcpp: jcpp 1.4.14 org\_antlr\_antlr4-runtime: antlr4-runtime 4.11.1 irisflw: Iris Flywheel Compat 0.2.5 itemswapper: ItemSwapper 0.5.3-mc1.20.1 java: OpenJDK 64-Bit Server VM 17 konkrete: Konkrete 1.6.1 lambdynlights: LambDynamicLights 2.3.2+1.20.1 pride: Pride Lib 1.2.0+1.19.4 languagereload: Language Reload 1.5.8+1.20.1 lanserverproperties: Lan Server Properties 1.11 legendarytooltips: Legendary Tooltips 1.4.4 libipn: libIPN 4.0.0 lilac: LiLaC 1.0.0-beta.2 litematica: Litematica 0.15.3 lithium: Lithium 0.11.2 loadmyresources: Load My Resources 1.0.4 make\_bubbles\_pop: Make Bubbles Pop Mod 0.2.0-fabric malilib: MaLiLib 0.16.2 maptooltip: Map Tooltip 3.0.0 minecraft: Minecraft 1.20.1 minihud: MiniHUD 0.27.0 mkb: ModernKeyBinding 1.2.1 modelfix: Model Gap Fix 1.14 modmenu: Mod Menu 7.2.2 mousetweaks: Mouse Tweaks 2.25 namepain: Name Pain 1.5.2 nochatreports: No Chat Reports 1.20.1-v2.2.2 notenoughanimations: NotEnoughAnimations 1.7.3 optigui: OptiGUI 2.2.0-alpha.1 org\_apache\_commons\_commons-text: commons-text 1.10.0 org\_ini4j\_ini4j: ini4j 0.5.4 pickupnotifier: Pick Up Notifier 8.0.0 player-animator: Player Animator 1.0.2-rc1+1.20 presencefootsteps: Presence Footsteps 1.9.4+1.20.1 kirin: Kirin UI 1.15.6+1.20.1 prism: Prism 1.0.5 puzzleslib: Puzzles Lib 8.1.19 puzzlesaccessapi: Puzzles Access Api 8.0.7 raised: Raised 1.2.3 realisticsleep: Realistic Sleep 1.10.2+mc1.20-1.20.1 server\_translations\_api: Server Translations API 2.0.0+1.20packet_tweaker: Packet Tweaker 0.4.0+1.19.4
replanter: Replanter 1.3 roughlyenoughitems: Roughly Enough Items 12.0.652 error\_notifier: Error Notifier 1.0.9 roughlyenoughprofessions: Roughly Enough Professions 2.0.1 roughlyenoughresources: Roughly Enough Resources 2.9.0 searchables: Searchables 1.0.1 shulkerboxtooltip: Shulker Box Tooltip 4.0.4+1.20.1 simple-rpc: Simple RPC 3.2.2 me\_hypherionmc\_simplerpc\_simple-rpc-common: simple-rpc-common 5.0.0 skinlayers3d: 3d-Skin-Layers 1.6.4 smoothchunk: Smooth chunk save Mod 1.20.1-3.2 smoothswapping: Smooth Swapping [0.9.3.1](http://0.9.3.1) sodium: Sodium 0.5.8+mc1.20.1 starlight: Starlight 1.1.2+fabric.dbc156f status-effect-bars: Status Effect Bars 1.0.3 tectonic: Tectonic 2.3.4 terralith: Terralith 2.5.1 toms\_storage: Tom's Simple Storage Mod 1.6.6 toolstats: ToolStats 16.0.3 tweakeroo: Tweakeroo 0.17.1 villagernames: Villager Names 7.3 visuality: Visuality 0.7.1+1.20 visualworkbench: Visual Workbench 8.0.0 voicechat: Simple Voice Chat 1.20.1-2.4.24 waterdripsound: Drip Sounds 1.19-0.3.2 waveycapes: WaveyCapes 1.3.2 xaerominimapfair: Xaero's Minimap 23.6.3 xaeroworldmap: Xaero's World Map 1.34.1 yet\_another\_config\_lib\_v3: YetAnotherConfigLib 3.1.1+1.20 com\_twelvemonkeys\_common\_common-image: common-image 3.10.0-SNAPSHOT com\_twelvemonkeys\_common\_common-io: common-io 3.10.0-SNAPSHOT com\_twelvemonkeys\_common\_common-lang: common-lang 3.10.0-SNAPSHOT com\_twelvemonkeys\_imageio\_imageio-core: imageio-core 3.10.0-SNAPSHOT com\_twelvemonkeys\_imageio\_imageio-metadata: imageio-metadata 3.10.0-SNAPSHOT com\_twelvemonkeys\_imageio\_imageio-webp: imageio-webp 3.10.0-SNAPSHOT yosbr: YOSBR 0.1.2 zoomify: Zoomify 2.11.2 com\_akuleshov7\_ktoml-core-jvm: ktoml-core-jvm 0.4.1 dev\_isxander\_settxi\_settxi-core: settxi-core 2.10.6 dev\_isxander\_settxi\_settxi-kotlinx-serialization: settxi-kotlinx-serialization 2.10.6 Flywheel Backend: Uninitialized Launched Version: fabric-loader-0.15.10-1.20.1 Backend library: LWJGL version 3.3.1 SNAPSHOT Backend API: Unknown Window size:GL Caps: Using framebuffer using OpenGL 3.2 GL debug messages: Using VBOs: Yes Is Modded: Definitely; Client brand changed to 'fabric' Type: Client (map\_client.txt) CPU:
2024.05.18 08:46 mikidongdong Tarrasch question, why is the pawn sac at d4 good for White?
I understand White has a lead in development, but is there a concrete plan for white that justifies the advantage despite being 1 pawn down? Any books on this would be helpful. For reference this is Nf3 after a French Defense: Tarrasch submitted by mikidongdong to chess [link] [comments] |
2024.05.18 08:11 Bllurito Jose R. Win streak
How does one person win back to back to back like this in a lotto that has very low odds? Weird submitted by Bllurito to yotta [link] [comments] |
2024.05.18 06:38 Future-Beginning8152 Cannot Edit Gradient In Compound Path
submitted by Future-Beginning8152 to u/Future-Beginning8152 [link] [comments] |
2024.05.18 04:48 Punjavepoonpoon Americans who played abroad today: 5/13-17/24
2024.05.18 03:11 TheSpace81 A stranger in strange lands - 13 (Part 2) [English]
2024.05.18 00:49 Pilot-ridejumpfly Asus 4090 tuf with 3 tv’s
Hi! I expanded my home sim and am running a i9 12900K with the 4090 TUF OC running external visuals only. Front display is a 75” two sides are 55”. I’m getting under 26-45 depending on flight stage and how detailed the airports when on the ground. Sliders below max. Some well below. Does anyone have suggestions on my settings to improve FPS but also not lose quality? I’m not that familiar with what causes the gains and losses the most. Also, any changes with using nvidia control panel vs in sim vsync etc.. submitted by Pilot-ridejumpfly to xplane12 [link] [comments] |
2024.05.17 22:30 next3days For those in Blacksburg, here's the Rundown of Local Weekend Events (5/17/2024-5/19/2024)....
2024.05.17 22:18 HaykakanTxa Daily News Report: 05/17/2024
2024.05.17 21:51 South_Solution6245 First time DUI in NJ - Advice
2024.05.17 21:12 AdmiralMizufugu Promotional merch isn't reliable for powerscaling
“The author said” “No, he didn’t” “Yes, he did” “NO, HE DIDN’T” “YES, HE DID” submitted by AdmiralMizufugu to OnePieceScaling [link] [comments] We’ve all read the age-old debate more times than we would honestly like to. That one debate so pervasive, so long-standing that it transcends the borders across series and generations. As long as fictional media exists, it will do so as well A topic so extensive that no singular dialogue is likely to ever cover every single argument available in either side’s arsenal, dooming the discourse to be started from scratch all over again without a verdict in sight Are third-party sources reliable for drawing conclusions about the source material? In a broader sense, nobody on earth has the catch-all answer to that question, as its true answer is variable on a case by case basis. In the particular case of the One Piece manga series, we will attempt to answer that question here and now If you find reading from Google Docs more comfortable, you can do it here, which would be my recommendation due to formatting and the possibility of future updating, since this format of Reddit posts can’t be edited In this post we will aim to holistically examine the role of promotional merchandise in One Piece powerscaling, seeking to grasp the big picture of the subject as well as delving into the more technical and detailed points, while also dabbling in various adjacent topics relevant to the main conversation It would be my preference to give individual credit to every soul who has contributed their stance in this discussion, whichever it may be, but really it was an innumerable number of posts and comments over the years that collectively helped me put together this behemoth of a write-up. So, to everyone who paved the way— thank you Although there is some continuity and callbacks between sections, this is a long read so I don’t expect anyone to just sit through the whole thing in order. Feel free to see this post as more of an encyclopedia rather than an unbroken prose. Hopefully this or that individual section can be of relevance to you at some point or another For easier browsing, here’s an index: Without further ado, let’s begin! 1- Reviewing promotional material claimsAs an appetizer, let’s first go over this post’s slides and take a look at a few claims that would be confirmedly true if promotional merchandise was reliable for powerscaling the One Piece manga 1- Jozu top 1 offense and defense confirmed. Also blocked the confirmed strongest slash in the verse 2- The confirmed strongest slash in the verse couldn’t scratch him, however, somehow Daifuku is totally capable of cutting Jozu’s diamond skin that “repels anything and everything” 3- The “Most Beautiful Woman in the World” with strength that is equal to her beauty 4- Apparently Mihawk > Whitebeard and Whitebeard > Mihawk are simultaneously true, with both men being confirmed to be the strongest man at the same time 5- Tamago kicks > Kizaru kicks confirmed 6- Ben Beckman confirmed to have intimidated Kizaru in four different sources with release dates ranging from 2012 to 2022 7- Don Chinjao, the 500.000 million berry one-shot fodder, is confirmed to have rivaled Gol D. Roger 8- Marco, who has been effectively damaged after running out of stamina is confirmed to be capable of regenerating no matter how many times he’s attacked 9- Sentomaru is confirmed to be an “impregnable” guard 10- Apparently who is stronger between Wano Zoro and Cavendish is a legit question worth asking, and a rivalry between them is something that Oda wants us to seriously consider 11- Whitebeard, who has pronounced his disinterest on more than one occasion, is confirmed to have contended for the title of Pirate King 12- Old Big Mom from Wano confirmed to be stronger than prime Shanks 13- The Egghead Incident and the fate of Luffy and his crew confirmed by the editors to be addressed in Chapter 1099, which ended up being an entirely Kuma-centric flashback chapter 14- Vista is confirmed to be capable of overwhelming and cutting down any opponent no matter who they may be 15- Speed Jiru, a background WB commander with no relevance, no feats and no hype in the manga is confirmed to be faster than YC1 Marco and Yonko Oldbeard 16- Katakuri confirmed to be literally flawless both offensively and defensively and yet lost a fight to someone who is multiple tiers below the strongest characters in the verse 17- Katakuri > Big Mom confirmed 18- Doflamingo confirmed to be the toughest enemy Luffy’s ever met, after having met Magellan, Blackbeard and the Admirals 19- We’ll come back to the last couple slides later on And we are up to a rocky start. These takes certainly don’t inspire much confidence, if any. This section alone already speaks volumes about how credible third-party products really are, simply by observing the claims made by promotional merch directly from the source and without the need for additional reasoning Take into consideration— this is only a fraction of the amount of absurd or contradicting statements that can be found in promotional merch. If you take some time to go through the translations of any source of merch, you’ll come to find that these types of claims are par for the course 2- Defining reliability and promotional merchandiseA) ReliabilityBefore diving deeply into the credibility of databooks and other promotional merch, let’s first establish what does it mean for something to be reliable, and what material can actually be qualified as such We will use the word “reliable” instead of the word “canon” because the latter is a fan concept that has never been used by the author and thus can lend itself to unnecessary misunderstandings and disagreements, muddling the discussion. The word reliable is, redundant as it sounds, a much more reliable and fitting term for our objectives, and will enable us to all be on the same page moving forward A.1) What is reliability? Reliable: “Someone or something that is reliable can be trusted or believed because he, she, or it works or behaves well in the way you expect”As we can see, none of the definitions above are anywhere close to being synonyms of the words “Official” or “Supervised”. A product can be both official and supervised by the author while also not providing reliable information. This is true when it comes to information of any type about any series in general, and it’s also true when it comes to information concerning One Piece powerscaling specifically Reliable ≠ OfficialFirst-hand content from Oda directly about the manga — like the SBS — is already a given when it comes to reliability, of course, but what about everything else? Following the definitions we just established, how do we define a product that is “reliable” for accurately powerscaling the One Piece manga? To that end, it would have to be a product that we can empirically prove “can be trusted because it behaves well” (behaves well for a purpose, in this case powerscaling the manga), or that we can empirically prove is “consistently good in performance” (in this case a good performance means providing accurate powerscaling for the manga) In other words; A third-party product is only reliable for powerscaling the manga effectively when it can be empirically proven that the information it provides translates to accurate estimations of the real abilities and real scaling of characters in the actual mangaA.2) How do we apply these concepts? When evaluating any particular source, an useful approach that allows us to put things into perspective is to just ask three simple questions. Is the source official? Is it approved or supervised by the author? Is it reliable for powerscaling the manga? We’ll see that a positive response to the first two questions does not imply a positive response to the last question Oda took part in One Piece Film: Strong World, in which pre-timeskip Luffy beats old Shiki 1. Is Strong World official? Yes, it’s not fanmade, this was 100% an official project from Toei and Shueisha 2. Is it supervised by Oda? Yes, he even had a hand in writing the story himself. Nothing made it into the film without his own foreknowledge and compliance 3. Is it reliable for powerscaling the manga? Hell no. Post Thriller Bark Luffy with no training, no Haki, no Gear 4, no awakening is not beating an old legend no matter how you spin it We didn’t have to dig deep at all to find a suitable example. Information from a perfectly official source with Oda’s very own supervision and shiny stamp of approval can be unreliable for powerscaling the manga. The same can be said for a myriad of other sources with information that had Oda’s supervision or his personal approval Novels, shows, games, films, magazines— I’m sure there are plenty of examples you can come up with of One Piece products that are official and fully supported by the author while also not being reliable for powerscaling the manga effectively B) MerchandiseB.1) What is merchandise? Crudely, merchandise is defined as “goods to be bought and sold”. However, in the distinct context of the anime and manga industry that is relevant to the subject we are discussing, the more appropriate definition would be: branded products used to promote a film, pop group, etc., or linked to a fictional character; merchandising”Going by its definition, merchandise refers to branded products used to promote. The role of merchandise is not to give an accurate depiction of manga characters and events, but to make sales, create hype and get more people invested in the source material and buying other official products. In essence, it exists to promote the brand and cash in on its popularity The landscape of merchandise includes an incredibly vast assortment of products (and services or experiences) ranging from figurines to keychains to apparel to concerts to theme parks to fanbooks. In this post we will, of course, be dealing specifically with the latter. Currently, all existing arguments vouching for the reliability of a particular medium specifically concern databooks and — especially — Vivre Cards, while there are no notable arguments for magazines and other forms of media being reliable to powerscale the actual manga. Consequently, when mentioning merch from now on we will mostly be referring to databooks and Vivre Cards— which also happen to be the most prominent source for merch scaling by far B.2) What are Vivre Cards? For those who may not know, Vivre Cards are official two-page character outlines about One Piece characters— to give a few examples; the Vivre Cards of Blackbeard, Kin'emon and Marco. These cards are sold separately in many different packs/sets and meant to be progressively collected in the “Vivre Card ~One Piece Illustrated Encyclopedia~” databook, which is an initially empty binder book designed to store these collectible cards. Basically, it’s like a One Piece version of those popular World Cup collection albums In the “Profile” page of a card we can find a profile with miscellaneous information about the character, including completely original details not found in the manga (depending on the character), like their age or bounty. On the “Essence” page of a card we will find character-relevant panels ripped straight from the manga, each accompanied with a paragraph of text describing it, much like you would find in an online wiki page. This text is popularly referred to as “flavor text”, which is roughly a synonym for fluff or filler text. Most of the examples of the images above come from Vivre Card flavor text Contrary to popular belief, Vivre Cards are not written by Oda, his editors, or even anyone within the Shueisha company or its affiliates, despite Oda’s name being on the cover of card packs (including credit to the author of the source material is standard practice for derivative material, in and outside of the manga and anime industry). While Oda does provide his supervision plus some original character details and sketches, Vivre Cards are, in fact, outsourced to a book production company called Caramel Mama (キャラメル・ママ), which is in charge of the creation and publishing of the card packs Any information about the specifics of Caramel Mama’s services and work history can be found in close detail on their website. They are specialized in the elaboration of manga and anime promotional merchandise, so you may already be familiar with some of their products from other series Artur from the Library of Ohara, the most well-known Vivre Card translator in the One Piece community (you’ve likely seen his translations before), has his own explanation about Vivre Cards, which can serve as a compliment to this post for anyone interested. You can also find here his translations of the first batch of Vivre Cards, in which he describes in detail the anatomy of the cards and breaks down the information they contain B.3) What are databooks? Databooks (also known as fanbooks) are a number of books which contain a wide array of information about the story, world and characters of One Piece. This group includes the prominent collection of the 5 color-themed databooks as well as other separate individual booklets like Volume Stampede, for example. As of now, no sources claim Oda personally writes or even supervises databooks, although he does provide tidbits of original info and sketches, just as he does with Vivre Cards (we will go over this in-depth later on) Unlike Vivre Cards, which have very specific and standardized formats and topics, databook content has great variety in format and subject matter, including sections like interviews, games, gag strips, concept art, behind-the-scenes info, etc. Here is an excerpt from databook One Piece Green: Secret Spices, which gives us a peek at what the content of a more typical section of a databook looks like. As we can see, it’s composed of flavor text highlighting characters and recapping manga events, containing no original information Let’s use the Road to Laugh Tale booklet to check out a couple of very popular claims which serve as opportune examples of how databooks operate. Rocks straight up confirmed to be stronger than Primebeard? An skewed reference to Sengoku stating in the manga that he was perhaps Roger’s greatest foe (Ch. 957). Shanks being too much for the Gorosei to handle? Again, an exaggerated reference to the Gorosei’s comments in the manga (Ch. 233) When it comes to powerscaling claims, taking manga events and statements and paraphrasing them in a severely embellished manner is the standard methodology of databooks, every bit as much as it is for other sources of flavor text 3- Addressing the arguments for merch being reliableAs of now there are three prevalent arguments vouching for the validity of promotional merch, which we will be thoroughly addressing one by one in this section. As mentioned before, databooks and Vivre Cards are the only formats with arguments to fall back on, so those are the two sources we will be chiefly referring to in regard to merch A) Oda has mentioned merch in the SBSOne of the two most common arguments cites Oda referencing on more than one occasion exclusive material provided by himself for databooks, as well as describing Vivre Cards as being for “readers who want to know everything”. What do these author comments tell us about the reliability of promotional merch to powerscale the manga? Let’s find out A.1) Reviewing the SBS statements First, let’s check out every one of these instances and all additions Oda claims to have provided for merch in his SBS answers: * • SBS 293: Oda shares sketches of a pair of gag characters he mentioned in fanbook One Piece: Blue * • SBS 451: Oda references descriptions he provided of a few devil fruits belonging to marines for fanbook One Piece: Yellow * • SBS 695: Oda brings up a name he provided of a background Whitebeard fleet pirate for fanbook One Piece: Green * • SBS 914: Oda names Galette’s devil fruit and says that SBS and Vivre Cards are for “people who really want to know everything” * ○ Note: the Viz version mistranslated “ONE PIECE図鑑もありますので” as just “bonus materials” instead of “ONE PIECE Illustrated Encyclopedia” (which is specifically the name of the Vivre Card binder book, as mentioned earlier) * • SBS 982: Oda addresses the name of a Roger pirate according to fanbook One Piece: Blue Deep differing from his name in the manga, by urging to call him whatever or just not bother with his name at all * • SBS 997: Oda discloses trivia about Jinbe and mentions that Jinbe’s favorite foods were already revealed in his Vivre Card * • Vol. 108 SBS: More recently, Oda also referenced a name he provided of Roger’s sword for his Vivre Card Now, what do all of these additions from Oda have in common? 1. They are NOT about powerscaling 2. They are NOT related to flavor text or retellings/summaries of the manga in any way, shape or form 3. They are completely original worldbuilding tidbits (character names, weapon names, fruit names) Without fail, every single thing Oda comments about is a piece of trivia or original knowledge that he provided for external sources, and not one of his comments even tangentially references the endless paragraphs of hyperbolic flavor text that are published in them Based on the examples he himself puts forward in his SBS comments, we can see that by “know everything,” Oda is alluding to niche knowledge like design sketches, character names, devil fruit names— all entirely original content that he actually needs to come up with on his own. Unlike flavor text, none of these things are subjective reinterpretations of already published panels that anyone could just see for themselves in the manga volumes There is no explicit or implicit indication to be found here of Oda writing or supervising merch flavor text, or of any personal participation beyond the names and sketches he provides. The argument “Oda has brought up databooks in the SBS” may sound sensible at first glance, however, when we take the time to actually look into these SBS comments and what they are communicating, we will find that there’s hardly any evidence at all supporting the reliability of flavor text for powerscaling the manga In short, what Oda himself is personally contributing and sharing with us through databooks and other merch is not the recycled flavor text, but just the previously unheard of tidbits of info that are meant to enrich the worldbuilding and carry no major implications in the manga A.2) Oda’s philosophy on bonus materials In order to shine a light on Oda’s personal stance on bonus material and non-manga sources, here are a few insightful quotes from the man himself: “First and foremost, I am a manga artist. I don’t create anime, and that’s that. But I do help out with character design for original anime stories and movies based on my manga. I don’t really do much. So I have to entrust the world and characters of One Piece, which I created in the manga, to other people”Oda’s opinion on bonus materials expressed throughout his many comments can’t get much more clear-cut than this, and has remained perfectly consistent for over 20 years. The manga is the manga and everything else comes last. Oda is determined to include any and all even remotely relevant information directly in the manga, and when the series is 1000+ chapters, you know he’s not bluffing. If it’s not in the manga, it wasn’t important to begin with— his words, not mine Not only has Oda made the claim, but he has also proved through his actions that he has no qualms about taking a hands-off approach on non-manga material and entrusting projects, especially merch, to other people. When he actually does get involved in something, you know that it will be relentlessly promoted and we won’t ever hear the end of it. Case in point: Oda’s involvement in the live-action series Something that really stands out about these comments is that this is mostly the SBS that Oda is talking about, which actually happens to be a very reliable source written first-hand by the author himself. Even though it’s the most reliable source there is outside of the actual manga pages, Oda still insists on the SBS being an inconsequential source to the point of choosing to repeatedly reiterate how you can dismiss it entirely, as anything of importance will be revealed in the manga If that’s the author’s take on his very own work that is published on the actual manga volumes themselves, then what does that suggest about third-party products like databooks and Vivre Cards, which aren’t even first-hand sources like the SBS is? Anybody who has read the SBS corner can testify to how stubbornly unwilling Oda is to reveal anything powerscaling related in his SBS comments. If the man is adamant on not giving away straight answers on his own personally written corner published in the manga, then it firmly stands to reason that he did not — in a completely out of character manner — decide to just casually settle in some external source years ago all the age-old debates and biggest powerscaling enigmas that are still being built up in the manga to this day Let’s put forth the questions we posed before, concerning this specific argument: * • Is merch official? Yes, it’s supported by Shueisha * • Is merch supervised by Oda? No mention of that whatsoever from these comments * • Is merch trivia reliable? Yes, something like character names or fruit names are open-and-shut cases directly provided by Oda and not up for interpretation * • Is merch flavor text reliable for powerscaling the manga? Nothing in Oda’s SBS comments even begins to suggest that Oda had a hand in the flavor text from merch or that their powerscaling claims conduce to effective estimations of the reality in the manga. On the contrary, we now know for a fact that Oda is actively averse to giving away that kind of information outside of the actual manga pages B) Oda supervises Vivre CardsThe most prominent argument out there in favor of merch reliability comes from a statement from One Piece editor Naito in an interview concerning Vivre Cards, in which he states that the cards are supervised by Oda. It’s also mentioned that Oda contributes information, which will be addressed in the next point— for now, let us just focus on the elephant in the room, that being Oda supervising the Vivre Cards. Reading the full interview before proceeding is recommended Original source of the interview with editor Naito English translation (images are unavailable) B.1) Author supervision Oda allegedly checks out Vivre Cards, which inevitably raises the question: is Oda just giving a routine thumbs up simply as a formality, or is he actively correcting flavor text to make sure every word printed in them is accurate to the reality in the manga? To begin unraveling this topic, let's follow our methodology once again, but this time in the context of Vivre Cards instead of databooks: 1. Are Vivre Cards official? Absolutely. Although published by Caramel Mama, a simple search will confirm they are supported by Shueisha 2. Are Vivre Cards supervised by Oda? The answer is yes, according to editor Naito 3. Are Vivre Cards reliable for powerscaling the manga? Now this is the part where the editor statement falls short Let’s remember the definition of reliability and its criteria that we defined earlier A third-party product is only reliable for powerscaling the manga effectively when it can be empirically proven that the information it provides translates to accurate estimations of the real abilities and real scaling of characters in the actual mangaThis editor statement by itself fails to prove that Vivre Card flavor text claims translate to accurate estimations of the real abilities and real scaling of characters in the actual manga. As we’ve seen with many projects approved or supervised by Oda before, author endorsement does not automatically guarantee that the powerscaling involved will translate to actual manga accuracy. When it comes to manga powerscaling, this statement does not give promotional merch a better standing credibility-wise than the live-action series or the films, which also have the benefit of counting with author supervision To conclusively prove reliability, the merch needs a successful track record and consistency with manga showings, which is a qualification that — as we all know from reading the actual thing with our own eyes — merch spectacularly fails to fulfill. This is all the more so true for Vivre Cards, which are the single biggest culprit out there when it comes to churning out ridiculous claims On paper there may truthfully be a certain level of supervision in place, but when we look at the claims made by the Vivre Cards, it really is nigh-impossible to argue that there’s actually any back-and-forth between Oda and the third-party writers about flavor text powerscaling with rectifications being produced as a result B.2) Editors and their role In order to apply some very relevant perspective to this discussion, it’s useful to keep in mind at all times that Shueisha is a business and its editors are businessmen. Shueisha is a company whose foremost concern is to maximize value for its shareholders by securing sales and earning as much profit as possible through any means available, while its editors’ ultimate priority is none other than to turn the franchise they are in charge of into a money printer It’s a common misconception that editors are primarily artists, when in reality their job is first and foremost to handle the business side of a franchise. Editors are marketers, supervisors, representatives, publicists, salesmen and managers, and every decision they make reflects those roles. Editors of huge franchises are very, very high up on the corporate ladder, and you simply don’t get that far up in the hierarchy without proving that your motivation and actions align with the interests of the company and the shareholders This is how you end up with editors issuing blatant false promises like the Straw Hats supposedly showing up in Ch. 1099. They did not choose to publish that preview because it was the statement with the most accuracy — which ISN’T their objective — but rather because it was the statement that would generate the most sales— which actually IS their objective While Oda himself doesn’t mind being open about his indifference towards bonus material (as we went over in a previous section), you are never ever going to hear an editor in an interview declare that “the author approved this thing but didn’t really look into it that much” or that “he supervised it but didn’t really provide any meaningful feedback”, because author involvement is their biggest selling point and that’s how the entire marketing machine behind it works Career-wise, every editor is highly incentivized to overpromise and put out the kind of idealized claims and half-truths that we often see from them. The system hinges on them asserting “Oda approves this thing and he wants you to buy it”, and that is why you should never expect to hear otherwise. Author involvement will always be susceptible to be overstated, and in this case it’s an easily verifiable truth for anyone reading the bizarre, contradicting statements that databooks and Vivre Cards are publishing B.3) Information added by Oda Now, as determined earlier, it’s time to go back and take a closer look at the interview, regarding Oda “adding missing information” to the Vivre Cards. As it turns out, Oda actively contributing to merch exclusively by providing concept sketches and background details in particular is an assessment that is even supported by the editor himself Firstly, when the editor elaborates on the information being added by Oda, the accompanying image used to describe it specifically points out the yellow box from the “Profile” page and nothing else, along with the caption “Oda sensei's handwritten additional instructions”. As stated in the second section of this post, this yellow box from the “Profile” page contains an assortment of completely original knowledge that, unlike flavor text, no one could possibly interpret from manga panels, like a character’s exact height or birthday Does any of this ring a bell? It probably does, because — unsurprisingly, knowing Oda’s MO — this is the exact same situation we went over recently. What we’ve been told about Vivre Cards is perfectly consistent with the information that we already know is the kind that Oda actually prefers to contribute to bonus material, based on his own SBS comments about merch that we just checked out and that exclusively reference trivia Secondly, this is then even further confirmed by the next question and answer in the interview right after the aforementioned image and, much more importantly, we are told that flavor text is not even supposed to contain new information. Translation provided by ChatGPT: Katsuhei: Whoa~~~ Oda-sensei is serious. Are there any first-time revelations?Editor Naito is directly asked if there’s any brand new content being revealed for the first time in Vivre Cards, to which his answer is that the brand new content is the trivia information like blood types and birthplaces and the sketches from Oda. This cannot be stressed enough. Once again the editor refers specifically to concept drawings and the yellow box trivia from the “Profile” page as the material provided by Oda himself, while the flavor text in the “Essence” page isn’t even part of the equation. He then goes on to add that even just the trivia and sketches is already pushing it in terms of giving away info What we have here is an explicit clarification straight from the horse’s mouth. The statement from the editor is as blunt, clear and conclusive an answer as there could ever possibly be on the topic. Same as databooks, the only original content Oda provides to Vivre Cards are trivia and sketches. Flavor text, from the very beginning, plain and simply has never been meant to contain original information at all in the first place. Its sole purpose is to serve as filler for the collectible cards based on information that is directly compiled from the manga. Fundamentally, “Essence” pages are no different from the subjectively interpreted character articles you can find in the One Piece Wiki, except in a physical format instead To sum up: Vivre Card flavor text can agree with the manga, but it can’t add on original information to the manga or clarify any ambiguity in the manga because its one and only source is actually just the manga itself— it is by design not supposed to contain any new information or insights that weren’t unequivocally in the manga already. Any disagreement with the manga or any claim that wasn’t previously explicitly confirmed in the manga is not to be considered a new piece of reliable information, but rather a personal exaggeration or interpretation derived from the writer of that card C) There is an official website that corrects Vivre CardsLastly, the third and least recurring argument is based on an official website geared towards correcting mistakes that were caught in Vivre Cards after their printing. The logic behind the argument being this one: any of the powerscaling claims that haven’t gotten a correction yet are reliable, otherwise they would have already been addressed in the website by now Original source English translation Just like the previous two arguments, this is another case of an idea that can sound really solid on the surface, but utterly crumbles when you actually look at the source for yourself and get the full picture. What this argument fails to mention is the fact that the website covers a very specific set of mistakes, and powerscaling claims in flavor text are simply not part of that group The entire argument hangs on the assumption of there being a precedent for erroneous flavor text claims being corrected in the website, which would in turn mean that the claims that haven’t been corrected were ultimately considered accurate. Except, no such precedent exists in the first place. There is not one example of an erroneous powerscaling claim being corrected. The website deals with a narrow range of issues and has never dabbled into the subject of flavor text powerscaling, ever Anyone is free to check the website for themselves and confirm it. You can read every single correction in the page from top to bottom and will find nothing but “fixed typo, fixed year, fixed name”. Even the page’s own description refers to itself as correcting “typographical errors” So, is someone going to go back and update the list to add “My bad, Sentomaru isn’t actually an impregnable guard”? No, not at all. Nobody is showing up to take back statements that pertain to powerscaling, after hundreds and hundreds of Vivre Cards have already been published and there hasn’t been a single instance of a flavor text powerscaling claim being updated yet If someone wrote that the Germa Kingdom is from the South Blue instead of the North Blue and corrected it, or wrote that the name of the Cocoyasi Village sheriff is Gen instead of Genzo and corrected it, does that somehow make it true that Katakuri is the strongest paramecia in his family and has flawless offense and defense? No— fixing trivial mistakes like a name or a number is something completely unrelated to flavor text powerscaling claims, and under no possible reasoning whatsoever does it prove their credibility For the last time we make our questions, in the context of this argument: 1. Are Vivre Cards official? Yes, same as before 2. Are Vivre Cards supervised by Oda? No mention of Oda involvement from this website, but as we know from the editor interview earlier, the answer is still yes 3. Are Vivre Cards reliable for powerscaling the manga? Nothing about this website supports the notion of Vivre Cards being reliable for powerscaling the manga, especially when the particular cases that are handled by the website are completely removed from the area of flavor text powerscaling and doesn’t acknowledge it even once With that, we reached the Reddit post character limit. You may continue reading through the Google Doc here, or in the comments if you sort by top or controversial, depending on how the post is received |