Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Couldn't find weapon XXX #406

Closed
BidyBiddle opened this issue Apr 26, 2017 · 6 comments
Closed

Couldn't find weapon XXX #406

BidyBiddle opened this issue Apr 26, 2017 · 6 comments
Assignees
Milestone

Comments

@BidyBiddle
Copy link
Contributor

BidyBiddle commented Apr 26, 2017

This "Couldn't find weapon ###" issue seems to only affect servers with:

  1. the "bot_enable" variable set to "1;" &
  2. the variables "teamnamered" and "teamnameblue" set to a custom field.
    These two variables have to return TRUE if you want to recreate this error, as far as my horrible experience went.

Hence, if the first option is set to "0" and you have custom names for the RED and BLUE team, then you're good. Alternatively, if you have set the first option to "1," then you must set the team names to blank or the default ones provided by the game.

The Great Ferroh

More information in this thread: http://www.urbanterror.info/forums/topic/31083-solved-couldnt-find-weapon-202/

@pedrxd
Copy link

pedrxd commented Jun 7, 2017

Something new about this topic?

@Barbatos
Copy link
Member

I tried for several days and in several situations, on both dedicated servers and local servers. Unfortunately, my game has never crashed. :/ Would anyone be able to provide a demo or some other "tips" to reproduce this crash?

@travmon
Copy link
Contributor

travmon commented Jan 31, 2018

Could be from running more than one server from same folder, or custom build? Have not seen this crash for awhile. Usually deleting the q3config.cfg from server always solved this issue for me.

@Barbatos Barbatos self-assigned this Jan 31, 2018
@Barbatos Barbatos added this to the 4.3.3 milestone Jan 31, 2018
@Barbatos
Copy link
Member

In fact, I just understood what introduced this error in 4.2.014 after digging some more in the code. This should be fixed'ish' since 4.3.0 and completely fixed in 4.3.3.

Please reopen the issue if you encounter that crash again later (but you definitely shouldn't!).

@BidyBiddle
Copy link
Contributor Author

BidyBiddle commented Feb 18, 2018

Just mentioning that it happened today in the middle of a Clan War having us lose a lot of time.
So it still occurs on 4.3.2.

Hopefully it's fully fixed with next update!

@pedrxd
Copy link

pedrxd commented Feb 20, 2018

It can be see on Zombie mod every day, but is a modded server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants