It’s a feature 
1 Like
it’s a feature 
itsa feature 
TBL broke too, by the way
Instance bugged, TBL bugged, Saalus bugged. What is content to be played then? Held fashion contest? sigh…
2 Likes
imc compensation = 3x exp tome -.-
F O U R
L O N G
H O U R S
O F
M A I N T E A N C E
A N D
E V E R Y
T I M E
A F T E R
M A I N T E A N C E
H A S
A
B U G
O R
A
M A J O R
B U G
3 Likes
best bugs ever
only the best game has the best bugs in petto for their hardcore masochist players
“I survived 9 dungeon kicks just to come out victorious on the 10th run!”
Best mechanics to increase difficulty? Bugs!!!
Just tried to do uphill.
Run #1 : Normal run, wave 30/30
Run #2 : Torch goes on an adventure to find its true purpose in life. (Lost a run)
Run #3 (on another character) : Torch is not back from vacation.
2 Likes
That’s why R9 won’t solve anything. They keep breaking the game every scheduled maintenance since day 1. Just wait and see how they’ll mess up in the next rank reset event too. It’s going to be worse than what happened in kTest, so be prepared to have your character deleted after using a rank reset voucher.
1 Like
It’s more like due to playerCountCheckDestroy=“1” on minigame event handlers.
That means, if an instance has 0 players in any given time, it will be considered as the run failed.
That’s what causes the game to have an instance to fail when all players are dead or left the map, like Earth Tower, Saalus and others. Additionally, the instance isn’t closed instantly after failure, there’s a ten seconds room before the instance is destroyed and players sent to the previous map.
So what happens here? There’s actually no mystery.
When players are entering instances, somehow the event handler is starting and doing the playerCountCheck before the players are able to join. It’s either the player who started the instance somehow took too long to load or the server started the event handler before the player actually joins or both, or simply a code error.
Proof-question: Did anyone actually had any problems with DG290? There’s no playerCountCheck for the dungeon.
Maybe it has something to do with ktos code merge on server-side in preparation for R9 due to players loading faster there (old bug fixed -> merge code with ktos -> threshold value updated). Maybe it’s something else.
But yeah, that’s the reason, playerCountCheck being executed before anyone actually joins to be counted.
P.S.: Same goes for no Torch in Uphill, the step “MGAME_EVT_EXEC_DELMON” is executed on mission-fail that actually deletes all monsters and npcs.
7 Likes
Maybe they tried to fix Saalus unlimited entries exploit and messed up.
2 Likes
Good to know, thanks for the insight.
Lost 2 mission entries because of this by going solo in a party, got auto kicked out after destroy the barrier in siaulai.
Loosing runs too. They better compensate with Monster Orb Fragments. Im losing all my daily runs with my high level pokemon and its a limited time event.
Everyone is suffering from this. And dont give me shitty EXP tomes. I want apprioate reward for my runs lost.
How do you lose tamer runs, doesn’t it only count when you collect the loot?
It’s a IMCeature 
1 Like
The whole reason I log in each day is now gone… Cant do instances - no reason to log on. If this doesnt get fixed by tonight IMC needs to give some really good compensation… 
10+ attempts to enter monster tamer. This game is so messed up. Im still waiting to spend TP i bought last month because they refused to remove the limit on my account (twice.)