What Is it I dont get with Mongos Golem?

So, I tried to make a Agent to test out Mongos golem in FP today. After some twinking at lvl 20, I got a wrangle and casted FP Enforcer and Mongos Golem (adding 1000 HP).
I then went to the subway to get some Ilegaly modified arms, when I notised my HP was only 1k + a tiny bit, and I dicovered that the Mongos Golem was no longer in mt NCU!

How come? Is it playshift req. or something? (says playshift requirements visual prof Enforcer.) So, when I shift playfield, my character is loaded with no nanos for a millisecond, then Im a Agent and Mongo Golem breaks?

Is this a bug, or intended.

Walcaround: get the wrange, enter desired playfield then cast wanted HP buff (mongo).

Those HP buffs have always cancelled on zoning, you'll need to cast them every time you zone.

Im prety sure I dont need to recast on my Enforcer, only my Agent in FP,

On my Enf I've always had to recast after zoning, will be able to check on him after work.
I doubt it's changed, but perhaps it has but only on the non-FPable ones.

On enf i don't have to recast on zoning, this changed with 18.7

Quote:

---

Originally Posted by Wakizaka

On my Enf I've always had to recast after zoning, will be able to check on him after work.
I doubt it's changed, but perhaps it has but only on the non-FPable ones.

---

It was changed on 18.7 Now my enfo zones and keep the huge hp buff just fine. Probably the same bug Agents had with Adv morphs canceling on zone

They did indeed change the nanos with 18.7. If you've got an eye for it you can see that there's something funny going on in the database.

Mongo's Golem has a requirement that most likely causes the problem: PlayshiftRequirements Self VisualProfession == Enforcer. That means every time the character zones the game checks if their visual profession (i.e. false profession counts) is enforcer.

Looking at Mongo's Kraken which most 220 enforcers will likely be using, we can see that there's no PlayshiftRequirements entry at all, meaning you're free to zone however you please. Going back one step in the line, Mongo's Behemoth has a PlayshiftRequirement of Level <= -1, which basically means it will ALWAYS wear off when you zone (since your level is never negative).

So I see two likely problems here. First, the nano is wearing off despite your visual profession being Enforcer, this says to me that the game probably puts you in the new zone, makes that check, and then puts all your buffs (including false profession) back on you, so you're an agent at that instant. The order of the check likely needs to be changed, or some workaround figured out.

And then of course there's the general inconsistency in the SL essence line. I was prepared to accept it if it had a playshift requirement only for the FPable nanos, but the level requirement on Mongo's Behemoth makes me think that there's some big oversight and the line in general needs to be reviewed.

If you haven't already I'd send in a bug report about this. Hopefully Michi also sees this thread and takes a look at these nanos before he's done with 18.7.4

I bet all old Huge HP buffs had the 'PlayshiftRequirement of Level <= -1' prior 18.7 and it was changed, but some nanos were overlooked (as expected with such huge changes).

You should definitely post a bug report.

Quote:

---

Originally Posted by Litestrider

Mongo's Golem has a requirement that most likely causes the problem: PlayshiftRequirements Self VisualProfession == Enforcer. That means every time the character zones the game checks if their visual profession (i.e. false profession counts) is enforcer.

---

Actually no. False profession does not count for playshift requirements. Playshift requirements are matched during playfield change (and possibly when logging in). It does not include effects of other nano programs. Since False Profession is a group of nano programs which change the Visual Profession stat, this check is broken by design.

Further, there are two playshift requirements for this nano. It's the playshift requirements criteria block, and it's the Use criteria block, because the nano as a whole is set to check playshift requirements.

It looks like a designer either didn't know how playshift requirements work, or they lazied it and set VisualProfession instead of Profession as the effect would be the same.