+admin warning

FAQ-&-Common-Issues.md

@@ -22,4 +22,7 @@ To close the console, one may do any of the following:
 With UDP, packets can easily arrive in the wrong order or not at all. The advantage is lower overhead. TCP solves the mentioned problems at protocol level. Because OpenRCT2 does not send a large amount of updates (it doesn't send peep positions for example, those are calculated by the clients) the higher overhead of TCP is not a problem, while the extra accuracy helps to prevent desyncs.
 
 ### I've set my RCT1 path and disabled scenario unlocking, but where's Mega Park?
-Mega Park is usually unlocked and shown upon successful completion of all RCT1 (not CF/AA & LL) scenarios, but can be unlocked by setting `scenario_hide_mega_park` in the config file to `false` and reloading OpenRCT2.
+Mega Park is usually unlocked and shown upon successful completion of all RCT1 (not CF/AA & LL) scenarios, but can be unlocked by setting `scenario_hide_mega_park` in the config file to `false` and reloading OpenRCT2.
+
+### Why do I get a 'It is not recommended to run OpenRCT2 with elevated permissions.' dialog on startup?
+Because you shouldn't be running OpenRCT2 as an administrator (on Windows) or as `root`/with `sudo` (on *nix). OpenRCT2 does not require elevated permissions. If your data files are stored somewhere your user account does not have read rights to, give your account rights or move the files somewhere else. The reason we explicitly warn against doing this is twofold - (1) OpenRCT2 connects to remote servers for multiplayer, and there is a small but non-zero chance that a remote code execution exploit may be discovered, and (2) an upcoming change will add a scripting system, which increases the risk of (1) happening. Running the process as admin dramatically increases the damage a RCE exploit could do.