Using “//so all port” no response

[Wickert99]

Just updated and ran sortie. Was so smooth! Was cruising through aita>gartell> then otw to Triboulex and then it started to time out going up and down with //so all port. All toons accept the one using command :( so i resorted to manual use. Then doing upstairs "//so all port" just would not send my alts up and down the rest of run :( but the char i used the //so all port command on worked every time. So sorry if i'm bugging i'm just so keen for this to work! @staticvoid0 @AkadenTK Love you guys

Thank you very much again!

[AkadenTK]

If you can, next time you go in, do a //sw debug then use it normally until the problem occurs and record the chat output for us? That will help us understand what's happening.

A screenshot will suffice. You don't have to type it up :P

[staticvoid0]

We’ll get ya straightened out man, don’t stress. Follow up with that ss.

[Wickert99]

Sure thing! Will do that tonight.

[Wickert99]

Ok! Turned on debug all sortie just now. Superwarp worked perfectly the whole run! I guess it was just user error...
Even porting down from Aminon was great!

Question, how do you port up from Aminon with it choosing the difficulty?

Thanks so much for a truly amazing update! Appreciate you all.

[xerusjoe]

I've had a mixed bag. Turning on debug gives messages like "debug: poke npc: 21001014 822.
Timed out waiting for response from the poke.
Retrying..."
It will just repeat that until it gives up or until I manually interact with the gadget/bitzer/device in question.
It's been in multiple areas. One run it'll work fine, and then another it will just refuse to work and the above type of message will display.

I should add, I'm not using the "All" part. This is for a solo character, but I'd assume the same problem would have the same solution for All vs. single character.

[staticvoid0]

there are silly little things that can cause this on the user's part, like for example, and i'm not saying you're doing this, but if you were to type a macro up as /console so p port. instead of /console so p port i believe that would produce this kind of result and that kind of error might go unnoticed, so you really have to take it apart and make sure there isn't something you're doing wrong because that isn't the only example i can think of.

[staticvoid0]

Ok! Turned on debug all sortie just now. Superwarp worked perfectly the whole run! I guess it was just user error... Even porting down from Aminon was great!

Question, how do you port up from Aminon with it choosing the difficulty?

Thanks so much for a truly amazing update! Appreciate you all.

So, the update just released addresses that for your Wickert. The user can now use so normal or so hard to enter aminon. you're safe to use all or party with this command too.

[xerusjoe]

there are silly little things that can cause this on the user's part, like for example, and i'm not saying you're doing this, but if you were to type a macro up as /console so p port. instead of /console so p port i believe that would produce this kind of result and that kind of error might go unnoticed, so you really have to take it apart and make sure there isn't something you're doing wrong because that isn't the only example i can think of.

All inputs have been typed manually, even doing as simply typing //so port, knowing it works and then later typing Space UpArrow to repeat the previous input and then it'll just time out. The whole thing is bizarre. Occasionally it'll work with no issues and others it'll just time out forever with no real consistency on when or why.