nikotine40 / confogl

Automatically exported from code.google.com/p/confogl
0 stars 0 forks source link

No horde after boom (YouTube link provided) #136

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.
2.
3.

What is the expected result? What is happening instead?
A horde after a boomer lands is the expected result, no horde showing up is 
what happened.

What version of confogl are you using?
2.2.2 + fresh

On what operating system is the server running?
No idea.

What version of sourcemod and metamod are you using?
The latest.

Do you have any logs about the issue? Setting confogl_debug "1" is
reccomended.
No.

Please provide any additional information below.
http://www.youtube.com/watch?v=2t6kaUkC_t0

Original issue reported on code.google.com by i...@j-sanx.nl on 9 Mar 2011 at 5:00

GoogleCodeExporter commented 8 years ago
So this is going to be completely ignored? Great!

Original comment by J.San...@gmail.com on 13 Mar 2011 at 2:39

GoogleCodeExporter commented 8 years ago
Please provide:

Operating system, actual SM/MM version, and try to reproduce with confogl_Debug 
1.

Also note that any number of server-side misconfigurations could cause this 
behavior. Please ensure that your server is configured properly, and that you 
trust the admins running the server you were playing on.

With the information you provided there's not a whole lot we can infer. Please 
fill out the bug report fields completely.

Original comment by prodigysim@gmail.com on 13 Mar 2011 at 5:10

GoogleCodeExporter commented 8 years ago
It is also completely possible that this is a rare bug that is part of L4D2 
itself and not related to Confogl at all.  With no method to reproduce it and 
very little information, we can't even tell if this is something we can do 
anything about.

If I planned on ignoring this issue report, I would have set the status to 
WontFix to clear the issue page instead of leaving it as new.  It is still 
marked new because Accepted implies that we have determined that it is 
something we should be fixing which we can't determine.

Original comment by Canada.R...@gmail.com on 16 Mar 2011 at 8:12

GoogleCodeExporter commented 8 years ago
I had this problem.. it happened when I sent the server to the 1v1 config then 
straight to a 4v4 config.  I bet they used the 1v1 config first and the setting 
for commons transferred to the 4v4 config

Original comment by msouza8...@gmail.com on 13 Apr 2011 at 6:00

GoogleCodeExporter commented 8 years ago
@mrsouz

That wouldn't explain it. You can't sm_forcematch to a different config while a 
config is already loaded in the current confogl version, you first have to 
sm_resetmatch which resets all 1v1 cvars.

And even if, the 1v1 config touches the horde size, but it only lowers the 
amount of commons, it does not remove them.

Original comment by Dynastic...@googlemail.com on 14 Apr 2011 at 5:04

GoogleCodeExporter commented 8 years ago
You can do it with new builds if you enable confogl_match_allowcfgchange 1.  
But it literally just does sm_resetmatch; sm_forcematch <newconfig> so that 
wouldn't be a problem.

And 1v1 still has hordes so even if 4v4 was using the 1v1 common settings, you 
would still get common, just a much smaller number.

Original comment by Canada.R...@gmail.com on 14 Apr 2011 at 6:18

GoogleCodeExporter commented 8 years ago
Not reproducible, probably no Confogl problem either, no further information 
provided - invalid.

Original comment by TheDonSanchez on 20 Nov 2011 at 7:10