[TRACKING] Missing and wanted commands

flybywiresim / discord-bot

This is the repository for the FlyByWire Simulations Discord bot

https://flybywiresim.com

GNU Affero General Public License v3.0

17 stars 35 forks source link

[TRACKING] Missing and wanted commands #8

Open benw202 opened 3 years ago

benw202 commented 3 years ago

This is a list of missing and wanted commands for the bot. Please comment with any commands you wish to see added.

[ ] Sticky

Valastiri commented 3 years ago

Currently inop

[ ] - mute command
[ ] - whois command
[ ] - checklist command

-- Wanted --

[ ] - .calibrate command - can discuss in #support-ops

benw202 commented 3 years ago

@Valastiri Thanks, checklist has been added to #7, I will add mute in.

Can you describe whois? Do you have an example of it from before?

frankkopp commented 3 years ago

~~.versions ==> link to https://docs.flybywiresim.com/start/fbw-versions/ (exists - should link to this page)~~

~~.cockpit (or .screenshot) ==> Text explaining how a good screenshot including PFD, ND, FCU and ECAMs looks like to diagnose issues~~

~~.msfs ==> link to Microsoft Flight Simulator Forum~~

.fpmbug ==> "This is a bug in the default Asobo flight plan manager - the team is working on a customFPM which fixes all these bugs and adds much better navigation - for now the workaround is to use DIRECT to the next waypoint again or selected heading. If you can, always enter your expected approach in the MCDU before departing. If this doesn't need to be changed, this will skip the turnaround bug on approach. This issue and others like it will be resolved in cFPM."

NUTTTTTTTT commented 3 years ago

Requested on Discord - .beginnerguide or similar to refer to the docs guide.

frankkopp commented 2 years ago

Request: .fdr

Is it possible that you send us some some files:
https://docs.flybywiresim.com/fbw-a32nx/feature-guides/autopilot-fbw/#work-folder-location

Check in your work folder for fdr files (flight data recorder) for the flight you did. You should recognize the correct one by the filename which is the date of the flight. For a long flight it might been split into several files.

Compress/Zip it and upload it to a sharing site (e.g. https://www.swisstransfer.com/) as these files are likely to be too large for Discord .

This file will allow us to see some more details to understand what happened.

Doesn't have to be exactly this but needs to provide the info.

frankkopp commented 2 years ago

.discontinuity / .disco

https://docs.flybywiresim.com/pilots-corner/beginner-guide/preparing-mcdu/#discontinuity

NathanInnes commented 2 years ago

Sticky still a feature we need? Don't really see the need in it anymore.