I have to wonder if the raid screwing up is what caused them to possibly reschedule it? Needing to mess around with the internals of SV might require them to tweak the Home code.Did Niantic have to cover for TPC this week or something? Borked raid battles and PR errors are something I expect from Pokemon GO, not the brand as a whole.
The issue with the Paradox raids was the raid tables didn't properly exclude materials, so it gave "none" materials and that caused the game to crashI have to wonder if the raid screwing up is what caused them to possibly reschedule it? Needing to mess around with the internals of SV might require them to tweak the Home code.
As someone playing Go, it's generally working as intended, it's just that the developers intend something not remotely fun for most of the playerbase. It's almost the opposite of GF where Niantic has the means to make the game better and chooses not to, vs GF/TPCi who can't seem to do it right to begin withNot only does it frustrate fans but it's going to start tarnishing their public image. So much of Pokémon's content lately has been incredibly broken. GO, their TCG game, their main series games.. like.. nothing is working as intended.
Honestly would not be surprised if this is the case considering they have never officially announced HOME compatibility dates beforehand.If the date is seriously still 5/24 and they just weren't allowed to announce it I might get a migraine.
Except nothing about the Paradox event raids causing crashes, because of their drop tables having null materials, matters to Home.The delay in Pokemon Home definitely has to do with the recent Tera Raids crashing your game. It’s not a coincidence that they announced this after people’s games started crashing.
Serebii even posted times that the update/maintenance was supposed to happen:If the date is seriously still 5/24 and they just weren't allowed to announce it I might get a migraine.
The date and time were originally just posted on all the relevant pokemon.com article versions, so it applies to every western language announcement on there.Serebii even posted times that the update/maintenance was supposed to happen:
Not sure if this was from the press site or something, but seems oddly specific to have a date and release times that are just wrong.
Yes that's been a thing since last year's Home update; we had to do some testing because of vague wording maybe indicating that ANY extras would trigger the warning but iirc near as we can tell it only puts the check on exact clones.Also this is late but looking on BDSP's page, I noticed this notice that says you can only put 1 of each legendary from a save file into HOME. I guess this is how gamefreak addresses clones, but I guess this would also stop you from trading two Dialga and trying to deposit them both from the same game. I guess I missed it or forgot because it wasn't relevant for me, but this was a thing that happened that was actually a problem for some people.
https://gamefaqs.gamespot.com/boards/314255-pokemon-brilliant-diamond/80026849
View attachment 517626
View attachment 517639
They’re gonna need to release an emergency patch to fix the raid issue, which is why Home is being delayed. Only a small amount of people are currently working on the game compared to all the development, so it’s pretty reasonable (or unreasonable depending your views) that they’d need to delay it.Except nothing about the Paradox event raids causing crashes, because of their drop tables having null materials, matters to Home.
All Home does is look at the Pokemon on the save file. If anything would matter to that it would likely be on the actual update to the game coming next week; and even then that's focused on live competition issues.
They don't need to do a patch to fix the raid issue, though. They should be able to easily set custom raid tables without it. And lord knows this isn't an urgent matter anyway....the Iron Leaves/Walking Wake matter was significantly more urgent and that still took like what 2 months to fix and that did require a version update probably because of the Bad Eggs issue.They’re gonna need to release an emergency patch to fix the raid issue, which is why Home is being delayed. Only a small amount of people are currently working on the game compared to all the development, so it’s pretty reasonable (or unreasonable depending your views) that they’d need to delay it.
Someone please back me up if you have more info, but I do remember back when Legends Arceus still had "early 2022" as its release date, Amazon posted a placeholder release date of June 30, 2022.It's still early 2023.... right guys?
Also this is late but looking on BDSP's page, I noticed this notice that says you can only put 1 of each legendary from a save file into HOME. I guess this is how gamefreak addresses clones, but I guess this would also stop you from trading two Dialga and trying to deposit them both from the same game. I guess I missed it or forgot because it wasn't relevant for me, but this was a thing that happened that was actually a problem for some people.
https://gamefaqs.gamespot.com/boards/314255-pokemon-brilliant-diamond/80026849
Any extras do trigger the warning and it doesn't have to be a clone. Not only can you trip over this with local trades, but you can also trip over this with official event Pokemon (South Korea got an event Regigigas). The super dumb thing is that the check is based on the depositing game's save file ID (invisible number generated when a new save file is created) rather than Trainer ID. To trigger the warning, both Dialga/etc. must have never touched Home before.Yes that's been a thing since last year's Home update; we had to do some testing because of vague wording maybe indicating that ANY extras would trigger the warning but iirc near as we can tell it only puts the check on exact clones.
So it absolutely was meant to be the 24th and the Paradox raid bug delayed it.View attachment 519187
HOME maintenance has been announced for May 30.