Around 5th job, Luminous was also changed to be identical to KMS's system, meaning a reduced mobbing ability but significantly increased bossing ability
The addition of the Meso Market system, allowing users to trade maple points for mesos and vice versa
The Legion system, which replaces the character cards and part-time job system and grants you bonuses depending on the characters you have. The Legion shop also allows you to purchase leveling potions and 2x cards.
Arcana (Spirit Forest): the fourth area of Arcane River
Cadena: The Nova thief character, who uses a chain to attack
Illium: A Verdant Flora character, who utilizes a crystal summon to direct his attacks
Morass (Swamp of Memories): The 5th area of Arcane River
A revamped Papulatus, and the addition of chaos-mode Papulatus
The removal of meso drops from bosses, and the addition of the Power Crystal, which can be sold to an NPC in the Free Market for boss meso rewards
Ark: A High Flora character corrupted by a Specter, functioning on a similar light/dark system to Luminous
Will, the level 250 boss of the Esfera area, notable due to difficult mechanics in all 3 stages (such as having to fight Will in 2 dimensions at once during the first phase)
The Monad blockbuster, exclusive to overseas servers, featuing the Julieta boss (a multi-map raid boss), and ultimately tying in all non-KMS content into a single storyline.
Since you decided you want to go out by insulting moderators, likely myself since I was the one who escalated your warning after you refused to acknowledge the ones given to you, on … (more)top of spreading FUD and having a generally toxic attitude, I've finalized everything by giving you a ban.
I'll be completely honest, typically that doesn't happen; you'd have gotten a temporary ban after the warnings for a duration according to moderator discretion. But you've demonstrated a consistently poor attitude towards...well, everyone and everything really. The autistic comment was really the last straw.
There is a cap on the number of potions you can consume. Separate caps for each type of potion.
You've hit that limit on the strength-boosting potions.
displays it sends them your fps, current map, world, level and job, as well as your PC's specifications. I don't think they use this feature to investigate client crashes. As in, I don't think any special log is sent to them whenever someone crashes specifically, identifying the line of code that caused it.
Crash logs will typically detail PC specifications, current map, and other details. This allows developers to track and record patterns to help identify the issue. For example, if an issue is only affecting computers running Windows 10, and Windows 8 users are fine.
The line in the code is likely sent as well, along with other debug information. What the message is doing is alerting you that your information is being sent alongside it. Many companies do this because many people dislike the idea of their information being logged.
Identifying what line of code caused it isn't actually as helpful as you think. For example, here's a segment of a crash report generated by one of my projects:
I actually had serious problems with this issue occurring repeatedly, but couldn't identify the cause. You could guess that I had mistyped the name of the database table in the SQL query, but it had worked the day before so that couldn't have been it. For some reason, the database the program was accessing kept disappearing at random.
Give up yet? The actual issue was that my team was using a publicly accessible test database which everyone in the school had access to, and as a result it was repeatedly being overwritten by other students turning in their work for the database management course. I only managed to identify the issue because I brought it up with the guy who managed the school's databases and he pointed out that we were using the test database rather than the official one we had been assigned (he also acknowledged the problems with the publicly-accessible test database and flagged it to be shut down).
But you'll note that you couldn't have guessed that from the line of code on its own. You need to look at all factors to understand crashes; especially if an incident can't be reproduced in a testing environment. (less)
