Bug-NUM_FOR_EDICT Error: Bad Pointer

[sPlOrYgOn]

hmm..
if what you said is correct...
Then I'd say it's the camp waypoint bug that PMB fixed...
he changed it from a vector to an angle..
perhaps SoUlFaThEr missed some camp waypoints when he was fixing the waypoints after that change...
[edit]
except i still don't see how this can make the NUM_FOR_EDICT error...
[/edit]

[biohazerd87]

Remember this is Steam. It sucks. It likes to do dumb things.

But on a serious note I am just telling you what I did that worked. It maybe some sort of waypoint the bots can't inturrpret correctly. Did you try comparing the 2.1 version of PODbot waypoint code against the "2.0" version or the most up todate version before 2.1 to see what changes may have occured?

[sPlOrYgOn]

don't just say 2.1 or 2.0 it sounds like you're refering to podbot 2.0 or podbot 2.1...
more correctly it should be podbot 2.6mm R2.1 or R2.1 for short.
The 'R' helps to distingush us from the original podbot, since we are not the official maintainers of podbot..
We're only coding for podbot 2.6mm which is PMB's metamod port of podbot and cleaned by PMB.

And this bug has existed since PMB's latest release..
you can even check yourself. here
The only thing that your info matches with, is with what PMB did to the Podbot waypoints and that is, he corrected what was saved when making camping waypoints.
in the original podbot the bot saved a vector in the direction the waypointer was pointing at.. (at least I think thats how it was)
when PMB fixed it he made it save an angle instead of a vector and the angle is the angle where the waypointer was pointing at when he made the camp start/end waypoint.

[biohazerd87]

Originally Posted by sPlOrYgOn

don't just say 2.1 or 2.0 it sounds like you're refering to podbot 2.0 or podbot 2.1...
more correctly it should be podbot 2.6mm R2.1 or R2.1 for short.
The 'R' helps to distingush us from the original podbot, since we are not the official maintainers of podbot..
We're only coding for podbot 2.6mm which is PMB's metamod port of podbot and cleaned by PMB.

And this bug has existed since PMB's latest release..
you can even check yourself. here
The only thing that your info matches with, is with what PMB did to the Podbot waypoints and that is, he corrected what was saved when making camping waypoints.
in the original podbot the bot saved a vector in the direction the waypointer was pointing at.. (at least I think thats how it was)
when PMB fixed it he made it save an angle instead of a vector and the angle is the angle where the waypointer was pointing at when he made the camp start/end waypoint.

True I should have been more spacifice when telling which Version of podbot, I have also known about the NUM_FOR_EDICT for sometime now, but it would only happen like once every like 2 hours or never, now it does it ever 30 seconds. Thats why i ask

[sPlOrYgOn]

look...
I seem to get it within the first 15 mins..
but from time to time it goes on for a few hours before crashing...
it seems to be random..
and also if it is the camp waypoint problem it probably crashes when the bot decides to camp at that certain waypoint.

[biohazerd87]

so how would me making new waypoints fix this? If i use my waypoints I used for Podbot 2.6mm R2.0 why won't they work for PODbot 2.6mm R2.1? And I am not trying to argue with you I was just trying to help.

[biohazerd87]

I also took a map with waypoints that worked fine with PODbot 2.6mm R2.0 and removed all the camp spots to see if it would crash using PODbot 2.6mm R2.1 and it still crashed giving me the same error NUM_FOR_EDITC

[sPlOrYgOn]

dude...
I said I didn't change any waypoint code...
look at the change log..
it includes all major changes...

[SoUlFaThEr]

my 2 cents:

i got rid of every single camp spot in every singel map until it said 0 camp waypoints when wp status was typed in the console and then i went back and added them.........

its not the camp spots. so if you have a crash on a map.....take a look at all the camp spots....if the 2 red lines are pointing linear up or down anywhere on the map then erase them and play on to see if it still crashes.............but i used a method for security that all camp spots got replaced and they should be fine.......

[sPlOrYgOn]

so it's not that thats causing the problems...