Search results

Not a damned clue man.. beats me

Yea except sometimes I want the bong.. and sometimes I don't. Changing the file all the time would be a pain!

Does this bong ONCE when you first flee to safe spot or does it bong endlessly the whole time they are in system? Endless bonging would be annoying as hell. I'm wishing I could seperately enable bonging for local chat and binging for special spawns so that if a couple of people are shitting up...

Interesting! I suspect the behavior of our bot would be FAIRLY standard. If so, and you have a second account, bring a noobcorp alt into system with a cloaking device and they will all warp to safes and cloak and you can have the belts to yourself. :evil: Syncro warping ends eventually...

I run two accounts ratting in the same system and I have seen it synchronized initially then they split up. This is mostly when they both are at safespot to start and I hit "run" at the same time. I suspect that the ideal would be to "run" with them in different belts where there was already...

Do you seriously have multiple people in your corp/alliance that you know are running this exact same bot? Ratting in a system with that many other "friendlies" would suck. Someone wouldn't chain right etc. I'd suggest ratting elsewhere! Another possibility would be to switch to using...

I'd love to have it be specific about launching combat drones only (so I could have some armor rep drones in the cavernous domi drone bay). Not sure if that is doable though. It shouldn't be ALL that hard to do, just not a priority for me. I don't equip drone range extenders for just this...

uhhhhh. It creates a template whitelist for you. Fill in where obvious.... Lets assume you are in 0.0 and want to keep on ratting when members of your alliance are in system rather than hiding at safe spot. Step 1: delete the current charname_whitelist.xml from your config folder Step 2...

I have no idea what you are asking here.

Are you using the latest "stable" version or are you trying to pick and choose versions from the main tree?

Current version of ISXEVE fixes this, both chaining and also a problem we were seeing with armor tanking.

This works for me.. but from your english I'm guessing you might be using it wrong... You should only have ONE of "warp out on whitelist" or "warp out on blacklist" checked. Blacklist would be for mining in high-sec to hide when a corp/individual that is hostile (perhaps wardec'd) comes...

More input on the chaining problem, seeing the same thing here. My recollection was that if I kept the console window open, it would spam the ship type to that window (frigate, crusier, destroyer, battlecruiser, battleship etc) but currently it's throwing a 3 digit number in there. The number...

My fix doesn't make it crash :P If you run with out it you will move from belt to belt to belt doing nothing and likely still crash eventually. If not then the reason why it crashes with my fix is that there is something in the "actually fight with the rats" code that causes the delayed...

ratter good work now stable since hours... Edit.. both instances just crashed within a minute.

I've never had a problem with this although I can see where you might have a problem switching back and forth. I run two instances of Eve/ISXEve all the time. The instances of eve are set to run windowed when starting normally and they come up the same way with or without innerspace/ISXeve...

Well.. it actually tries to rat now but the whole of eve seems to crash occasionally. Posting crash debug log here: LOAD: 0.00033 sec 'res:/UI/Texture/UITexLib_01.dds' PREP: 0.00235 sec 'res:/UI/Texture/Icons/icons03.dds' PREP: 0.00030 sec 'res:/UI/Texture/UITexLib_01.dds' LOAD: 0.00008 sec...

Workaround/change Change: if ${tgtIterator.Value.OwnerID} != ${Me.CharID} to if ${tgtIterator.Value.Owner.CharID} != ${Me.CharID}

Sit at a safe spot away from other ships and run this.... without the radius argument it returned a LOT of results even with an empty grid in game. The Target.OwnerID is different every time this is run. function main() { variable index:entity tgtIndex variable iterator tgtIterator...

The game didn't patch but ISXEVE.dll DID patch today. Likely Amadeus accidentally broke something. Updates on testing: Searching for PC ships on grid variable index:entity tgtIndex variable iterator tgtIterator EVE:DoGetEntities[tgtIndex, CategoryID, CATEGORYID_SHIP]...