No feature yet has been poorly added.Sly wrote:Assumed it was just another poorly added feature
Scav Issues
Moderators: GSH, VSMIT, Red Devil, Commando
Re: Scav Issues
Re: Scav Issues
And yet no examples. And then you will probably come up with something half baked or that is also a bug.Sly wrote:wrong
If you try to claim DX9 in TA5, that was why it was an alpha not a beta, if you try to claim the networking in PB6, that wasn't a feature, that was a base code change, which is also what DX9 was.
A feature would be something new, and as you refuse to actually do any work I don't see how you could actually know of any issues with them in the first place.
Insights into the bug of this topic subject would be good though.
- MrTwosheds
- Recycler
- Posts: 3059
- Joined: Sat Feb 19, 2011 8:37 am
- Location: Outer Space
- Contact:
Re: Scav Issues
Unless people have some experience of complex software development, they cannot really be expected to understand how illogical its response's to minor alterations can sometimes appear to be.
If you were replacing the spark plugs in your car, you would be very surprised to find that this caused the seatbelts to malfunction.
That would be irrational, because there is no functional physical connection between the two. Software however is not physical, tweaking something at one end can affect apparently unconnected functions elsewhere in the program. The effect will be logical but may well be quite unexpected. Designing software well helps to avoid this sort of thing, but with BZ2 now we are not designing software, but attempting to remould something that was a bit slung together in the first place. So weird **** happens.
Now I spent 12 tears testing software that operates physical machines, we were often in the same situation, a piece of software originally designed to just perform a specific function in a specific way on a specific piece of hardware, would then later on need to be altered to run on a different machine in different ways...My job was "Head unfolder of weird voodoo **** happening now", or software tester as it was formally known. A very much unappreciated role by just about everyone except the software writers, who fully understood that they needed a bunch of deranged fools to diagnose the true functionality of their coding out in the real world operation of the physical machines.
We had our trolls too, allot of the office worker types just didn't understand why we got to sit around allot looking mystified at a bunch of half dismantled machines. We had a code of silence too we were not to discuss details of what we did with anyone outside the department! there were just too many Politico's from other depts hunting for poo to throw at the software dev team. The stuff we found made perfect weapons for them to attack us with.
This is why people not in the dev team here don't know what's really going on at all and have to resort to making up arguments about things they don't know much about.
If you were replacing the spark plugs in your car, you would be very surprised to find that this caused the seatbelts to malfunction.
That would be irrational, because there is no functional physical connection between the two. Software however is not physical, tweaking something at one end can affect apparently unconnected functions elsewhere in the program. The effect will be logical but may well be quite unexpected. Designing software well helps to avoid this sort of thing, but with BZ2 now we are not designing software, but attempting to remould something that was a bit slung together in the first place. So weird **** happens.

Now I spent 12 tears testing software that operates physical machines, we were often in the same situation, a piece of software originally designed to just perform a specific function in a specific way on a specific piece of hardware, would then later on need to be altered to run on a different machine in different ways...My job was "Head unfolder of weird voodoo **** happening now", or software tester as it was formally known. A very much unappreciated role by just about everyone except the software writers, who fully understood that they needed a bunch of deranged fools to diagnose the true functionality of their coding out in the real world operation of the physical machines.
We had our trolls too, allot of the office worker types just didn't understand why we got to sit around allot looking mystified at a bunch of half dismantled machines. We had a code of silence too we were not to discuss details of what we did with anyone outside the department! there were just too many Politico's from other depts hunting for poo to throw at the software dev team. The stuff we found made perfect weapons for them to attack us with.
This is why people not in the dev team here don't know what's really going on at all and have to resort to making up arguments about things they don't know much about.
Re: Scav Issues
It works that way in every aspect of life, just open your eyes and see how people judge what they do not know.
I've worked in the steelindustrie, simple things like bending steel can give (fairly) unexpected results, sometimes it tears, sometimes it gets an other kind of plastic deformation. Latelly I work in logistics, again the same aplies. When something isnt there in time there is always someone saying 'but its just a matter of leaving in time'.
People hear 1 word, think they know 3, but fail to realise it actually is over 20 words.
And the funny thing is, we all do it
I've worked in the steelindustrie, simple things like bending steel can give (fairly) unexpected results, sometimes it tears, sometimes it gets an other kind of plastic deformation. Latelly I work in logistics, again the same aplies. When something isnt there in time there is always someone saying 'but its just a matter of leaving in time'.
People hear 1 word, think they know 3, but fail to realise it actually is over 20 words.
And the funny thing is, we all do it

Re: Scav Issues
Its definitely another thing (besides the hovering physics) that was "fixed" to the worse.
Re: Scav Issues
How many times do we need to say it's a bug, not a fix? Most likely caused by a completely unrelated change to the code?
Re: Scav Issues
One of the worst features you guys added was making rats' heads spin slower than dirt. They are completely useless. Respawn height was off the charts in the beginning (this was actually fixed, proving that your statement about every feature is erroneous). Added a recycler protection time (which every strat player will agree is never used and is completely useless). Added an anti-griefer feature for MPI's (that's like Counter Strike adding an option that teammates won't be affected by their own teams flashbangs because so many people grief using that method). Not that this feature even stopped the griefing; had we wanted to, we could have easily continued it. People pass out thug recs on every MPI and its so easy to tell someone that Ctrl + M gives a scrap boost.
Re: Scav Issues
Why you think you can waltz back in here and demand things after a stunt like that shows you're still a griefer. And an arrogant fool.Not that this feature even stopped the griefing; had we wanted to, we could have easily continued it.
Topic over.
Sly - once again, I encourage you to find somewhere else to post until you show some remorse for your actions. Clear?
-- GSH