B.Fatih KOZ

Nice idea 🥇

Those fields are not designed to hold decimals, they are technically integers. Also SimBrief API wants them as integers, specially the passenger and baggage weights should be integers, also they...

 Technically even if you try to enter 185.01 here or 185.99, they will be treated as 185 as you described as a bug (but it is not) :)

What will be the benefit of that change? Those fields follow documents and backend works fine (according to documentation)... My personal opinion; No, it will make no difference. Either with...

pax weight and (per pax) baggage weight needs to be integers rest can be floats (for precise conversions). And we do not have problems regarding weights and sending proper data...

> I think this would avoid confusion. I spent some time trying to figure out why I was having weights discrepancies in all my flights until I got here. If...

"Exclude flights already flown" part is kind of non schedule logic, I mean not realistic considering "flight schedule" displaying. (Can be done, not impossible but how do you want to...

It is not just server load, it is a complex logic. Imagine you have 10 flights between MAD - AMS replicating a real airline, all with different departure times, different...

Maybe a small map in the edit page would be ok, but do we really need it ? A slight change on edit page will be much better, like putting...

No, they can not accept/reject from frontend if this is what you are saying. There was a request for the map at admin side, maybe 3-4 years ago, to ease...