![]() Play Pink With Twin Sails 19.8€ for the entire bundle Ghostbusters: The Video Game Remastered 0.7€ Mind-Bending Masterpieces 15€ for the entire bundleįebruary 2024 Humble Choice 8.5€ for the entire bundleĮxceptional Indie Allies 10.7 € for the entire bundle IGN Fan Fest '24 12.5€ for the entire bundleĭestiny 2: The Story So Far 19.5€ for tier 3ĭestiny 2: Bungie 30th Anniversary Pack (DLC) The Creative Sandbox 19.5€ for the entire bundle Games Done Quick - Frost Fatales 2024 10.4€ for the entire bundle Im buying the following games as steam keys only. IF I DONT REPLY OR ACCEPT YOUR INVITE IM NOT INTERESTED. If you wanna trade post a comment and add me on steam. Sometimes we'll try to add stuff like this in a earlier, in a temporary fashion, via putting it behind somewhat aggressively-priced/timed research - at least that way the longer term implementation is perceived as not being a "difficulty" adjustment in an undesirable way, though still not the ideal.THERE IS AN IMPERSONATOR ALWAYS CHECK WHO YOU TRADE WITH I WILL NEVER COME INTO YOUR THREAD AND ASK FOR A TRADE OR RANDOMLY ADD YOU I ALWAYS ASK PEOPLE TO ADD ME SO BE CAREFUL It just commonly comes off as though we're making the game more difficult or removing features, even if we had just been trying to get something to you sooner until we were able to really make use of it the way we intended to. We have some plans for it though but we've found that it's usually a much easier 'sell' if we go straight towards the plan than it is to do something easy/freebie in the interim, and then 'take it away' later when we go to add the intended system. It supports all timeslots for each requirement already, we just don't have it offering anything in EAM right now. The UI itself, and the code backing it, is already setup to handle requiring a given flight to have its "arrival" and/or "departure" be in any of the timeslots (or "Any", as is currently the case for the departure slot requirement on all flights). It'd be pretty easy to add and the hesitation is really just in the "what" we want to do with it that's pretty much known too, we just haven't had a chance to do so quite yet. Occam's Razor, though, would suggest that it's just a very low-priority and simple "switch throw" item that's being pushed to the back of the queue because it has a relatively minor impact on gameplay. ![]() That then means ripping out code that works and replacing it wholesale which is a big headache indeed.Ī third possibility is that maintenance is defaulted to occur during the EAM period, and that may be causing some kind of conflict. Adding those could produce all kinds of disruptions in the flight offerings, so it could be a substantial amount of tracing and tweaking to get the distribution right since everything is modeled rather than hard-coded, the schedule modeler may not be able to handle weighted variables too well. On the other hand, if they're trying to weight the schedule to put more demand on daylight hours and less on red-eye flights, then it might be held up because the weighting variables were never part of the code. Tracing down synergistic bugs like that is an enormous pain, especially when there isn't a clear cause. However, based on personal experience, I suspect there's either a conflict creeping up such that when EAM is enabled airline satisfaction collapses or available scheduling suddenly dries up. Without seeing SA's actual code, it's hard to say for sure. But if they wanted to weight the flight time categories so that EAM receives lighter demand on average, that might run into some difficulties. To just add the EAM category such that it functions like all the rest, it'd be pretty straightforward assuming there isn't some conflict that's keeping it out. It depends on how they want to implement them, really.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |