AlliedModders - Development Roundup, We need you!

AlliedModders (https://forums.alliedmods.net/index.php)

- News (https://forums.alliedmods.net/forumdisplay.php?f=16)

- - Development Roundup, We need you! (https://forums.alliedmods.net/showthread.php?t=310564)

Re: Development Roundup, We need you!

I see there's the master (more recently updated) and the dev branch (not updated recently).
Which one should I get for more stability?

The only reason I want to update amxmodx is that client_cmd("mp3 play <path to sound>") gives "Server tried to send invalid command" error to the clients, but I also see it appends a new line after the command, so maybe that's the issue, not the "mp3 play" command itself (please someone correct me if you have more knowledge about this). The command itself as I write it does not contain a new line (I hardcoded it for testing), only the command that the client receives.
I'm using 1.8.2 currently, so if the official 1.8.3 solves the issue above I might use that as well, instead of a non-release version

EDIT: Updated to 1.10. client_cmd still doesn't work. I know the client_cmd stuff is off-topic here, so can someone direct me to a thread/github issue that discusses this problem, if it exists?

Re: Development Roundup, We need you!

The newline in `client_cmd` has always been there from the start. Maybe with the recent game releases, it's no more needed.
Are you using the latest HLDS version or ReHLDS?
Also, before anything else, make sure you do pass a valid command and that you can reproduce (create a simple test plugin, if you can)

If you are sure there is an issue and you're using HLDS, you should create an issue on Github.

Re: Development Roundup, We need you!

Quote:

Originally Posted by Arkshine (Post 2678396)

Thanks for replying!
HLDS for the moment.

But I just found out this morning (by hopelessly trying different things) that mp3 play <anything that doesn't start with "media/"> shows the invalid command message.
Is this intended or should I submit a bug report somewhere?

I see most of the online references for playing mp3s on clients use sound/....mp3 and media/....mp3 interchangeably, but I guess something changed in HLDS, or new dlls on clients

UPDATE: Actually, I think the client or server's dll blocks paths containing certain words. For example, it would tell Invalid command for media/somename/loading/1.mp3 but not for media/somename/loaging/1.mp3 - I don't understand. Should I create an issue about this on github?
UPDATE2: Done

Re: Development Roundup, We need you!

The amxmodx.org website is giving PR_CONNECT_ABORTED_ERROR errors when trying to load it.

Re: Development Roundup, We need you!

Seems to be working now, at least for me.

Re: Development Roundup, We need you!

It's still broken for me. I'm getting the above error using Firefox and ERR_SSL_PROTOCOL_ERROR when using Chrome.

Re: Development Roundup, We need you!

after soo, much searching reached the right place. works now. cheers

Re: Development Roundup, We need you!

a small bug in cstrike_const.inc file

PHP Code:


		
			
const CSW_ALL_WEAPONS      = (~(1<<CSW_VEST));

:arrow: should be :arrow:

PHP Code:


		
			
const CSW_ALL_WEAPONS      = (~(CSW_ALL_ARMORS|1<<CSW_NONE) )

Re: Development Roundup, We need you!

Quote:

Originally Posted by Natsheh (Post 2732032)

a small bug in cstrike_const.inc file

PHP Code:


		
			
const CSW_ALL_WEAPONS      = (~(1<<CSW_VEST));

:arrow: should be :arrow:

PHP Code:


		
			
const CSW_ALL_WEAPONS      = 0xFFFFFF & ~0x01;

Why do you think that? Do you have an example of code that is broken because of this? Also, wouldn't that remove CSW_P228 and CSW_G3SG1 through CSW_VESTHELM? Note that it is defined the same way in the cstrike module.

Additionally, if you can show it's actually a bug, you should create an issue on GitHub if you believe there is a bug.