30.07.2015, 16:07
There is an object limit, it is 1000 objects.
Whether you use a streamer or not, the object limit will always remain 1000.
The only thing the streamer does is this:
CreateObject will save at the client's memory and the objects will be loaded at all times.
However what a streamer does is it is streams the objects, it is not saved at the client's memory. A streamer will show objects only if the client is near them (or the stream / draw distance set by the scripter)
When you use CreateObject, the objects you have added will be used from the "object slots" and when you use CreateObject, the object will use from the slots whether the player is near the object or even at the other side of the map.
What a streamer does is, show the objects that are only in the range of the player. This way, the object limit is countered. Because the "object slots" are only used when the client is near the dynamic objects.
However, even if you use a streamer, you must not forget that the visible objects limit is 1000. So in other words, the maximum amount of objects you can use is 1000, at all cases. However using a streamer is wiser by configuring which object will be shown when or where, this way you can counter the limit.
Infact, the amount of objects that is visible used through the streamer is limited to 500, however this is adjustable.
So to keep things short, a streamer is not some "magical plugin" that removes the object limit, it is something that just makes smart moves and shows objects only when they are supposed to be shown at.
With the help of a streamer and setting your object stream / draw distance smartly, you can easily counter the object limit.
Whether you use a streamer or not, the object limit will always remain 1000.
The only thing the streamer does is this:
CreateObject will save at the client's memory and the objects will be loaded at all times.
However what a streamer does is it is streams the objects, it is not saved at the client's memory. A streamer will show objects only if the client is near them (or the stream / draw distance set by the scripter)
When you use CreateObject, the objects you have added will be used from the "object slots" and when you use CreateObject, the object will use from the slots whether the player is near the object or even at the other side of the map.
What a streamer does is, show the objects that are only in the range of the player. This way, the object limit is countered. Because the "object slots" are only used when the client is near the dynamic objects.
However, even if you use a streamer, you must not forget that the visible objects limit is 1000. So in other words, the maximum amount of objects you can use is 1000, at all cases. However using a streamer is wiser by configuring which object will be shown when or where, this way you can counter the limit.
Infact, the amount of objects that is visible used through the streamer is limited to 500, however this is adjustable.
So to keep things short, a streamer is not some "magical plugin" that removes the object limit, it is something that just makes smart moves and shows objects only when they are supposed to be shown at.
With the help of a streamer and setting your object stream / draw distance smartly, you can easily counter the object limit.