Describe the bug
When loading the Settings page of Dashboard, Start Latitude, Start Longitude and Send Delay get loaded from DB with a comma as decimal separator instead of dot, making you have to manually edit when you want to update any other parameter.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Settings' in Dashboard
2. Update whatever
3. Click on 'Update'
4. See error

Expected behavior
Not having to update unchanged fields with decimal values.

Client

• French browser

Is your feature request related to a problem? Please describe.
I have currently multiple instances of rdm running for different areas that I'm scanning.
I want to merge them into one instance of RDM but there is no way to specify that a user only gets access to a specific area of scanned quests. I don't want a user to have access to all quests and IV.

Describe the solution you'd like
Create user roles to assign users to specific scanned areas (could be done with geofences).

Is your feature request related to a problem? Please describe.
Correctly distinguish between "banned" und "suspended" (for 30 days) accounts, when detecting a punishment.

Describe the solution you'd like
Pixel check for "30" in "..you are suspended/banned.."-screen.

Describe alternatives you've considered
Get it via proto, if there is one.

Additional context
We could then use suspended accounts again after 30 days, without having to check thousands of permabanned accounts as well.

Is your feature request related to a problem? Please describe.
It's always long and tedious to update the Pokemon IV prio list on instances: having to load the page, edit one Pokemon IV instance, update, wait for page to reload, re-do with next instance, etc.

Describe the solution you'd like
Would be nice if there was a setting in dashboard for "default prio list" where you can update once and all instances using the default settings get automatically updated, unless they have their own prio list set.

Describe the bug
Level instance goes its own route, while thats a great idea it results in the phone going way to far from starting location where we get a lower stop density and a lower xp/h

To Reproduce
Steps to reproduce the behavior:

1. Use level instance in center of paris
2. See it go way to far away on map

Expected behavior
Maybe add a geofence to restrict it

Screenshots
http://prntscr.com/s0pfca

Is your feature request related to a problem? Please describe.
At the moment auto-assignments are all separate, and for example in case of quest re-roll starting a scan on different areas is long.. Or switching to a different scan configuration during CDays for example.

Describe the solution you'd like
Possibility to have Assignment Groups where different assignments for different devices can be started all at once with one click.

Describe alternatives you've considered
Maybe have a checkbox in auto-assignment page to select multiple lines and "start all selected"

Is your feature request related to a problem? Please describe.
It's a pain to clear each IV instance's queue when needed.

Describe the solution you'd like
Would like a "Clear IV Queues" Utility (Misc -> Utilities) that clears all IV Queues with a single click.

Describe alternatives you've considered
None

Additional context

Describe the bug
When a device gets removed, new leveling instance seems to have problems.
I had two devices on a dedicated leveling RDM docker instance, and removed one of them (deleted the device from the database through phpmyadmin since RDM doesnt have a clean way to delete devices).
The "instances" page still shows two accounts being used, and it doesnt spin any stops.
XP/hour are at 0%.

To Reproduce
Steps to reproduce the behavior:

1. Create dedicated RDM docker instance for leveling
2. Assign two devices to leveling instance.
3. Remove one of them (delete device from database)
4. Check instance page.

Describe the bug
Account page is a mess.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://website.com/dashboard/accounts
2. Open eyes.

Expected behavior

1. Cooldown column should go as it depends on where and how you would want to use it.
2. 'banned' column should be split up into 'permban' and '30day ban'
3. accounts should not be good & shadowbanned at the same time.

Describe the bug
Using a smart raid instance, if a scan fails in a scan location where there are multiple gyms, and one gym has an egg active, Smart Raid will fail to return to update the other gyms.

Issue has been discussed in detail on Discord. Posting here so it doesn't get forgotten.

Is your feature request related to a problem? Please describe.
Niantic goes all in on costumes. So should rdm.

Describe the solution you'd like
A costume column in gym table.

On my map I see the moveset listed when the raid is just an egg.

Should the raid_pokemon_move_1 and raid_pokemon_move_2 be set to null when saving a new egg to the db?

Describe the bug
Dashboard does not reflect the true status of accounts.

To Reproduce
Steps to reproduce the behavior:

1. Go to Dashboard
2. Click on Accounts
3. Scroll down to view your account status.
4. Cross reference with database queries to see numbers that don't match, and stats that aren't useful.

Expected behavior
A clear, accurate description of account statistics, including good, warned, banned (and suspended would be nice).

