Rendar1970 Posted November 22, 2007 Posted November 22, 2007 Suddenly im getting alot of crashes where a little windom comes up and says C+++++ runtime error, illegal action. I have found the source of this problem, but not a solution. This error comes up every time a saber leaves someones hand. Whether it be from disarming, throwing the saber, or even when they drop it when they die. The second a saber comes out of someones hand, i get the c+++ error crash. and just for information no i do not have any clientside saber mods or hilts.
Maxstate Posted November 22, 2007 Posted November 22, 2007 First of all, delete all your other OJP DLL files and make sure you don't have any in base or elsewhere. Second, what hilt were you using?
Rtemis Posted November 23, 2007 Posted November 23, 2007 The hilt problem is with not only with us. It's also with the bots. the SmallAssassin bot, for example, has a ninja sword instead of a lightsaber. Whenever it's dropped, C+++ error occurs. The clanging sound reverberates madly.
Maxstate Posted November 23, 2007 Posted November 23, 2007 Maybe you have two conflicting saber names in your .sabs?
DarthDie Posted November 23, 2007 Posted November 23, 2007 Yeah this happens to me too, when it pops up just click ignore.
SeLeXeL Posted November 23, 2007 Posted November 23, 2007 I had this error yesterday when testing out a hilt I created. Only it wasn't my saber with the issue. One of the bots had thrown theirs, and I don't think it wasn't able to return so I moved in to chop em down, I receive a pop-up msg saying something like ' Saber is not used ' or something to that effect.
razorace Posted November 26, 2007 Posted November 26, 2007 Sounds like the saber drop code got borked somehow. Someone should post a bug ticket if it hasn't already been done.
Maxstate Posted November 26, 2007 Posted November 26, 2007 Hmm something else might be borked. It only seems to happen with hilts that people don't have but the server does, or at least in my games. So it continues...
razorace Posted November 27, 2007 Posted November 27, 2007 That could very well be it. Unfortunately, the coders need some foolproof steps to make it happen before they can fix it.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.