[fysiks]

Originally Posted by ViBE what i really miss are a complex voting/mapvoting like deagle's map manager and an afk managing stuff. and banning should be like amxbans.

If that's what you like then use those plugins instead of the default functionality. That is why the ability to make your own custom plugins exist. The core shouldn't have all these features because it will be impossible to design it to satisfy everybody.

Originally Posted by ViBE 3rd party plugins are pretty outdated sadly.

Why would you make that generalization? Many of them still work just fine. If you have a specific issue with a plugin you can request that it get fixed. The community for 20 year old games is much smaller than it used to be so there is naturally going to be a slow down in development of things for the game(s).

[PartialCloning]

Originally Posted by Arkshine As usual, AMXX should retain full backward compatibility, so if existing functionality breaks after upgrading, file a bug report.

https://github.com/alliedmodders/amxmodx/pull/662

[CrazY.]

Is custom entity data module going to be integrated in main amxx package?

[<VeCo>]

Hey, I was looking around the example codes from the 1.9 API changes page and some of the default plugins, and I noticed some peculiar coding style which made me wonder.

As far as I understand, callbacks from within the plugin now use the short '@' symbol (which actually becomes part of their name), while forwards registered from includes use the full 'public' keyword. I assume that improves code readability, but can you shed some more light on this? Do you encourage it as a new standard coding practice?

[fysiks]

Originally Posted by <VeCo> Hey, I was looking around the example codes from the 1.9 API changes page and some of the default plugins, and I noticed some peculiar coding style which made me wonder. As far as I understand, callbacks from within the plugin now use the short '@' symbol (which actually becomes part of their name), while forwards registered from includes use the full 'public' keyword. I assume that improves code readability, but can you shed some more light on this? Do you encourage it as a new standard coding practice?

There is no functional difference between declaring a function or variable as public using 'public' instead of 'new' or starting the name with '@':

Originally Posted by Pawn Language Guide Global “simple” variables (no arrays) may be declared “public” in two ways: ⋄ declare the variable using the keyword public instead of new; ⋄ start the variable name with the “@” symbol.

The only difference being that the '@' become part of the name (as you noticed).

Since they are functionally the same, someone could choose to use the difference to convey certain context as you explained already. Very few plugins (2 of 21) actually use this method so it certainly can't be called a new standard practice for AMX Mod X. IMO, someone noticed that it worked and figured that they wanted to be different.

[DJEarthQuake]

Nice write up. Implementing @ forthwith.
22/09/1998 Functions whose name start with an '@' are always public.

[PartialCloning]

The upcoming update looks to be gamedata breaking. The beta clients already support the new "Account" message, suggesting the update could be released soon. How long would it take to update gamedata?

[Arkshine]

I'm following more or less the changes on /ValveSoftware/halflife but it looks like I missed the "Account" thing, could you elaborate/link on it?

[PartialCloning]

Under the beta client, your money and your teammates money is displayed in the scoreboard.

Account Message:
Destination: MSG_ONE
ARG 1: BYTE (Player ID)
ARG 2: LONG (Amount of Money).

[PartialCloning]

https://github.com/ValveSoftware/hal...ment-485826646 is set to fix the gamedata break reported above.