• Stats should accurately reflect the true account status.
• 'Other' column has never served any purpose, should be removed or have reason.
• 'Banned' column should be split up into 'permban' and '30day ban' (suspended).
• Accounts should not be good & shadowbanned at the same time.
• Warned accounts that have passed warning expired date should be (optionally) set to good.

System

• Running in docker: yes
• RDM Version: PR#83

Additional context
As per issues discussed in Discord related to expired warnings, suspensions, and other incorrect Dashboard account stats.

Describe the bug
When you configure RDM to send webhooks, it will often send duplicates or multiples of the same webhook event. This creates a big problem for notification systems (such as existed back with NovaBot). The problem has existed for over a year, and still remains unaddressed.

To Reproduce
Steps to reproduce the behavior:

1. Go to Dashboard, and setup a Webhook (Interval seems to make no difference)
2. Setup any webhook listener (WDR, Brock, NovaBot, PokeAlarm, etc..).
3. Wait a bit.
4. See multiples of the same webhook come through.

Expected behavior
I expect only one webhook per single unique event.

Screenshots
Here is an example screenshot of a Discord Rocket Pokestop Notification being generated from a RDM Webhook. The webhook event is sent SEVEN times from RDM, each 5s after the next:

This issue affects ALL types of webhook events, Pokemon, Raids, Quests, etc... They are most often in duplicate, but higher multiples as exampled above are not uncommon.

System

• Running in docker: yes
• Host OS: Ubuntu 18.04
• RDM Version: This issue has existed in all RDM versions since 2019

Additional context
This is a very annoying issue for end users and anyone trying to manage webhook data. There must be a way to cache and/or check for duplicates without causing a flood of unnecessary, duplicated webhook data.

Describe the bug
Circle smart raid is not going back to check eggs after they hatch.

To Reproduce
Steps to reproduce the behavior:

1. create a circle smart raid
2. watch it not go back and get ?? for raids

Expected behavior
Circle smart raid is supposed to jump to gyms that are about to hatch to eliminate having to wait to see the boss after the egg has hatched.

Describe the solution you'd like
Currently we can have multiple fixed time assignments but only 1 oncomplete.
Example: I have 1 area i want to scan for quests 100% but i do have about 4 hours left untill 8am in the morning. I want to utilize those 4 hours to get some extra quests scanned. I can use a on complete to go to the secondary quest instance but that one only takes 2 hours so still 2 left. The time the second one finishes varies everyday so to make the most of every minute i would like to chain up multiple oncomplete triggers.

So if we can give a priority number to each on complete. If priority 1 is complete do 2 if 2 complete 3 and so on.

For date/time assignments this comes in place for events like community day or other specific events that are worth changing focus on what is scanned at that time.

Since we don't have rdmui anymore we need a way to enable or disable devices (and avoid mass login).

Describe the bug
After the leveling instance has reached the max level a new account is not selected unless max account level is modified to a lower level.

To Reproduce
Steps to reproduce the behavior:

1. Go to Instances page
2. Find a leveling instance
3. Wait for an account to reach max level
4. See the account has reached max level but a new account is not selected to continue leveling

Expected behavior
A new account should be selected for leveling once an account has reached max level.

System

• Running in docker: no
• Docker Engine Version: [if applicable, e.g. 19.0]
• Host OS: Ubuntu 16.04
• RDM Version 1.6.13

Is your feature request related to a problem? Please describe.
No.

Describe the solution you'd like
Just a click to scan functionality. Clicking on a point on web map it will send a worker to scan that location.
Useful on cases where a rare Poke its outside of the IV geofence or you just want to scan a different location for a reason.

Describe the bug
When a account reaches lvl30 in level instance and gets swapped out the status says 999h0m until next level

Expected behavior
make it show 0h0m or clear the account from status

Screenshots
http://prntscr.com/s3blzg

Is your feature request related to a problem? Please describe.
With UltraQuest, RDM receives data from 40m80m, this means all quests inside this circle are received at same time, so a quest instance based on circle method should be more efficiency.

Describe the solution you'd like
Do extra quest instance like CirclePokemon behaviour

Describe alternatives you've considered
Change auto_quest behaviour is not an option due some users maybe don't have UltraQuest enabled, the only option is add a new quest instance

Is your feature request related to a problem? Please describe.
When ex passes go out niantic removes ex tags. RDM pick this up and updates database as if its not a ex gym at all.

Describe the solution you'd like
If possible: 2 columns. 1 that always tells if its a ex gym, the other to show if passes are send out or not.

