Author Topic: New Airplane changes  (Read 411 times)

patson

  • Administrator
  • Hero Member
  • *****
  • Posts: 915
    • View Profile
Re: New Airplane changes
« on: December 06, 2019, 02:10:38 pm »
I'm down for something more drastic. Remove auto-renewal and force us to manually plan when to order planes for replacement. As for refurbish button - it should be like a cabin renovation, plane age stays the same, just a boost of pax satisfaction and make it cheaper though. Perhaps if maintenance is introduced we could have the plane condition affecting delays/cancellation separate from cabin refurbish. Maintenance can be monthly fee, perhaps depending on a provider you pick and depending on type of plane - more expensive for a bigger plane. This should restore balance should you decide to make fuel efficieny accurate.
I would also love to see different seating options - more dense, more luxurious. SQ expenses will need to go down for this change to compensate for loss of cabin density. All this will allow for more types of game strategies possible and could truly be rewarding to more active players. I believe it will also attract new players and make them stay.

Thanks GR! <3

I cannot remove auto-renewal tho...cause honestly that would turn into a micro-management hell....i thought u own the most airplanes....wouldn't you hate to replace them manually??? ;)

As for separating cabin refurbish vs actual airplane condition and different types of seating, tweaks to airplane  - I think other games are doing that, I agree those are more realistic, but what really kinda stop me is:
I don't really have the time to write all those extra code lol.

Another concern for me tho, is when i first designed the game, i deliberately ruled those out very early in the development stage - i see other games ARE indeed doing that - customization of the airplane and stuff - I tried those myself, it was fun maybe for the first few mins, but then later on i found it's either "chores" or something that I just ignore cause it's kinda useless. Therefore I kinda abstract those details away and just put it in the big "SQ" bucket and also the class configuration :)

I do agree that it  might allow some meaningful gameplay with customization. But it's very hard to execute it right to avoid the "chore" or "useless" part. At least to me, other games have failed to make it meaningful in long run, and i just wanted to avoid that pitfall by not going into that at all lol . And again, coding those extra details in could be very challenging - and surely with some value added but not enough (at least to me...sorry im very subjective on the game design sometimes ;) ) to justify the dev cost.