Quote:
Originally Posted by Rockon
Hm) Thanks!
Then here to you the added and improved transfer (some problems are solved with a hyphenation). But some parts of transfer too long also do not get at line.
...
|
This is the problem that -=hunter=-
reported a while back. I'm working on a fix, partially based on the code he posted. The problem affects more than just the chat messages, however, and I am working on a solution that addresses all aspects of the problem.
Quote:
Originally Posted by hjkwe654
suggest: use a function in offical amxx 'mapchooser' plugin , it called "loadSettings()" (more faster load maps list)
because i put my maps name in files (over 4,000 maps),server loading so slow
|
Are you saying that when you put all 4,000 maps in mapcycle.txt/allmaps.txt, that causes the slowdown, or are you talking about another file?
Quote:
Originally Posted by mimozmi
help me please
I want to extend the time to map in the last round to finish the last round and change the map to the next round
I saw this on a server that uses Deagles' Map Management 3.0
and bottom of the screen is this message:
** Extending time limit to allow players more time to finish the current round **
|
That message automatically shows up if:
- The enforce_timelimit CVAR is set to 0
- The server is running Counter-Strike
- There are at least 2 human players connected to the server
If you are running another mod, the time can still be extended, but that message just doesn't show up.
Quote:
Originally Posted by NeO|GoD|LDR|SturmTiger
everytime I enable this , and think I have it installed correctly , my maps change every 3 minutes like clockwork , you cannot even get in the server fast enough before a vote is enabled , the map changes witha vote up to change to the next map allready in process..something is not right in the code or the default settings , or someone needs to post how to delay the mapvotes for more than the 3 minute stock value...say to 20 minutes or 30 minutes before a vote is enabled.
|
Please post the contents of your plugins.ini, error_*.log (if there is a recent one), the most recent dmaplog*.log, and your server.cfg (take out any lines with a password).
I just re-read every post in this thread starting at page 50, which is around the time I created v3.20, to find any reported problems or feature requests that I had forgotten about. Based on what people have reported, and issues I have seen, I put together the following todo list:
(I removed the list after the release of v3.24 of the plugin. Half of the changes were implemented in that version, and the rest are on the to-do list, visible at the bottom of the first post in that thread.)
If anyone else knows of something I forgot, please let me know. I'm going to work on these issues over the next couple weeks and then hopefully take a break from this plugin.
--
Andy