Basic informations

OS: Windows 10 22H2
VSCode version: 1.81.1
Extension version: 0.2.0

Further Information

The extension is named AMXXPawn vscode in the Extension Browser. But it tries to compile scripts using the SourceMod compiler.

To Reproduce

Install the extension.
Configure mainPath
Get the error spcompile.exe not found

Code to reproduce the behaviour

N/A

Expected behaviour

The extension looks for amxxpc.exe, the AMXX compiler, instead of SourceMod compiler.

Error messages

I didn't record them before I removed the extension, sorry.

Aug 19 '23 02:08 tmp64

I agree

need more support for AMXModX

Sep 07 '23 01:09 wopox1337

Hey @Sarrus1, is there any possibility to get better support for the extension? The AMXX plugins don't work with the updated LSP.

Jan 13 '24 22:01 aleeperezz16

@Sarrus1 up

Apr 08 '24 00:04 wopox1337

Echoing the sentiment here - the plugin is still trying to act like it's running on sourcepawn

May 08 '24 11:05 ededdneddyfan

Setting current file as main also doesn't work

May 08 '24 11:05 ededdneddyfan

Hi all, I don't want to make false promises: Porting the sourcepawn ext to amx was much more work than I thought... A lot of this comes down to the fact that the syntax is still different, which trips the parser. Maybe, and that is a big maybe, I can disable some features to make it somehow work. But I want to insist that my priority at the moment is to polish the sourcepawn extension and to ship a stable release of the rewrite, as it has been in the works for 8 months now.

I will update this issue when I get to work on the amx ext.