06.07.2014, 21:20
I have no actual knowledge of SA-MP internals, so I can't tell you anything "for sure", this is just based on knowledge of SA and logic.
The client has to store the list of "removed buildings" for when the world streams in and out, so I imagine that there is indeed a limit to the size of this list, and therefore the number of RemoveBuildingForPlayer calls that can be made before it simply doesn't work anymore. (B)
In regard to A, this is probably just because you're making the engine do far too much at once. It's likely similar to the limits (especially in past versions) on CreateObject, and too many objects in the same area, etc. - SA doesn't exactly have the best game engine in the world.
It would be useful to know what the limit for RemoveBuildingForPlayer is, and in your case, it would be useful to have something like a RestoreBuildingForPlayer function.
The client has to store the list of "removed buildings" for when the world streams in and out, so I imagine that there is indeed a limit to the size of this list, and therefore the number of RemoveBuildingForPlayer calls that can be made before it simply doesn't work anymore. (B)
In regard to A, this is probably just because you're making the engine do far too much at once. It's likely similar to the limits (especially in past versions) on CreateObject, and too many objects in the same area, etc. - SA doesn't exactly have the best game engine in the world.
It would be useful to know what the limit for RemoveBuildingForPlayer is, and in your case, it would be useful to have something like a RestoreBuildingForPlayer function.