Lisias

They are the fuel!! In the most strict sense, we are all NPCs on life. Check the local graveyard, there're lots and lots of reminiscences (dark punk not intended... or perhaps just bit) that the Game (World) didn't ended when they passed away. Or perhaps just failing.

Yep! They are in the project's github page, on the section "Sponsor this Project". https://github.com/net-lisias-ksp/distantobject However... There're some inconveniences while trying to sponsor a Brazilian, the fees are... hummm... inconvenient. (it's the reason I like CurseForge - I can accumulate the points and take them every a year or two, making just one transaction and saving a ton of money in the process)

You know, the idea is not bad - but I would do some calculations the same just for it, and I think I found a dirty trick to get it for free. I don't have the time to try it in the short term (things are somewhat hairy on DayJob©), so I'm reticent to open my big mouth without proper grounds (I had to eat my words recently on MM/L on something about :HAS, I think it's a good idea to try to avoid doing it again! )

But then why not just deinvest the Studio and recoup the money? Like... I'm a taxi driver, and the costs of the car are eating badly the incoming and I want to quit this taxi business. In this situation, how I would recoup most of the money? By selling the car to someone willing to be in this business or by putting it down into a recycler for the money from the recycled materials? It's the reason I think we are missing something important - the only situation in which the second option on my example above would be the best outcome is if the price of the recycled materials after writing the car off outweigh the money you would earn by selling the car to someone. What's only true if the car is really a rotten tomato... Or you had stripped the car of anything valuable and then are going to deduct the price you paid for it from the taxes as losses. I have (had, switched industries) more than 25 years on development on embedded systems, and I had seen THREE Corporate take overs (one of then, absolutely hostile). And I agree, no one shuts down a whole division for poor performance. They do it for money. Once, I saw a division being shutdown after a merge (that hostile one) because there was already another division doing exactly the same job (bought on a previous merge), and this division were performing poorly when compared to that one, so they scrapped this division and kept the other. In other situation, the buyer literally paid 1USD for the whole Company (the seller was desperate to get rid of the expenses and cut the losses). The buyer stripped the dead body from anything of value, and then terminated it, because this would be more profitable in the short run than sanitizing the Company and make it profitable again (and they could do it, but they had no interest on the Brand, that market was collapsing). And there's that Nokia stunt, with Stephen Elop in the helm - Microsoft bought Nokia pretty cheap and literally wrote it off after some time, deducting the money invested from their taxes as losses.

Exactly. There's something else happening on the Industry. Making good, profitable games 'will no longer keep you safe': industry expresses fury and heartbreak over closure of Hi-Fi Rush and Prey studios https://www.pcgamer.com/gaming-industry/making-good-profitable-games-will-no-longer-keep-you-safe-games-industry-expresses-fury-and-heartbreak-over-closure-of-hi-fi-rush-and-prey-studios/ Good, profitable Studios are being shutdown the same - they aren't even considering selling them (someone would probably buy them!), they are shutting down everything and the kitchen's sink. Obviously, this is not random, there's some methodology on this - but I just can't understand it right now.

Porco Rosso meets Crymson Skyes - and beer. How I would not love this one? The Brew Barons. A very nice (but somewhat short) game about flying biplanes, fighting Zeppelins (and warships) while trying to run a brew business in competition with a nasty monopoly. Sounds like an euphemism for games, uh? As usual, an indie game. https://www.lifetapstudios.com/the-brew-barons/

I heard of people managing to get the refund on the 2nd or 3rd try. Additionally... Steam don't want to lose (yet more) money themselves, if the studio is closed and the respective wallet is near depleted, Steam would have to pay the refund from their own pockets. What is not exactly unfair, but still highly undesirable (for them). I respect Steam a lot for the many, many good things they are doing for gaming (almost as much as I respect GoG) - but some line must be drawn somewhere. I really don't think KSP2 was a scam, but it ended up working as one and someone must be accountable, or the very principles in which our Economy works may be jeopardized.

This is not a problem (it's already implemented), except by being too fast. There's an issue about it here: https://github.com/net-lisias-ksp/DistantObject/issues/26 This #26 is on the backburning, because I think there's things more important on queue, but perhaps I should prioritize it as a low hanging fruit. Considered that, but on a "thought experiment", it would create some visually awkward situations: The sky not dimming while orbiting/passing by big asteriods (that are "crafts" in the game); and/or The sky dimming while orbiting/passing by small asteroids (ditto) Additionally, using something that would be tied to the Sun itself would allow the thing to be easily "ported" to Kopernicus.

Yep, it's a known issue: https://github.com/net-lisias-ksp/DistantObject/issues/31 I tried some stunts, but got unhappy with the results. On one, I did too many raycasts trying to figure out how much part of the Sun is covered by something, on another I tried to calculate projections of the Sun over whatever is between me and the Sun and see how much of it would be covered. These stunts kinda worked, but I found them clumsy or too computing intensive to be used on the Unity's Update. I'm currently looking for a shortcut - I'm betting something in the game already calculated something that could be reused, saving me the trouble to do it again.

Yes, they did. But you have 2 weeks for the refund, what's good enough for bombing the game due a crisis. In the mean time, your review is there. Besides, counting or not, seeing a lot of reviews with the label "Refunded" being marked as "useful" sends a hell of a message, believe me. Anyway, there's the financial burden of the refunding - and this is the nastier part of the deal, not the bombing itself. Someone lose a bit of money (besides the refunded amount) when this happens. There's a fee applied when you buy it, and there's a fee applied at chargeback - someone is going to pay for the party. The old and faithful 1USD bill is the best and most effective voting ballot still in existence. === == = POST EDIT = == === So I did a research on the Refund thingy, and I found that no, reviews from people that refunded the game are still being counted. Like this one. Some other criteria must be in effect nowadays.

I'm following the backslash on Steam. Dude... I'm taking some popcorns and waiting people starting to buy the game just to lay a terrible review and then ask for refund, because it's literally the only thing people didn't did yet there.

Fool me once, shame on you. Fool me twice, shame on me. Fool me thrice, fool. Your truly, KSP Development Teams (both)

Mi-10 Flying Crane. A very, very, very unexpected looking helicopter... You don't board this thing. You climb it...

The Refunding resource is defined to be invisible, nontransferable, untweakble and undrainable: RESOURCE_DEFINITION { name = RefundingForKSP111x displayName = Refunding ... flowMode = NO_FLOW transfer = NONE isTweakable = false isVisible = false RESOURCE_DRAIN_DEFINITION { isDrainable = false showDrainFX = false } } It's even more restricted than ElectricCharge: RESOURCE_DEFINITION { name = ElectricCharge ... flowMode = STAGE_PRIORITY_FLOW transfer = PUMP isTweakable = true } So I think this is something to be handled on StageRecovery. I will check SR source code and see what can be done. The fact is that this will be useful to any other add'on that wants to add resources that should be hidden from the user. https://github.com/net-lisias-ksp/KSP-Recall/issues/79

If they were working full time in the project, yes. If they were working on other projects too, well... Not exactly. Well, they are trying to kill it, no doubt. I think it may be a good idea, as long the corporation understands the development model - instead of (ab)using it as a marketing tool. The problem here wasn't a corporation using EA to develop the game. The problem is the corporation being a freeloader, (ab)using it for free workmanship and free marketing. EA is being (ab)used by corporations to save money, not to develop a better game. I don't doubt they would do it, but I don't think it's the case this time. I understand that most of people around here are not fond of the C-Suite (neither do I), but most of them are not stupid idiots as we like to think about them. They are dumbasses on STEM, no doubt, but they have other skills - and they know how to use these other skills. One of these skills is the Sense of Opportunity. They are excellent opportunists (not necessarily a bad thing). They are risk takers, and so, they know how to calculate risks. They don't win all the time, but they know how to lose and still be profitable (believe me, they do it). So, unless P.D. had an team of incredibly inexperienced and/or completely incompetent C-Suit people on the helm, they would not try to purposely scam people on E.A. like you are suggesting. The risks were too high. Unless they would had nothing to lose... There're people on Forum suggesting that the TTI's C-Suit cornered P.D. demanding some financial results or the axe would start to fall on some heads/projects. I think this hypothesis is, by far, one of the most probable (remember the upper management of P.D. being fired earlier this year?). So P.D.'s C-Suit people, feeling the knife in their throats, decided to risk it all in a bold move - let's publish everything no matter the state and see if we get lucky and one of them sticks. What could they possibly lose? "We are already losing our jobs: worst case scenario, we lose our jobs the same - the money invested on all these years of development weren't ours at first place, why we would bother wasting it?" So, TL;DR: I don't think TTI or even PD did EA to scam people and try to recoup some money - the risks were too high, the earnings were too low. So they did EA in "good" faith, or PD (and not TTI) did EA in a desperate attempt to save their necks, disregarding any consequences.

You know, the BDA guys would like the concept. Instead of "Catch the Flag", a new mode called "Catch the Fuel - Snacks for free". Team Fortress my <piiiiii>, Team Station, baby!!!!

I think it's more like to fire up the Let's Encrypt daemon. SpaceDock uses Let's Encrypt, and the current cert were issued Tue, 06 Feb 2024 13:40:08 GMT. Exacts 3 months ago. I'm betting that whatever he had to do to survive the klang in the klong, he had to update something and/or perhaps reboot the server and forgot to fire the daemon.

We need to face the harsh true: we are the oldies nowadays. Our kids will not like the same things we liked just because "it's old guys stuff". People nowadays have different sense of aesthetics, different objectives in life, different preferences on gaming. KSP2 tried to lure these kids into a game style that, essentially, marked the last 15 years in a way Casablanca marked the 40s and Planet of the Apes marked the 70s, and at the same time wanted to keep the old guys around. Frankly, it failed in both fronts. Going back to movies, KSP2 is more like Ghostbusters 2016, a far cry from Ghostbusters Afterlife.

ANNOUNCE KSP Recall 0.5.0.0 Rollbacks the PAW changes due an absolutely unexpected, unexplainable and crappy KSP behaviour that only manifested itself on KSP 1.12.x I don't have the slightest clue about what happened yet. Closes issues: #77 Refunding is not working on 1.12.x!!! The krapstorm was detected by fellow Kerbonaut @by_HOY_ (thank you very much, dude!). I just don't understand how in hell 0.4.0.3 did this breakage on KSP 1.12.x (and only on 1.12.x, the damned thing worked on the previous ones!). In a way or another, I rolled back the codebase to 0.4.0.2, backported some small fixes and I'm launching 0.5.0.0 to stop the hemorrhage. I will come back to this problem in the weekend (RealLife™ and DayJob© are biting hard): https://github.com/net-lisias-ksp/KSP-Recall/issues/78 — — — — — This Release will be published using the following Schedule: GitHub, reaching manual installers and users of KSP-AVC first. Right Now. CurseForge. Right Now. SpaceDock. Right Now.

It's odd. StealBackMyFunds is working, and it uses essentially the same mechanisms. I managed to make the damned Refunding to be loaded by renaming it, besides it didn't recovered any funds. It's like the name "Refunding" became cursed somehow. DayJob© is calling now, but I will go back to this issue ASAP. I think I need to do some regression tests using previous KSP-Recall releases to see what I find. === == = POST EDIT = == === KSP Recall 0.3.0.12 is working as expected. So this is something related to a change on newer KSP-Recall that worked fine on KSP 1.11.2 and olders, but some internal change on KSP 1.12.0 ended up screwing it. The fault of Schrödinger: it's not my fault, but it's my fault. --- -- - post post eidt - -- --- This mess started at 0.4.0.3. @by_HOY_, roll back to 0.4.0.2 for a temporary workaround. Until the end of the day, I will publish something that will solve this issue on a way or another. -------- Fixed on KSP-Recall 0.5.0.0 .

You are right, I confirm the problem! There's something wrong on KSP-Recall, as it appears. Working on it: https://github.com/TweakScale/TweakScale/issues/329 === == = POST EDIT = == === The thing is working on previous KSPs. https://github.com/TweakScale/TweakScale/issues/329#issuecomment-2095104416 I'm trying to figure out what changed, when and how. === == = POST POST EDIT = == === It doesn't makes sense. Refunding is not being loaded into a new part, and without it the KSP 1.12.x bug relate to ICostModifier is not handled, screwing TweakScale. So I moved the issue to there: https://github.com/net-lisias-ksp/KSP-Recall/issues/77 @by_HOY_, do you know exactly when this started to happening? I'm kinda puzzled, because I have remembrances of testing this on the 1.12 KSP series... (besides not impossible I'm wrong - but, dude...)

I said before, and I will say again - there's more than one plausible explanation. For example, I will (again) suggest a quick research about how Stephen Elop conducted Nokia before Microsoft bought them.

To minimize the risks of class actions, probably. They made a huge lot of promises while selling the game (being on E.A. or not, it's irrelevant - the Bureau of Consumer Protection have the final word about the subject in USA - and I'm kindly ignoring pertinent foreign legislation). No matter what they say to you, EULAs are not licenses, are contracts and as any contract, can be questioned on a Court of Law - even with the mediator clause in effect, a situation that will demand to question that clause first and, if won, then proceed with the suit. That said, I'm not saying this is class action material. I'm saying that a class action is possible (if it will stick or not, dunno), and if they are really going to bury the franchise on a landfill (Atari style), then it makes sense to push hard to deliver all that promises the less worst possible (as long it costs them less than a hypothetical class action).

Did you tried the | operator inside the :HAS? It's supposed to be the OR.

I'm frequenting this thread too much! Ozzy Osbourne, No More Tears. (I love that bass) Cheers!