You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 18, 2020. It is now read-only.
Please enter some information which help us solving this issue.
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like
Setup
I am using the latest version of this tool
Installed using Docker
Installed via precompiled zip-Archive
Cloned and locally built
Browser Console Output
Each browser has a Dev-Console. Please open it and paste the output inside the
triple ticks (```). To open it, follow these steps:
Chrome / Chromium / ...: CTRL + SHIFT + I, then switch to the tab Console
Firefox: CTRL + SHIFT + I, then switch to the tab *Console"
Important are the red lines, which indicate an error.
# delete this line and enter your console output
Other Console Output
Are there any other errors? Paste them here:
# more output, which could be useful
Description
I am not exactly sure how, but I sent the project to a friend of mine, who managed to get a working installation on his server so it could be accessed online.
We are 3 friends who play Pokémon Go, the installation was intended to be used by all 3 of us, when we play the game together. Running on an assumption that 3 persons connecting to a website will never be noticeable enough for Niantic to shut it down.
I go to his website and log in, everything works just as it does locally and I can see my Pokémon like I can locally, all of a sudden I see strange nicknames that I know I don´t have in my game, I haven´t used these nicknames for anything I´ve caught, turns out it´s my friend who is hosting the server who´s pokémon I can see all of a sudden, after enquiring about this it turns out he can see mine when I take "control" of the session. Leading me to believe that the script is made in such a way that only one session is allowed at a time. I don´t know if this is by design, or a bug, I just thought I´d report it in case it turns out that it is a bug and not a design choice.
The text was updated successfully, but these errors were encountered:
yes this is by design, as the tool was supposed to be used localy. We are currently thinking about building in a session manager so multiple people could use one installation.
In fact there is an outdated sketch in the feature/seassions branch of the repository. If one of you can programm you could try to get it into the newest version. (If you do, i would love a pull-request :) )
I think we will be adding this feature in the future, but its on the lower end of the priority list right now.
Thanks for contributing!
x
into all the boxes [ ] relevant to your issue (like that [x])Setup
Browser Console Output
Each browser has a Dev-Console. Please open it and paste the output inside the
triple ticks (```). To open it, follow these steps:
Important are the red lines, which indicate an error.
Other Console Output
Are there any other errors? Paste them here:
Description
I am not exactly sure how, but I sent the project to a friend of mine, who managed to get a working installation on his server so it could be accessed online.
We are 3 friends who play Pokémon Go, the installation was intended to be used by all 3 of us, when we play the game together. Running on an assumption that 3 persons connecting to a website will never be noticeable enough for Niantic to shut it down.
I go to his website and log in, everything works just as it does locally and I can see my Pokémon like I can locally, all of a sudden I see strange nicknames that I know I don´t have in my game, I haven´t used these nicknames for anything I´ve caught, turns out it´s my friend who is hosting the server who´s pokémon I can see all of a sudden, after enquiring about this it turns out he can see mine when I take "control" of the session. Leading me to believe that the script is made in such a way that only one session is allowed at a time. I don´t know if this is by design, or a bug, I just thought I´d report it in case it turns out that it is a bug and not a design choice.
The text was updated successfully, but these errors were encountered: