Why does Nimbus for 3DS specifically use the `test` environment?

Technical Discussion
1

On a normal retail unit only one local account is ever made, which is set to the prod NASC environment. Local accounts may be set to prod , test or dev . Nimbus makes use of this unused feature to create sandboxed local accounts with different environments

This quote was pulled from the Pretendo Network website.

Why does Nimbus specifically use the test environment to run Pretendo on a 3DS? Why not dev? Is this because of technical limitations?

1 Like
2

I don’t think there’s any specific reason, I assume test was just chosen because it’s the first one after prod.

3

Could someone make a homebrew that put any other online homebrew services (for instance, the rverse archive) into the dev environment? I feel that would solve the issue of two services overlapping each other.

4

Sure, that would be possible. The other service would just use a separate account and need to host its own account server - it would be completely separate from Pretendo.

5

The test environment was chosen because that environment loads a different set of URLs for going online (the test server URLs). This let us make an IPS patch that was able to stay loaded at all times, which only replaced the test environment URLs, without affecting the production URLs (which is what is used by the main Nintendo Network user)

3 Likes
6

Then does the dev environment also make it’s own URLs?

7

Yes, the dev env uses it’s own URLs

8

2 posts were merged into an existing topic: Questions about rverse archive in Pretendo Network

9

So if all environments issue their own URLs, I guess @MatthewL246_PNID’s assumption that the test environment, because it comes directly after prod, was chosen for Nimbus, is true?

10

Yes, it’s just because it was the first one after prod. Using dev would have worked too, we just went with test

3 Likes