Update Item Tracking module to be able to limit gascans etc.?

zerydaa / confogl

Automatically exported from code.google.com/p/confogl

0 stars 0 forks source link

Update Item Tracking module to be able to limit gascans etc.? #120

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

Would be cool if it could also limit:

gascan
fireworkcrate
propanetank
oxygentank

Original issue reported on code.google.com by Dynastic...@googlemail.com on 20 Nov 2010 at 9:33

GoogleCodeExporter commented 8 years ago

Oh, propanetank and oxygentank might sound a bit ridiculous, I am not sure if I 
would even want that... :P (Can't hurt to be able to limit them as well tho.)

My main concern are the gascans (and in the case of c2m5 also fireworkcrates).

I took this picture during a 1v1 for example: 
http://www.s5.directupload.net/images/101129/h4iebh8m.jpg

Original comment by Dynastic...@googlemail.com on 29 Nov 2010 at 2:49

GoogleCodeExporter commented 8 years ago

To me gas cans are part of the level design.  Just like if the physical layout 
is a poor place for a tank (ex. c5m4 billiards room), gas cans can make areas 
harder for tanks.  They are also currently static, and if we were to limit them 
it would add a random element, which would favour the second team since they 
would know ahead of time which gas cans are spawned (made worse by the fact 
that its quite easy to check the static spawns for gas cans).

Original comment by Canada.R...@gmail.com on 29 Nov 2010 at 3:28

GoogleCodeExporter commented 8 years ago

They aren't all static, and I could see the utility of this, but I wouldn't 
have a clue what to set limits to.

I'll consider this low priority 2.2.3

Original comment by prodigysim@gmail.com on 29 Nov 2010 at 4:27

Changed state: Accepted
Added labels: Priority-Low, Type-Enhancement
Removed labels: Priority-Medium, Type-Defect

GoogleCodeExporter commented 8 years ago

Ye it would become more random, but it's kinda the same with molotovs no? They 
are random and you know during the second round where they spawned in the first 
round.
And I would prefer it to be more random, so every match is a little bit more 
different from another.

I'm not sure what I would set the limits to either tho... except 0 for 1v1 and 
-1 for the rest until we found good limits.

Original comment by Dynastic...@googlemail.com on 30 Nov 2010 at 12:09

GoogleCodeExporter commented 8 years ago

Randomness shouldn't be added for the sake of randomness.  The worst enemy of a 
competitive game is random elements, especially when they favour one team over 
the other (in this case the second survivor team) because it can prevent the 
better team from winning.

Original comment by Canada.R...@gmail.com on 30 Nov 2010 at 12:32

GoogleCodeExporter commented 8 years ago

Well, of course I don't want randomness like default boomer horde from 10 to 30 
commons, but this is something different.
But I guess to even all that out with first/second round we would need ABABA 
team order.

Original comment by Dynastic...@googlemail.com on 30 Nov 2010 at 1:00

GoogleCodeExporter commented 8 years ago

You get ABABA working and I'll do this the instant ABABA works!!

Original comment by Canada.R...@gmail.com on 2 Dec 2010 at 12:52

GoogleCodeExporter commented 8 years ago

Haha. :P

I wish I could... guess you haven't forgotten my other issue about it: 
http://code.google.com/p/confogl/issues/detail?id=64

Original comment by Dynastic...@googlemail.com on 2 Dec 2010 at 1:38