Describe the bug
Account does not switch when its in a huge cooldown

To Reproduce
Steps to reproduce the behavior:

1. Assign phone to quest instance
2. wait until it spins a stop
3. Assign it to level instance on a location far away
4. Wait hours in cooldown

Expected behavior
Switch account instead of wait

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:
Quest instance is pretty big with remote rural areas. But quests not scanned change everyday either downtown where hundreds are in range. The next day it might actually be a remote few.

Expected behavior
A clear and concise description of what you expected to happen.

Complete quests instance 100%

Screenshots
If applicable, add screenshots to help explain your problem.

System

• Running in docker: yes
• Docker Engine Version: [if applicable, e.g. 19.0]
• Host OS: [e.g. Ubuntu 18.04]
• RDM Version [e.g. 2.0.0]

Additional context
Add any other context about the problem here.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Is there a way to add in GetPlayer response in RDM so the details for trainerName, Level etc can be sent via web hook

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Describe the bug
Quest instance failed to complete due to not able to retrieve correct account. There were plenty of accounts available but the instance kept on logging in on the accounts that reached the spin limit.

To Reproduce
Steps to reproduce the behavior:
Quest instance logging in and out on accounts that has reached its spin limit. looping between 2-3 same accounts that has reached spin limit and did not grab other fresh accounts.

Expected behavior
Quest instance should try to retrieve accounts that has not reached the spin limit.

System

• Running in docker: yes
• Docker Engine Version: 19.03.8
• Host OS: Ubuntu 18.04
• RDM Version 1.6.8

Is your feature request related to a problem? Please describe.
Rdm instance is fine. database is corrupt. Wanting to start with a completely fresh database means a complete re-install of rdm.
Describe the solution you'd like
A method to recreate the database structure.
Describe alternatives you've considered
just creating the table myself as described here

Describe the bug
Level instance stores spawns, spawnpoints, gyms etc. We dont have any reason to do that and only creates more load on database.

To Reproduce
Steps to reproduce the behavior:

1. use level instance
2. get useless data

Expected behavior
Don't store the data at all.

Is your feature request related to a problem? Please describe.
Currently, forcing RDM to use warned accounts breaks quest instances due to a mitm provider issue. But beyond that, it is also a preference of several mappers to only use good/clean accounts.

Describe the solution you'd like
A checkbox in the dashboard that would tell RDM to only use accounts in a good state, making it optional to use or not use warned accounts.

Describe the bug
When you click truncate Pokémon table in utilities the popup says it truncated 0 Pokémon.

To Reproduce
Steps to reproduce the behavior:

1. Go to dashboard/utilities
2. Click on Truncate Pokémon Table
3. See issue in popup.

Expected behavior
Give a real number or not at all.

Describe the bug
Some devices still have login loops on Quest Instances

To Reproduce
Steps to reproduce the behavior:

1. Start a device in an quest instance
2. Device will try to scan_quest, but switch_account is also sent at the same time so quest is skipped
3. This will happen over and over while no quests are scanned

Expected behavior
Devices should not be logged out while trying to scan for quests.

System

• Running in docker :yes
• Host OS: Ubuntu 16.04
• RDM Version 1.11.3

Additional context
Add any other context about the problem here.

Describe the bug
When a device inits for first login, if no accounts less than tl 30, then rdm does not handle device.
To Reproduce
Steps to reproduce the behavior:

1. Have only level 30 in database
2. Start rdm
3. Watch all devices fail

Expected behavior
Device to init with assigned instance data reducing unecessary logins and eliminating this issue (bonus, solves 2 isssues)
Or
Raise level defaults from 1-29 to 1-30 (and still have unecessary logins :/)
Screenshots
If applicable, add screenshots to help explain your problem.

System

• Running in docker: [yes|no]
• Docker Engine Version: [if applicable, e.g. 19.0]
• Host OS: [e.g. Ubuntu 18.04]
• RDM Version [e.g. 2.0.0]

Additional context
Add any other context about the problem here.

Describe the bug
The column definition for username on rdmdb.pokemon is set to varchar(15). It is varchar(32) on every other table that has username. This allows you to import usernames longer than the max limit for rdmdb.pokemon. The insert fails silently when a username longer than varchar(15) is attempted to be inserted.

To Reproduce
Steps to reproduce the behavior:

