Innerspace is unable to initialize

Gray · Post by **Gray** » Fri Mar 11, 2011 6:49 pm

Once I lose link for some time, IS tries to reconnect once, fails (as connection hasn't returned yet) and makes no more attempts, which effectively reduces an idea of having unattended EVE bot to pieces. Is there any way to make it work much like ICQ: try to reconnect, say, every minute - and, once internet connection is reestablished, relaunch every instance of EVE again?

Post by **Lax** » Fri Mar 11, 2011 8:51 pm

Hi. I don't develop nor support bots. People who do, have solutions for this. Ask on isxgames.com or in the #isxeve chat room and perhaps someone there can help you out.

Gray · Post by **Gray** » Wed Mar 16, 2011 4:11 pm

It has nothing to do with bots. If I lose link for several seconds, EVE closes, restarts, then bot auto-restarts as well. If I lose link, say, for a minute, EVE just isn't relaunched by Innerspace (just brings an error message noted in this topic title). I know you don't support bots, but you support IS, right?

Post by **Lax** » Wed Mar 16, 2011 5:28 pm

Alright.... allow me to restate that.

I am in the middle of a rewrite of the client/server system used by Inner Space. It is intended to solve this and other issues with the license server. This is not going to come overnight, but it is currently my highest priority.

If you want the workaround in the meantime, the people I attempted to direct you to have it. It is not incredibly difficult to identify the box and handle it, and they already know how to do this...

Gray · Post by **Gray** » Thu Mar 17, 2011 8:44 am

Ehhe no, I don't want a workaround

But it's nice to know you are working on it! Any ETA on that, btw? Approximate? A week? A month?

Gray · Post by **Gray** » Sun May 29, 2011 6:52 am

Lax wrote:I am in the middle of a rewrite of the client/server system used by Inner Space. It is intended to solve this and other issues with the license server. This is not going to come overnight, but it is currently my highest priority.

May I ask please, how is this project going? I mean no offence, but... almost 2.5 months have passed, summer is coming soon, and it kind of sucks to "guard" my comps while it's so nice outside - just because several EVE windows might not be automatically restarted by Innerspace after an extended lag

sylvisj · Post by **sylvisj** » Sun May 29, 2011 10:26 am

May I ask please, how is this project going? I mean no offence, but... almost 2.5 months have passed, summer is coming soon, and it kind of sucks to "guard" my comps while it's so nice outside - just because several EVE windows might not be automatically restarted by Innerspace after an extended lag Crying or Very sad

You don't have to "guard" your PCs. In fact, you don't really have to do anything. For example, you don't have to wait 2.5+ months for a fix when you can find a workaround or other solution fairly easily.

You could do what was suggested in the first few posts, e.g. ask around in the ISXEVE-related areas as there's a good chance someone has encountered the same issue and fixed it. I do realize that's :effort: and complaining is much easier, but you've just about gone that extra step here, so why not take it just a *bit* further and ask for help with a workaround in the meantime?

sylvisj · Post by **sylvisj** » Sun May 29, 2011 10:28 am

Also, I'm not sure how much you pay attention to Lax's change logs, news posts, and IRC comments, but he has been quite busy with InnerSpace fixes, server-related fixes, etc. Simply put, he is fixing pretty fast. Have some patience and wait until the critical things are done so he can get to the once-off features which affect an exceptionally small portion of the user base.

Gray · Post by **Gray** » Thu Jun 02, 2011 6:09 am

I do not use ISXEve anymore (more than 3 months, that is). So any ISXEve solution wouldn't be of any use for me. Moreover, I know for sure from out inject lib developer that the problem is IS-related.

sylvisj wrote:features which affect an exceptionally small portion of the user base.

Exceptionally small?... Are you going to say that links if EU are so utterly stable so nobody experiences 20-30 second lags (which is enough to "break" IS) ever?

Post by **Lax** » Thu Jun 02, 2011 8:15 am

The "problem is IS related" because you are asking me to implement a feature that causes Inner Space to either wait until you have an internet connection, or automatically retry until it does.

How you would have tried to tell me in the beginning that this is not about your bot, and then come back and whine about not being able to go outside this summer because your bot might get disconnected, is beyond me. (Note that you call it "Breaking IS" but IS doesn't need a persistent connection. EVE does. You get disconnected from EVE. IS is only affected because EVE restarts the client)

I do not currently plan to implement such a feature, as it should be simple enough for anyone who is so concerned about their bot (which I am not responsible for) running, to detect a message box, and launch a new Inner Space session.

I would rather refund the precisely $10 you have paid me, than implement this feature. You're a dick to me, and from what I'm told you're also a dick to EVE players.

I don't see you getting me to implement this feature for you. Good day.