Page 1 of 1

My feature instagibber doesn't gib spring engine trees

Posted: 09 Feb 2015, 21:41
by Forboding Angel
http://pastebin.com/wqdX2Ke5

Any idea why? Are engine trees considered not to be features, or are they considered to be a significantly different type of feature that Spring.DestroyFeature doesn't cover them?

Halp! This is really annoying. :-(

Edit: Jk gave me some odd explanations about renderers, but I solved it by simply bettering my featuredef replacing thing.

SOmething in spring is broken though, I simply managed to bypass it.

Re: My feature instagibber doesn't gib spring engine trees

Posted: 09 Feb 2015, 22:57
by 8611
Even if these are trivial lines, not mentioning that originally several others made this, putting author='', calling it "My" featureXY and asking for more "halp" without posting any own attempts is annoying.

Re: My feature instagibber doesn't gib spring engine trees

Posted: 10 Feb 2015, 00:22
by Forboding Angel
In this instance,"My" (that is in no way unclear) refers to possession not creation. Don't blame me if you can't read English properly.

Also, it's part of gadget that does a few things, I snipped out ALL of the relevant portions. dealwithit.jpg.

Re: My feature instagibber doesn't gib spring engine trees

Posted: 10 Feb 2015, 00:38
by 8611
"does a few things" = It does excactly 2 things. (None of which was written by you.)
https://github.com/EvolutionRTS/Evoluti ... xes.lua#L5
One could only argue that it is too trivial to have a name or license attached, but that does not make it your "possession" either. Creation is the only thing that is relevant, lol @ possession of digital text where anyone can make a copy with one click...

Regarding "bettering 'my' featuredef replacing thing" it is the same thing again. Maybe you want to read the last thread on that and compare what was written there to https://github.com/EvolutionRTS/Evoluti ... 97b592d62a

Re: My feature instagibber doesn't gib spring engine trees

Posted: 10 Feb 2015, 01:01
by smoth
8611 wrote:"does a few things" = It does excactly 2 things. (None of which was written by you.)
You are back to splitting hairs I see. My laptop, my widgets.. well all my widgets were not written by me but they are in my spring dir and part of a collection which is my collection. It doesn't matter who wrote it.

You seem to think forb is taking ownership when it is a way of speaking.

Re: My feature instagibber doesn't gib spring engine trees

Posted: 10 Feb 2015, 02:00
by Forboding Angel
You can put the douche in another canoe, but in the end you're still stuck with a douchecanoe.

User was warned for this post. Felony 1. (Silentwings)

User was banned - mandatory minimum ban for accumulated warnings in a short period.

Re: My feature instagibber doesn't gib spring engine trees

Posted: 10 Feb 2015, 02:02
by Forboding Angel
8611 wrote:"does a few things" = It does excactly 2 things. (None of which was written by you.)
While many people would agree that “few” means three or more, the actual dictionary definition of “few” is, “not many but more than one.” So, a "few" cannot be one, but it can be as low as two.
Image

Now kindly, gtfo.

Re: My feature instagibber doesn't gib spring engine trees

Posted: 10 Feb 2015, 02:53
by 8611
It is not about whether "a few things" means more than 2 things :roll:
well all my widgets were not written by me
So would you post them and ask "halp please fix my widget?" and expect nobody to be irritated? It is simply good ettiquette to note where something comes from, everybody else does it.
Not just for being not lame but also because it is helpful info for those who might look at the problem.
But worse, it is another thread that shows zero attempt at own solution, otherwise there would be a description of "what I tried", a simplified testcase, or anything. This is just pointing at something and saying "Halp!"

Image

Re: My feature instagibber doesn't gib spring engine trees

Posted: 10 Feb 2015, 03:31
by gajop
Forboding Angel wrote:Are engine trees considered not to be features, or are they considered to be a significantly different type of feature that Spring.DestroyFeature doesn't cover them?
They are different only as far as rendering is concerned (you can't render them using the same Spring functions you would for other features), but they can get Destroy-ed just like any other feature.
Forboding Angel wrote: Edit: Jk gave me some odd explanations about renderers, but I solved it by simply bettering my featuredef replacing thing.

SOmething in spring is broken though, I simply managed to bypass it.
I assume this is solved then. If you have any other difficulties please open a new thread with a specific issue.
Also locking, for obvious reasons.