1. Import an account with a username longer than varchar(15) and less than varchar(32)
2. Login to account.
3. Watch it fail.
4. `docker logs realdevicemap --timestamps | grep "too long for"`` should pull up the error.
   Expected behavior
   Expected behavior: make me a warm meal after work, tell me you love me..wrong website.
   Matching column definitions across all tables in a database would be a great place to start.

Screenshots
N/A

System

• Running in docker: [yes]
• Docker Engine Version: [N/A]
• Host OS: [N/A]
• RDM Version [highTable3000]

Additional context
If no "shiny stats" there would be no problem. 98% of the issues I see across almost every user trace back to rdm trying to be a one stop shop. In trying to do everything great, it kinda is starting to nothing well. My 2 cents and a nickel.

Is your feature request related to a problem? Please describe.
It's a pain to update each IV Instance's IV Priority List

Describe the solution you'd like
Would like to store and save IV lists. Then for IV instances, select the IV Priority list from a drop down instead of copying/pasting into the text box.

This would allow the editing saving of a single IV Priority list that would update all instances that are using that particular list.

Describe alternatives you've considered
Currently use cut and past from a local file that has each priority list.

Additional context

Describe the bug
resources/migrations/3.sql
ERROR 1146 (42S02): Table 'rdmdb2.metadata' doesn't exist
ERROR 1146 (42S02): Table 'rdmdb2.metadata' doesn't exist
ERROR 1146 (42S02): Table 'rdmdb2.metadata' doesn't exist
ERROR 1146 (42S02): Table 'rdmdb2.metadata' doesn't exist
Insert into metadata... table not created in 1.sql, 2.sql, or 3.sql

1. login to mysql
2. Create database rdmdb; use rdmdb;
3. source ~/migrations/1.sql
4. source ~/migrations/2.sql
5. source ~/migrations/3.sql
6. ERROR 1146 (42S02): Table 'rdmdb2.metadata' doesn't exist
   Expected behavior
   When creating a fresh database, the source files to create the database work?
   Screenshots
   If applicable, add screenshots to help explain your problem.

System

• Running in docker: [rdm:yes db:no]
• Docker Engine Version: [if applicable, e.g. 19.0]
• Host OS: [e.g. Ubuntu 18.04]
• RDM Version [e.g. 2.0.0]

Additional context
Add any other context about the problem here.

Is it possible to get the weather conditions send in the raid webhooks ?

Describe the bug
When iphones are sitting on a complete quests instance something triggers a shit ton of requests and calculations causing RDM to flood and kill itself.

To Reproduce
Steps to reproduce the behavior:
Put a few iphones on a quest instance that is 100% complete

Expected behavior
When a quest instance is complete it doesn't have to do any calculations just send a "pause" the the device. Would be fancy if we could make it go to the next instance. As asked in #135

Screenshots
If applicable, add screenshots to help explain your problem.

System

• Running in docker: yes
• Docker Engine Version: latest
• Host OS: debian 10
• RDM Version latest

Is your feature request related to a problem? Please describe.
I have slightly more than 25 instances, and after waiting for the page to load I have to keep tabbing over to the next page just to see the remaining few. There is a dropdown for showing 25, 50, 100 or All, but nowhere to set what you would like that default number to be.

Describe the solution you'd like
An option in general settings to change the default number of values loaded on such pages as Instances, Devices, Auto-Assignments and such.

Describe alternatives you've considered
Not really relevant here

Additional context
Should be pretty obvious what I'm asking for. There's obviously something hard-coded to set that default to 25 and it would be nice if we could change it to 50, 100 or All.

Describe the solution you'd like
RDM writes Instance done in docker logs but why not add timestamp into a extra DB column so it can be shown in the instance overview page on the dashboard.

https://github.com/123FLO321/RealDeviceMap/blob/f94347099b441ef1b26a14d99ea23df914be5452/resources/webroot/static/data/en.json#L1040

Describe the bug
Built RDM in Ubuntu 18.04 without docker. Pointed to external mysql db. Start rdm and everything rungs great.
As soon as I goto the UI (http://localhost:9000), login and try to go to any other page (devices, accounts, instances, settings, etc...), rdm crashes with the following error:

Could not cast value of type 'RealDeviceMap.Pokemon' (0x55f3f9f53510) to 'Foundation.NSObject' (0x7f32a2e89a30).

Using swift 4.1 with swiftenv per readthedocs instructions.

To Reproduce
Steps to reproduce the behavior:

1. Start RDM
2. Goto http://localhost:9000
3. Login
4. Try to navigate to any other page
5. RDM crashes with:
   "Could not cast value of type 'RealDeviceMap.Pokemon' (0x55f3f9f53510) to 'Foundation.NSObject' (0x7f32a2e89a30)."

Expected behavior
Expect to be able to navigate through UI menus.

Screenshots
If applicable, add screenshots to help explain your problem.

System

• Running in docker: no
• Docker Engine Version: not applicable
• Host OS: Ubuntu 18.04
• RDM Version: Master branch

Client

• OS: Any
• Browser Any

Additional context
Swift 4.1 via swiftenv

Something that would help a lot would be to have the ability to see Ban and Warning statistics for the past 24 hours. I often add new accounts and like to rotate them when I can and having the last 7 days as the most recent makes it tough to keep track of how fast accounts are getting banned/warned.

Another great option would be to have the "accounts in use" viewable by each level (like we have with banned/warning/invalid/etc). Maybe have it labeled, "in use".

Many come to this github, see the README in its bare state with a link to vote on features, and assume there's no tutorial to install.

There is, in fact, it's just in the wiki.

Most people don't click on the wiki because, in my experience, most projects just don't use it and for most projects all the useful stuff is in the README.

It's the opposite case for this project. Can we link from the README to the Wiki? It'll reduce questions on the discord.

Would it be at all possible to allow the option for a full leveling route (like before) rather than a single coordinate only?

I say this because my 0-30 leveling times are WAY slower now and I have really great custom paris and tokyo routes I'd love to use instead.

Currently the latest RDM build is not working correctly with Ultra Quest. All devices are failing to scan due to wrong cooldown calculation.

Describe the bug
Insert fails somewhere that has column shiny.
Failed to execute query. (Out of range value for column 'shiny' at row 1\r\n","stream":"stdout","time":"2020-02-06T14:06:35.091622027Z"}
This is a brand new stock database created lastnight, with fix for issue 33.
To Reproduce
Steps to reproduce the behavior:

1. No clue but...,
2. In terminal docker container inspect realdevicemap
3. Look for filename for "LogPath", Copy path and filename
4. grep -wc "Out of range value for column 'shiny'" path/to/reallylongnamedfile.json will give count of occurences
5. grep -m 1 "Out of range value for column 'shiny'" path/to/reallylongnamedfile.json prints date of first occurrence.
6. Scratch head to find where this error originates.,,,

Expected behavior
Not to have data lost for arbitrary things like "isShiny".

Screenshots
If applicable, add screenshots to help explain your problem.

System

• Running in docker: [yes]
• Docker Engine Version: [if applicable, e.g. 19.0]
• Host OS: [e.g. Ubuntu 18.04]
• RDM Version [current]

Additional context
My comments yesterday were in reference to things like this. Development is not necessarily adding features, it is also resolving issues and verifying that there are no current issues. In that process when an issue is identified, most of the time it's necessary to stop and ask a couple questions.

1. Is this a necessary feature?
2. If yes, stop adding new content until any and all conflicts are resolved. Otherwise we are just pouring gas on a fire.
3. If no, remove it.
   Currently, from what I see, we are in pour gas on fire mode.
   just doing a grep count for the occurrence of "ERR" (error) on a log file from a container created 6 hours ago, 100% stock returns a count of 431,931. That is somewhat unsettling.

Is your feature request related to a problem? Please describe.
Generating >250K images taking >7 Gb is ugly and a headache for new server setup. Without enough horsepower this can crash a server -- happened to me on latest version on a linux vm.

Describe the solution you'd like
Implement an image overlay solution using existing images for quest_invasions. Wasn't there one on gitlab before the move?

Additional context
Anything that could help the pain setting up new. Copying from existing server works if both are local, but moving 7Gb remotely is not much better.

Is your feature request related to a problem? Please describe.
More and more users are looking for PvP mons. But we dont have any way to show how good mons are or easy filter on them.

Describe the solution you'd like
Invent a ranking system based on IV stats for each league and store it in pokemon table / send it in webhook.

Describe alternatives you've considered
Implementation in PMSF. But i dont think thats the proper way to do it.

https://github.com/123FLO321/RealDeviceMap/blob/f94347099b441ef1b26a14d99ea23df914be5452/resources/webroot/static/data/en.json#L1055

Would be nice if we had a counter to tell us how many scans each device is doing on raid or Pokemon scanning, ive included a quick example screenshot ...