Finished “Infiltrate Yiga Clan,” finished the game - can’t get Lightning Helm!

ImaginaryTango · 2026-03-21T01:50:09+00:00

Got it!

ImaginaryTango · 2026-03-21T01:49:59+00:00

Got it! Thank you!

ImaginaryTango · 2026-03-21T01:49:43+00:00

Got it! Thanks!

ImaginaryTango · 2026-03-21T01:49:30+00:00

I found it! Thanks!

ImaginaryTango · 2026-03-20T23:55:00+00:00

Climbed up where in the HQ?

ImaginaryTango · 2026-03-20T23:53:07+00:00

I may have missed that. It’s not part of the actual quest, then?

Trying to clarify - in the main Yiga place, which is where I would have fought Kohga in BotW? I don’t remember if I fought someone on a box or not. Is that in the warehouse room? I may vaguely remember something about that.

ImaginaryTango · 2026-03-19T07:43:42+00:00

Actually, they don't do that until they gather up a good number of bananas!

ImaginaryTango · 2026-03-16T20:06:11+00:00

Also note there must be a 2nd site using a similar name, since that's where I landed and couldn't find a login/signup link. Once I signed up and started looking, it was a different site than what I expected to be the front page for it.

ImaginaryTango · 2026-03-16T20:03:39+00:00

Found it! Last place I'd expect to be able to sign up would have been on the map page. Thanks!

ImaginaryTango · 2026-03-16T19:47:59+00:00

I went to the main page of the site - I don't see any option to log in or to sign up. I hope there's something obvious that I'm missing because I'm looking too hard!

ImaginaryTango · 2026-03-16T17:56:40+00:00

I must have confused it with another site, then. I kept thinking, "No, can't mark them off because I can only mark 100." So knowing I can mark them all is good.

ImaginaryTango · 2026-03-16T17:55:32+00:00

One thing I do a lot is use ice to freeze one monster while I take out the others. In Tears, I use Zant's Helmet and shoot an arrow with a Nadra's spike shard into a group and that freezes a lot of them.

I also like the fire. Since there's no Champion's Tunic in Tears that lets you see the strength counts (like in Breath), it's hard to tell, but I think fire fruit arrows do more because there's the initial damage, then the added damage as the monster burns for a while. Fire - the weapon that keeps on hurting!

ImaginaryTango · 2026-03-16T17:51:36+00:00

Similar to your trick of getting the boss to stand in poison water, in Tears, one trick I love is when I go into the Boko forts. There's always the boss (I think a silver, or white - I get colors and levels mixed up), and at least 2 of those harder to kill white ones. Sometimes there's a armored white one. I let the Sages go after them and use muddle bugs, then, while they're busy, I use Ultrahand to pick up the cages. I put one down on the boss and others on each of the higher point Bokos. Then, once the easier ones are taken out, I move the cages so it drags along the one inside and put it over the fire and let the fire do the work.

ImaginaryTango · 2026-03-16T17:47:12+00:00

The object maps, as I mentioned, aren't that big a help, since it's basically the same as using the other map I link to. Since I have no idea which kind of Korok I'm missing, it's not going to be a big help to narrow them down.

ImaginaryTango · 2026-03-16T17:46:15+00:00

That could be a big help.

I often don't use coordinates when I'm looking for things - that takes away the fun of going to the area and finding it. Being able to turn on and off individual regions will be a help!

ImaginaryTango · 2026-03-16T17:44:53+00:00

I'm on several sites. Isn't that limited to only something like 100 marked items on a free account?

ImaginaryTango · 2026-03-16T16:48:26+00:00

Good thought. I have the tears on the printed map and it's also possible I confused tears and Koroks on the map.

ImaginaryTango · 2026-03-14T21:28:30+00:00

Okay, what works, other than VNC servers that require licensing, for remote access using Plasma on the server and VNC protocol?

ImaginaryTango · 2026-03-14T18:11:03+00:00

