[Solved] error in .sma with TEAM_COLOR - Page 3

redivcram · 02-14-2021 , 12:47 Re: error in .sma with TEAM_COLOR

Does HLDS close? If not, there should be output in the console.

Awesomerp · *Last edited by Awesomerp; 02-14-2021 at 13:39.*

If you mean the cmd tab of the server, it auto closes also
start hlds -game cstrike -console +maxplayers 12 +map de_dust2 (i have put this in the hlds)

OciXCrom · 02-14-2021 , 13:40 Re: error in .sma with TEAM_COLOR

Quote:

Originally Posted by Awesomerp

I tried compiling the file on 1.9 and I got the message: fatal error 100: cannot read from file: "dhudmessage"
am I missing this include?

Which means you didn't compile on 1.9 because 1.9 already has dhudmessage included.

redivcram · 02-14-2021 , 14:13 Re: error in .sma with TEAM_COLOR

Quote:

Originally Posted by OciXCrom

Which means you didn't compile on 1.9 because 1.9 already has dhudmessage included.

Now I feel stupid. :V

Awesomerp · 02-14-2021 , 14:17 Re: error in .sma with TEAM_COLOR

Then i dont know what I am doing :_
Is there still a way to see whats wrong?
Downloading latest amxx and compiling ?

redivcram · 02-14-2021 , 14:42 Re: error in .sma with TEAM_COLOR

When you download AMX Mod X, you get its own local compiler along, located in addons/amxmodx/scripting as amxxpc.exe. I assume you're using a web compiler?

Awesomerp · *Last edited by Awesomerp; 02-14-2021 at 15:23.*

When I was using the web compiler it always failed, but when i have put in the hud and colorchat includes and used compiler from app the compile suceeded. But now I dont know the problem cause the server autocloses

And yes I just noticed since I am trying to run the plugin on 2 versions they are 1.8.2 and 1.8.3 ( not 1.9 sorry)

redivcram · *Last edited by redivcram; 02-14-2021 at 15:50.*

Run HLDS in GUI mode and check the console tab. *Assuming that's even possible, never even used HLDS windowed, only in cmd*

Awesomerp · *Last edited by Awesomerp; 02-14-2021 at 16:18.*

Now I tried 1.10 compiler got new error messages
cstrike\addons\amxmodx\scripting\hns1.sma(875 ) : warning 213: tag mismatch
cstrike\addons\amxmodx\scripting\hns1.sma(312 9) : error 040: duplicate "case" label (value 1)
cstrike\addons\amxmodx\scripting\hns1.sma(349 0) : warning 213: tag mismatch
cstrike\addons\amxmodx\scripting\hns1.sma(349 1) : error 040: duplicate "case" label (value 1)
cstrike\addons\amxmodx\scripting\hns1.sma(419 5) : error 040: duplicate "case" label (value 1)
cstrike\addons\amxmodx\scripting\hns1.sma(445 4) : warning 213: tag mismatch
cstrike\addons\amxmodx\scripting\hns1.sma(446 5) : warning 225: unreachable code
cstrike\addons\amxmodx\scripting\hns1.sma(476 6) : warning 213: tag mismatch
cstrike\addons\amxmodx\scripting\hns1.sma(508 5) : warning 213: tag mismatch

fysiks · *Last edited by fysiks; 02-14-2021 at 16:31.*

Regarding all the duplicate cases, it's because you are redefining/overwriting the variable "NORMAL" (see lines 74 and 356). In other words, you are using the same variable name for two different purposes. And it looks like all the tag mismatches are also because of this.

Unreachable code means that the code on the specified line will never be executed, ever. Whether or not this affects how the plugin works depends on how you need that particular function to behave. You should