[WildCard65]

Originally Posted by asherkin (new-api exists because it was the only candidate, not because it's perfect - it was actually written for AMXX).

If I'm guessing this right, your saying the new-syntax is a way to differentiate SM SP from AMXX Pawn?

[asherkin]

Originally Posted by WildCard65 If I'm guessing this right, your saying the new-syntax is a way to differentiate SM SP from AMXX Pawn?

I have absolutely no idea how you managed to draw that conclusion from a discussion about an API browser - that is seriously impressive.

[Wliu]

Originally Posted by asherkin FYI, wearables are not weapons, I'm not sure why you would expect them to be. And the documentation is on the wiki.

Just the fact that they're equipped in weapon slots and not as cosmetics.

And since no one seems to have answered abrandnewday's original question, I might as well:
I can't log in either (used to be able to using AM credentials), so I'm going to assume that that part of the website broke.

[RedSword]

I believe a simple and easy way to solve this problem would be to allow login&commenting on the old API... The old API is still online for a reason (notably for forum links I'd say, and I believe people looking at it should be allowed to know important information (i.e. a list of team number per team, per mod)...)

On a side note, since the old API code isn't (publicly) available (I know, license stuff), they have no way to know how to query the old API comments (if it were to be AM-powered) in a new API they code themselves.

Red

[404UserNotFound]

Originally Posted by Wliu Just the fact that they're equipped in weapon slots and not as cosmetics. And since no one seems to have answered abrandnewday's original question, I might as well: I can't log in either (used to be able to using AM credentials), so I'm going to assume that that part of the website broke.

I'm guessing it was disabled when the new API was released.

[asherkin]

Originally Posted by abrandnewday I'm guessing it was disabled when the new API was released.

It broke when the forum password hashing scheme was strengthened - the method in use by the API browser is fundamentally incompatible with sane security.
Step 1 of fixing it was to move it to HTTPS (which was done a while ago), no one has had time to get back to it and do the necessary code changes (as psychonic said, it's not exactly pleasant to work on.)