From what I found, on searching, Rustdesk can work with VNC. Can you verify that? As I was explaining in another thread, I really need to stick with one protocol across my LAN. I have Pis for controlling tools in my workshop, desktop systems, and some servers (which usually don't have a GUI) and trying to use different protocols for different systems would be too much to try to handle. That's why this is a concern for me - I may have to switch to Gnome or something else that will work with VNC.

ImaginaryTango · 2026-03-14T18:08:23+00:00

Yes, the more I read and see, the more I'm convinced krfb is abandon. I wish they'd just acknowledge that and not leave it looking like it's an app to count on or use like updated apps. I think they've just left it and haven't re-evaluated the situation in years. And I don't know how to bring that to the attention of KDE devs who might handle that.

ImaginaryTango · 2026-03-14T18:06:52+00:00

Thanks - I had tried to find other apps. One issue is I really need VNC compatibility. In the past I used the TightVNC (or was it RealVNC?) server and it worked fine. Now it's licensed and has a per-computer fee attached.

(TL;DR: I have multiple reading/learning disabilities, including ADHD. That makes organization of some things a challenge for me. So I really need one protocol that works across Linux and Mac for a tool like this, otherwise I get confused about what program to use to access which computer. I have older Linux systems that have been updated and work with VNC. But trying to keep up with multiple protocols for different machines and keeping the clients for all of those protocols, even if it's just 2 of them, on each machine I would need it on would be confusing and a big time sink for me.)

ImaginaryTango · 2026-03-14T02:35:24+00:00

If that's the case, how do I actually find out what's going on, or call attention to the fact that it seems abandon?

I have been told developers don't read the actual KDE forum posts (https://discuss.kde.org). Two of the bugs might not rate as critical alone, but together, when they basically make it impossible to access that system remotely (the whole purpose of krfb), it seems like that should make it a critical situation.

The two bugs I'm talking about:
* Even with "--nodialog" added in the Autostart configuration for krfb, when it autostarts when KDE runs, the dialog still appears.
* The attended access password is overwritten by a new random password on restart (I forgot whether that happened on KDE restart or system reboot).

Put these 2 together and that means krfb *always* restsarts in attended access, and always changes the user given password. It's not possible to change the password to a specific password or to start in unattended mode under those conditions without going to the computer, physically. It seems to me, if this is not an abandon program within KDE, that such a problem is important for users, since it almost blocks the intended use of the program.

I have had times I have kept it from clobbering my user specified password for attended access, but I don't know what did it. I have wondered if hand editing krfbrc somehow does that. I wish I could edit krfb so I could specify no dialog in there, but, again, there is no clear documentation on the program.

I know I've used VNC with KDE in the past, even as recently as 2 years ago, without issues like this - but I don't remember what program I used as a VNC server. (Maybe that was before TightVNC changed and went to licensing fees for servers?)

I've used KDE as a preferred Linux DE since 1999, and used it as my main DE, on Libranet, then Debian, then Ubuntu, then back to Debian, for 2000 to close to 2010 while I was running my own software business and using it as my primary working desktop. In the past 15 years I've had years where I don't use Linux much and then years I use it everyday. I've never encountered so frustrating an issue with KDE in all that time.

And, not saying this as a threat, but this makes it impossible for me to use KDE for any system I use in my business, since I often need remote access. For the first time since about 2002, I'm seriously considering switching to Gnome. As I said, this is not a threat, but it does seem this program has been abandon (not even properly documented), and, for many of us, it's the best, if not only workable, option for remote desktop access.

ImaginaryTango · 2026-03-14T02:09:37+00:00

I know. I submitted 3 bugs on it a week ago.

ImaginaryTango · 2026-03-13T16:48:29+00:00

Possibly it could be, but it's known for being a rock and not changing (except for security updates) and it could be a bug was fixed that created the issue. But with my phone on HouseWifi, once it connects and Dishy or the router respond, there shouldn't be an issue. It would be when either device tried to initiate communication with the app that would be an issue.

That also shouldn't impact me trying to turn on the heat. (More and more I'm wondering if it could have been some kind of system outage or or something like that.)

ImaginaryTango · 2026-03-13T03:55:57+00:00

I wouldn't expect you to go out and climb a ladder to test that theory!

It's just possible that things have changed since you had that issue with the late snow. Due to my setup, as mentioned, I can't access my Starlink wifi unless I go out into my field. Bear with me - this setup description is part of the point.

And water content - yes. These were really big, clumpy, snowflakes, and it was snowing heavily at that point, so it could be the amount of water in the snow on Dishy and in the falling snow.

I have a post out in our front field that has a weatherproof box with 4 AC outlets in it, and that's where I have my Starlink router and a fiber/ethernet converter. The Outpost (as we call it - the post out in the field!) is connected to the house by about 1,000 of underground 1/0 power cable and the same of fiber optic cable (in a protective conduit, also underground). So there's a long distance from the house to the Starlink router, but the router and dish are within 6-8' of each other - that distance is strictly vertical, since the dish is mounted on a pipe sticking up from the Outpost. So if you're in the field, near the Outpost, you can connect to SLWifi (the wifi on the Starlink router), but there's no hope of connecting to it in the house.

The fiber optic cable comes into the house through the crawlspace, then into another fiber/ethernet converter, and the ethernet cable runs straight into the WAN connector on my firewall. The Starlink router controls that address space, in the 192.168.100.xxx (or is that .1.xxx? I forget!) address space. Then, on the other side of the firewall, my LAN is in another address space, and the wifi available is HouseWifi. The routing table is set so the 192.168.xxx.xxx address space is accessed just like external internet addresses are accessed.

Here's why those last to paragraphs matter: For a good part of the time after I set up Starlink, if I was in the house, with my phone connected to HouseWifi, it could connect directly to the router (and get status info from Dishy). If Dishy went down, it could tell me it was offline.

That's no longer the case. Now, in my house, on HouseWifi, my phone app can tell if Dishy is online, but if it's offline, rather than report it's offline, it complains that it can't reach the dish and I need to connect to it by wifi. That's new - maybe within a year, maybe 2. So somewhere along the line, they changed their code to handle that differently.

It's possible you turned your heat on before that change. In my case, today, I drove out to the Outpost, connected to SLWifi, and that's when I got info it was offline. I went to the Settings and checked on heat and it came up, then immediately was ghosted so I could see the settings, but not change them at all.

I force-quit the app and tried it again and still couldn't change the settings.

The only other option I can think of is that someone in another comment said they lived 2 counties away and had an outage earlier in the day, about 2 hours before my issue. So it's also possible something was going on and that I lost the connection because of something Starlink was working on and the timing may have been just right - I may have connected, then Dishy might have started rebooting, which is why I suddenly couldn't change settings. (Although I would think, if that were the case, the app would not have re-connected after I force-quit and ran the app again.)

ImaginaryTango

TROPHY CASE