[IdkanYavuk X]

Hello LU Community

As you see in the title, the vehicle respawn time is very useful depending on the server, and I present you the next problem I have

This configuration line:

Code: (Configuration line :P) [Select]

vehicle_idle_respawn_time 250makes the vehicles respawn after unused for a while.
How can you guys make so the vehicles stay on the same spot until the server stops (infinite)?

Thanks and happy killing

[Mido_Pop]

Hello LU Community

As you see in the title, the vehicle respawn time is very useful depending on the server, and I present you the next problem I have

This configuration line:

Code: (Configuration line :P) [Select]

vehicle_idle_respawn_time 250makes the vehicles respawn after unused for a while.
How can you guys make so the vehicles stay on the same spot until the server stops (infinite)?

Thanks and happy killing

Man, If You Mean You Don't Need The Vehicles Re spawn Make This >>
 

Code: (Pop) [Select]

vehicle_idle_respawn_time 9999999999

[SugarD]

Don't use that for the time. It can create a buffer overflow.

Use this instead:

Code: [Select]

vehicle_idle_respawn_time 4294967295

[Juppi]

Actually it would cause an integer overflow, a buffer overflow is something completely different. Also it is worth noting is that setting the respawn time to max unsigned integer value wouldn't work in this case due to the way LU handles respawn times internally - they're signed integers, and the internal times are stored in milliseconds (so the user input is multiplied by 1000).

Setting the time to 2147483 or lower should work reliably.

Edit: Technically that doesn't keep the vehicles where they are until the server stops (it's only a couple of weeks, if the server is on longer than that some of the vehicles will respawn). If you want to keep the vehicles where they are for a longer time, you can use Vehicle.SpawnPos and Vehicle.SpawnAngle to force the vehicle to respawn at a given location.

[SugarD]

Actually it would cause an integer overflow, a buffer overflow is something completely different. Also it is worth noting that setting the respawn time to max unsigned integer value wouldn't work in this case due to the way LU handles respawn times internally - they're signed integers, and the internal times are stored in milliseconds (so the user input is multiplied by 1000).

Setting the time to 2147483 or lower should work reliably.

Blame VRocker. These are his words

I would also suggest adding an option to turn that feature off altogether in the next version.

[Vortrex]

I would also suggest adding an option to turn that feature off altogether in the next version.

I agree. Maybe it would work if we set the respawn time to -1 like I think SA-MP does.

[SugarD]

I would also suggest adding an option to turn that feature off altogether in the next version.

I agree. Maybe it would work if we set the respawn time to -1 like I think SA-MP does.

Tried that a long time ago. I think it just does whatever the default time is instead.

[Vortrex]

I kinda said that wrong. I was talking about in future releases, maybe if the value was -1, then have an infinite respawn time. It was more of a suggestion lol.

[SugarD]

I kinda said that wrong. I was talking about in future releases, maybe if the value was -1, then have an infinite respawn time. It was more of a suggestion lol.

Ah. Ya, that sounds good to me.

[IdkanYavuk X]

So I use 2147483?

I also tried using 0, and the vehicle made a quick respawn (note that the vehicle was vh.OneTime = true;) and stayed like that for a while (I don't know if it dissapeared or not after that)

[SugarD]

So I use 2147483?

I also tried using 0, and the vehicle made a quick respawn (note that the vehicle was vh.OneTime = true;) and stayed like that for a while (I don't know if it dissapeared or not after that)

Yes, use 2147483.

Several of us have suggested/requested an ability to turn this off in future versions. We aren't sure of the decision yet, though.

Did this resolve your situation?

[IdkanYavuk X]

Did this resolve your situation?

Yes

[SugarD]

Awesome!


Issue resolved, topic locked!