|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Vote Love hate new inventory.[message #233440]
|
Thu, 17 September 2009 23:41 
|
|
| Headrock |
 |
Messages:1757
Registered:March 2006 Location: Jerusalem |
|
|
Quote:
How is it a misconception? You just said that the NIV is built on a version that uses the SCC. If you are uncomfortable with that than why aren't you helping me to try to rectify this situation. If you aren't uncomfortable with it than what it the problem?
As stated many times before, I completely lack the expertise required to understand how SCC works, why it causes problems, let alone how to fix it. Otherwise I would've fixed it already, if for no other reason than to kill this silly discussion once and for all.
Quote:Do you want me to go around adding a disclaimer that Headrock and this or that guy weren't responsible or what? You already complained about me not clarifying the niv from scc even though they are components of the same project so I go out of my way to add extra words to every post where I talk about this bullshit and now what? Do you want me to pretend the scc is not a part of the 1.13?
It's not a question of responsibility. My qualm is about you taking a general issue and making it very specific - too specific. And in many ways, your choice has possibly made it more difficult to get what you wanted (I.E. SCC fixed). You insist on drawing parallels between SCC and NIV, and thusly implying that NIV is at fault (heck, look at the name of this thread vs. the discussion we're having), and in doing so you are causing confusion between two completely separate subjects. As you know from my work, I strive to make JA2 transparent and better understood. Having two unrelated concepts being constantly strung together is making things harder to understand for people who do not know the background. You yourself are making no effort to undo the confusion between them, so naturally I have to.
Quote:Already fix his oversight with OWNERSHIP item in OBJECTTYPE class, and one other copy/paste oversight, so maybe this could call some kind of improvement.
Interesting. Can you tell us what the oversight was?
Quote:I have feeling all moders community is pissed off because someone add new stuff but
Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
| Re: Vote Love hate new inventory.[message #233482]
|
Fri, 18 September 2009 19:34 
|
|
Khor1255 |
 |
Messages:1815
Registered:August 2003 Location: Pleasantville, NJ |
|
|
StarwalkerKhor1255I also didn't say that the niv needed the scc only that it was built on top of it.
Which is also not true, NIV was well on its way and already working when the SCC was made.
EDIT: If you insist on using the phrase "was built on", then SCC was built on NIV, because NIV was in (but not released) when SCC was added.
Well, la de dah. No, I'll just stick to using terminology which is commonly understood. Built on top of means something that is built along with something else. I'm not going to write a paragraph disclaimer that only really amounts to semantic literary masturbation to appease the folks who ruined the 1.13 for modding.
But please, keep insisting on this stupid bullshit. You aren't going to cloud the point for me at least.
EDIT
Oh, besides you already said that certain things in the niv would be impeded or different were it not also using the scc so - in this case at least - I'd say built on top of is not only acceptable terminology but THE ONLY accurate way to describe what is going on here. You already used this point as justification for why you have to leave shitty code in the 1.13 and now....what?
Man, this would be funny if it wasn't the decline of a once great project.
[Updated on: Fri, 18 September 2009 19:40] by Moderator Report message to a moderator
|
Sergeant Major
|
|
|
|
|
|
| Re: Vote Love hate new inventory.[message #233486]
|
Fri, 18 September 2009 20:37 
|
|
Khor1255 |
 |
Messages:1815
Registered:August 2003 Location: Pleasantville, NJ |
|
|
I already said I was going to try it. A little opened communication would have gone a long way last year. Today we have over a thousand new builds on top of bullshit code. Of course it is possible to straighten it out, but from a mod makers standpoint this situation should never have been allowed to go on for so long. Early on when we warned that this stuff should not be merged with the main build would have been the best time to straighten this out.
What is wrong with having an alternate version like HAM or whatever to use until modders can give it the thorough test needed to make sure it is not only going to have regular gameplay problems but is not going to break mods built on top of it? I'm sure with as popular and interesting as the niv is everyone (including me) would have made a separate install and merged our work with it. So what possible problem would there have been with keeping a reliable version on hand until enough time had elapsed for EVERYONE working on the project to give it at least the once over?
But that is not the worst of it. Almost immediately after the 2085 a virtual flood of posts came from various modders complaining about new and gamebreaking glitches we never experienced before. Instead of considering these concerns, the current team instead went on a pr campaign to smear any concerns we had while promoting a project that no longer was even as easy to mod as vanilla.
So as soon as the issue arises again - surprise - in comes a moderator to lock down the thread. Isn't there a gulag somewhere you should be moderating? I hope you understand the spirit of that last comment.
[Updated on: Fri, 18 September 2009 20:37] by Moderator Report message to a moderator
|
Sergeant Major
|
|
|
|
|
|