Dimitris
Posts: 13282
Joined: 7/31/2005
Status: offline
|
quote:
ORIGINAL: peterc100248
"Maybe just add a message that the weapon won't fire if you don't own the DLC. I can see it easily becoming a major problem if scenario authors who have the DLC start to release scenarios with these weapons in it and not releasing a different version without those weapons. With the current "lock out" feature that peter is talking about, this might create a large divide in the C:MANO community in terms of scenario authors and community testers."
You didn't address this.
I did. See above. Blocking a player mid-scenario is bad. Axe-crazy bad. Blocking the scenario at load is not ideal, but a much lesser evil.
Another solution has been suggested to us, by a rational customer, and we're looking into its feasibility.
quote:
"I want to be clear here. I'm not concerned that the laser/AGS gun rounds are not usable. I'm concerned that scenarios created prior to 936.2 that happen to have whatever now triggers the "unloadable" feature (or any feature yet to be discovered), or new scenarios created under 936.2 without the upgrade that trigger the trap, are effectively rendered unusable if saved.
As things stand, that is a divergent path. Without seeing your code, I would think it can be easily corrected with a simple "if then else" qualifier for those features that only come into play with the upgrade, but that is a guess."
The eternal "it's a simple fix" assumption looking from the outside. This also skirts the question of why a scen author would add non-working weapons in a platform in the first place.
quote:
You didn't address this, except to say that the answer is to have TWO iterations of CMANO running. Are you going to instruct the entire installed user base to do that?
Nope, just the ones who do pointless stuff like putting non-working lasers on ships.
quote:
Look, I understand completely what you guys are doing. You have been doing an excellent job. I think you need to understand that once you start charging money for your product, you are really no different than any other commercial enterprise. I have no issue with you doing that, but the relationship does change - like it or not.
Indeed. Apparently we also have to deal with customers whose default-mode reaction to a change is "you're screwing us". Thankfully a very small percentage of our user pool.
quote:
I'm not sure what you would say if you owned a business, purchased software to do accounting for that business, and suddenly, after an update, the software crashed every time you tried to load your payroll. Then you get a little pop-up note saying if you'll just buy an upgrade, you can get the payroll feature back with a few improvements. Or you, can just "downgrade" and have the payroll feature back, complete with bugs, but "we won't support the version you payed for." Meanwhile, all the work you put into your payroll is useless.
Fallacious comparison. Your example's payroll software worked correctly before the upgrade and stopped working after it. The SSF laser that you added on the ship was not working before, and is not working after the update either. What has changed is that now the blocking check happens earlier (at scen load) rather than mid-play. I understand how this can irritate scen authors who put non-working lasers on ships, but it protects players from the mistake of these same authors.
quote:
Looking at the qualifications Matrix prefers of future employees, it seems there is an understanding of how important it is to have a good relationship with their customer base:
http://www.matrixgames.com/news/2143/New.position.open.at.Matrix.Games.LLC
Indeed. Thank God we have an excellent working relationship with every single one of our pro clients. It probably helps that their default reaction to a functionality change that creates an issue to them is not to publicly accuse us of bait-and-switching them. I can see how that would raise bumps on our cooperation.
quote:
"Hostage Ware" is not a personal insult.
It's so cute when you seriously claim that.
quote:
It is a common phrase in the computer industry and is directed at the code one generates that, knowingly or unknowingly, does what you may not have intended it to.
That's the definition of a bug. "Hostage ware" is another thing entirely. You're not the only one with decades in the software trade.
quote:
If you took it personally, I apologize to you. That doesn't change my opinion of the little "feature trap". Even had you written the code, "Hostage Ware" is not directed at a person. I spent 25 years developing systems and software for the defense of the free world. Had my customers informed me I had written "Hostage Ware", I wouldn't be waiting on an apology. I would have been trying to figure out what went wrong, and how I could smooth ruffled feathers.
Your sorta-apology is sorta-accepted.
Moving on.
< Message edited by Sunburn -- 4/19/2017 9:05:27 AM >
_____________________________
|
Printable Version
936.2 Hostage Ware? - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread