Before asking, I did some trying and researching and came to the conclusion that, to upload on Miiverse from inside a game, I need to open the Miiverse app at least once, which is not possible on a console that’s connected to pretendo using SSSL and not modded.
However, on the pretendo website it says that there’s support for Cemu, and then there’s a web tool called Dumpling, which doesn’t need to hack the console to be used:
So, assuming I dump the files necessary for online play and put them on Cemu, my question is: would it be possible to do that first-time opening of the Miiverse app on Cemu and then upload posts from the game on a real non-modded console?
On a side note that I don’t know if it has to do with that first-time run or not, if i log into the juxtaposition/miiverse website ( https://juxt.pretendo.network/titles/show?src=login ) and log in, it says “Account Creation is only available when you have a linked Wii U or 3DS.”. I just played a race of mariokart 8 online a moment ago to see if something was wrong, but I could play fine, so I assume it’s linked? (or am I going to the wrong website? That’s the one that came up first when searching online)
I’m not sure Juxt works on cemu. Obviously if you are using SSSL on your WIIU you can’t access juxt.
There is another topic asking if juxt works on cemu and jon explained how to do that (its hard), im not sure if you could do it on an unmodded console sadly.
Maybe a moderator knows more?
People have got Juxtaposition running on Cemu (it might have been only Jon though tbh) but I’m fairly sure you can’t easily set it up. I wouldn’t have any instructions on getting that set up anyways.
You can only access Juxtaposition on web when you complete the setup for Juxt on a console and you’re unable to do that on SSSL.
This isn’t true, and wouldn’t make much sense from a technical perspective anyway. This would imply some system-wide check exists, when Miiverse functionality is done on an account-level basis. Also I’ve used Miiverse features in game using SSSL before on accounts (and consoles) which have never used the Miiverse app, nor has anyone else reported this to be an issue since we launched SSSL from what I can tell. So the entire premise of the question seems flawed
The Miiverse app and the Miiverse API used by games are 2 entirely different services. The in-game API is a standardized API made specifically for games to use. The Miiverse app itself is just a web app which can define its own standards
"Before using this online service you must start Miiverse at least once.
Access Miiverse from the HOME menu and add your user information."
I did use Miiverse back when it was available on another user account, but this one was made recently and specifically for pretendo, so i never accessed miiverse with it.
Not sure if this makes a difference somehow, but this is an European Wii U, not an American one.
This looks like an issue on our end. I brought this up with the Miiverse devs so we can look into it. Not sure when this got introduced, since I’ve definitely used SSSL to access Miiverse features in games on accounts that have never used the Miiverse app itself, but it’s being looked into
I could be wrong, but it’s due to needing to “create” a Juxt Account, which can only be done by opening Miiverse on a Wii U/3DS and then following the setup, agreeing to the rules, selecting your game experience level.
Even signing in on Juxt Web on a brand new PNID tells you to open Miiverse on a console first.
When I used In Game Posting on SSSL it didn’t even allow me to post it will just take a extremely long time and then it would say error 115-0505 (iirc that was the error) unable to connect to the server and it wouldnt even have the posting thing up.
I just tried in-game posting with SSSL again and this time it worked!
However, that was after modding my 3DS and reading and accepting to the rules and other information that appears when opening Juxt/Miiverse for the first time. I assume that’s what fixed it (mostly since that’s also what unlocked being able to access juxt from a web browser), but I’m not entirely sure if the fix was something that the devs did to the servers since last time I tried or that.
The important thing is that the problem is gone, so I’m marking the thread as solved
