[sgqwonkian]

Having looked briefly at your code and not found any obvious typos or conflicts*, I suspect the problem lies in when "TYPE homeworld" triggers.

I think it triggers only upon arriving at a homeworld and either avoiding or surviving a fight. After all, it's the same code used in the main game's home_muk to tell you "You have won a decisive victory!" and that only happens after the battle is over.

So, if you want them to be friendly or enemy at the homeworld, you need to make sure it's set before you ever get to the homeworld.

Currently, on the first two pages of lovemuk, you have a REQ3 that draws on either CONDITION 4 or 5. One of those is "nothome", so it'll trigger before the fight whenever you're not at Bandur. The other is "homeworld", so it'll only trigger at Bandur, but after the fight is over.

I think the solution is to get rid of REQ3 on the first page of lovemuk, and get rid of the second page entirely. Then, in theory, the first page will trigger whenever you meet them, regardless of where it is.

Also worth noting that in lovemuk, it's possible to match the triggers to both the first page and the third page at the same time. However, due to the "ACTN endquest break" in the first page, it'll never load the third page. If you remove the "ACTN" (and just the break, not the popup or endquest) from the first page, it'll display the third page after the first one. I think.

I'm hoping that solves your problems. I haven't tested it yet, but the logic seems sound.

__________________________________________________ ___________

*: Okay, so there is one possible conflict/error/typo, but I haven't tested it yet, and it's definitely not related to what's causing the muktians to not be friendly at their homeworld. You have REMS happen twice in page 1 of hatemuk. It targets different ships each time, but I've found that with some codes (it was either ITEM or ITMS, don't remember which off the top of my head) there's trouble when you use the same code twice in one page.

Don't know if that will be the case with REMS, but I mention it just in case. Should you ever find that the ship doesn't go away, it's probably because of the code happening twice on the same page - only one activation happens. The solution, should that problem manifest, would be to move the second instance of REMS to PAGE 2.