WillyTheGoat

As a stakeholder since BATC's inception and a designated supporter, I have consistently valued the organization's commitment to transparency and technical expertise, which initially fostered strong confidence in its offerings. However, recent developments suggest a discernible shift in operational efficacy, in my assessment. Historically, BATC operated with a core team of four developers (including three software engineers and one sound engineer), as communicated via official Discord channels during its formative phase. Leadership was spearheaded by an individual known as "Captain," while the traffic injection system—acknowledged as a foundational innovation—was engineered by "Whakamolenz," also credited as the architect of FSLTL. Currently, Captain's presence on Discord has markedly diminished, with no substantive community interaction recorded for several months. This decline in engagement correlates with observable delays, and potentially a cessation of progress, in core engine development—a domain primarily overseen by Captain. This hiatus has been attributed by representatives to shifting personal circumstances. While another developer has resumed community engagement following an absence, operational challenges persist. A significant backlog of unresolved issues has accumulated, including but not limited to: erroneous vector assignments, procedural incompatibilities at specific airports, and malfunctioning parking systems. Compounding this concern is the developer team's recent need requesting new issue submissions following each patch release. This policy lacks effectiveness and consistency, as stakeholders receive no indication of whether patches actually address previously reported defects. Consequently, reports frequently remain unacknowledged despite assurances that all submissions are reviewed. The community commendably attempts to mitigate non-critical issues (e.g., user errors or feature misunderstandings), yet core technical deficiencies persist unaddressed. This operational posture contrasts unfavorably with BATC's primary competitor, which demonstrates prompt issue acknowledgment, systematic resolution tracking, and explicit patch documentation linked to specific reports. The disparity in responsiveness is substantial. While differing monetization models may contribute, it is notable that BATC itself previously maintained higher levels of engagement than observed presently. Collectively, these circumstances give cause for concern regarding BATC's current strategic direction and prioritization of stakeholder experience.