.NET scripting

[carbonfire]

Ok guys, I am pretty new to this community but not to botting. I am currently writing a bot in .NET using isxeve/lavish and I wanted to both introduce myself and ask a question.

the question being, when you access EVE via Globals, and you use frame lock, how many different actions can you do? For example, can I undock from a station, warp and mine all in one frame lock?

 

[CyberTech]

Ok guys, I am pretty new to this community but not to botting. I am currently writing a bot in .NET using isxeve/lavish and I wanted to both introduce myself and ask a question.

the question being, when you access EVE via Globals, and you use frame lock, how many different actions can you do? For example, can I undock from a station, warp and mine all in one frame lock?

Er.

A frame is one image drawn on the screen. 30-90 of these happen per second ("Frames per second", FPS). I'm sure you know that undocking does not happen in 1/30th, 1/60th, or 1/90th of a second, much less warping etc Things take time, and you must wait for the client to do what you told it to do.

 

[carbonfire]

Er.

A frame is one image drawn on the screen. 30-90 of these happen per second ("Frames per second", FPS). I'm sure you know that undocking does not happen in 1/30th, 1/60th, or 1/90th of a second, much less warping etc Things take time, and you must wait for the client to do what you told it to do.

ok, I understand that; but when you lock the frame, do you freeze the process or even though the frame is locked the game is really running normally?

also, lets say you wanted to get your ship's velocity... do you need to lock the frame for that, even though its just retrieving a value?

 

[CyberTech]

ok, I understand that; but when you lock the frame, do you freeze the process or even though the frame is locked the game is really running normally?

also, lets say you wanted to get your ship's velocity... do you need to lock the frame for that, even though its just retrieving a value?

Yes, when you lock the frame, the process main thread is frozen. You don't want to do long-lived items in a framelock.

You need to lock the frame for all data retrieval; that's how IS ensures the state of the data you're attempting to access during your access. If you fail to lock, the lock will be done by IS on a per-call basis, slowing you wayyy down.

 

[carbonfire]

Yes, when you lock the frame, the process main thread is frozen. You don't want to do long-lived items in a framelock.

You need to lock the frame for all data retrieval; that's how IS ensures the state of the data you're attempting to access during your access. If you fail to lock, the lock will be done by IS on a per-call basis, slowing you wayyy down.

gotcha. thanks you for your help. I hope I will have a release soon for you guys.