Forum Rules [Updated 12/21/2016]


Please respect your community. Respect each other as you all enjoy the same thing – The Game.

We encourage open and friendly discussion of the game and the Community. Moderators and Staff have final decisions on all matters, and are here to make sure that the Community remains a friendly, fun place appropriate for players of all backgrounds, ages and groups.

It is the forum member's responsibility to stay up to date on forum rules and to honor the behavior outlined.


These forums provide an area for constructive player discussions of the game. It also allows players to
help each other identify bugs and issues, and help each other reproduce and resolve them.

These forums are not the most direct way to contact support. If you’re having an issue with your game and you need direct assistance, please tap on the FAQ/Support tab within the game.


Please make sure to stay updated on these rules by reviewing this page from time to time.


This is a private board. As such, decisions made are final.
We reserve the right to remove any message board content without notice for any reason.

Rule 1: Responses to rule violations
Violating these rules will result in warnings, either formal or informal, suspensions, banning, or other sanctions.

Rule 2: Respect other users on the forums
- Do not make attacks or insult other users, either in the forums or through private messages. Disagreements and debates are fine, but don’t make it personal.
- Do not attack groups. This includes professions, races, religions, sexual orientations, genders, incomes, or even vague groups like “you people.”
- Do not use ill terms which are offensive to groups, do not “flame”, “troll.” or “haze”.

Rule 3: Respect the forum purpose and structure
- Make your posts in the appropriate forum.
- Please use the Search function. If a relevant thread already exists, please post there instead of creating a new thread about the same topic. Duplicate threads will be closed to keep the forums orderly and easy to navigate.
- Keep off-topic posts in the off-topic forum.
- Don’t start discussions about games that are not ours.
- Do not cross-link to other message boards or websites unless approved by a moderator.

Rule 4: Respect the law
- Do not post anything illegal under U.S. law, or encourage other users to break the laws of the U.S. or their country of residence.
- Do not encourage users to break terms of service. This includes giving information about how to find scripts, exploits, or cheats, as well as arranging to buy or sell accounts or virtual goods.

Rule 5: Respect the audience
Think about who you're talking to. Users may be as young as 13 on these message boards, and may be male or female, and from countries across the globe.
- Keep your language civil. Profanity is frowned on.
- Do not post Adult Material, inappropriate graphic sexual content in any format, or links to sexually explicit sites.
- Do not post graphic images or explicit descriptions of violent acts.
- Do not use an avatar or signature that could offend other users. They have to look at it a lot.

Rule 6: Respect privacy
- Do not post any private emails or private messages unless you have the explicit permission of each person involved in the exchange.
- Do not post private communication between customer support, members, moderators, or administrators on these forums, or anywhere else. (This include support ticket responses)
- Do not post any information covered by a non-disclosure agreement or beta testing agreement. Even if you somehow have inside information about our competitors, for legal reasons we don’t want to hear it.
- Do not post Facebook information about other forum users.
- Do not post any private information about other users.
- Do not post in-game information in an attempt to have other players attack your target. Be careful to not cross the line into bullying.

Rule 7: Do not spam
- Do not post repeatedly about the same topic.
- Do not spam users on the forums or through private messages.
- Do not start a thread without actual purpose.
- Do not start a thread about a news story or article unless you make it clear what the story is about, and offer your own opinion to start a discussion.

Rule 8: Respect your account
- Do not share your account information with other individuals. You will be held responsible for any rules violations that occur under your account.
- Do not create new accounts or use other tricks to avoid suspensions or bans.
- Do not create ‘sock puppet’ accounts – multiple accounts created just so that you can agree with yourself and make it seem like your ideas have more support than they do.
- Never include your e-mail address or any other personal information in posts.

Rule 9: Respect the Moderators
- Do not post using the color red. This color is reserved for moderators.
- Do not impersonate moderators. Do not claim to speak for the moderators.

Rule 10: Respect the decisions of the moderators
- The moderation teams reserves the right to warn, suspend, or permanently ban users judged to be acting against the spirit of the rules, even if the user is following the letter of the rules.
- Do not argue with moderators about moderator decisions. You can disagree with a moderator’s opinions, just like any other poster, but when they post moderator actions in red text, it is considered final.
- Moderators have no access to your game account. If you have an issue you must contact customer service.

Generally, BE NICE. There is nothing wrong with being nice to each other.
See more
See less

Monster codes have been changed

  • Filter
  • Time
  • Show
Clear All
new posts

  • Monster codes have been changed

    If you check Monsters on the Public list, you'll see that monsters that used to have ":101" at the end of the code now have ":145" (I haven't checked all mpool=101 monsters though).
    In the same way, Thanatos of Fire and Ice which used to be :100 is now :144.
    Other monster types seem to have kept the part of their code related to their mpool (:1, :2, :3, and probably :4). Though once again, I've only checked a few.

    However that's not the only change. The full Monster code has been changed. At least for me. It's not the same anymore, at all.

    Will it now change with each new monster summon, as it has been asked in the past?
    Have the codes been changed (or much better, the code system reworked) because the devs are trying to block scripters, with all the Praetorian and baby Mephs discussion going on recently?
    Edit: Although I suppose if only the codes change and not the links, nothing will change in that regard.

    This change was reported because someone on Discord 4 hours ago couldn't share his Cronus Astaroth because the monster code was not working. It was db94f51:145. Now it has changed again and it's working (418ccch:145 - the monster is public so I don't think it's an issue sharing it right now, and I can edit the code out on a later day if necessary).

    So 4 hours ago, I randomly chose a few monsters on the public list, and the two :145 codes I copied from public monsters weren't working, while the few :3 and :1 codes I tested worked.
    It was very few tests, so it might have been a coincidence, however there were definitely codes that weren't working.
    Now just a few minutes ago I tried testing a few other :145 mobs from the public list and the codes worked. Again, very few tests, idk if it's fixed for all monsters.
    I also don't know why changing :101 to :145.

    I also tested a few links (using the at-first-not-working Astaroth) to see if things had changed.

    The default link of the monster was still with mpool=101: (casuser edited out so it's not a working link)

    Changing it to mpool=144 and mpool=2 still redirected to the Astaroth, for some reason (not so surprising for mpool=2 since for quite some time now we can't summon Epic Team monsters and mpool=101 monsters at the same time).
    mpool=1, 3 and 100 don't redirect to it.
    And then I tried mpools that so shouldn't exist.
    5 doesn't redirect to an active monster, but 6, or 65 (chosen randomly), redirect to this Astaroth.
    Didn't feel like trying hundreds of numbers so I stopped there.

    No idea how to make sense of all this TBH.
    Last edited by gogoo; 10-23-2019, 01:12 PM.

  • #2
    So it appears Monsters "caught in the middle of the change" have some issues, while monsters summoned after the change don't.

    For instance, I got a report that 2 players who had previously summoned mpool=101 monsters couldn't summon a mpool=2 monster.
    However, 2 other players who had no ongoing monsters prior to the change were then able to summon from all 4 main monster pools (1, 2, 3, 101, others haven't been tested).
    So it appears there is no more overlap between mpool=101 and mpool=2!

    Furthermore, the links working weirdly may also be only for monsters "caught in the middle".

    The link for the Astaroth in the first post only truly works when using mpool=101.
    It's a little weird. By "truly works" I mean this: when you use the mpool=101 link, it show you the monster normally, with all attackers in the Activity leaderboard. But if you use any other mpool that still directs to the Astaroth, it shows it with only 2 Attackers, and a lot more HP remaining that what it actually has. It was probably the state of the monster before the code change happened.
    I tried attacking it, and it "updates" it and shows the monster in its current state (but if you reload the link with a different mpool than 101, it shows you again the old state).


    • #3
      Current Alperon on I'm on (not public) summoned with the old link, now working fine with the new link ending in 145
      * Stealth Moderator *


      • #4
        Maybe I'll be lucky enough to be able to summon monsters normally again now. That would be great!
        Come say hello FB link
        Web 3 Keep link

        Originally posted by VersionsOfViolence
        #1 it's not nice to be mean to ppl
        #2 nobody cares about da wilbsta


        • #5
          Bookmarks are still working


          • #6
            Monster codes are still not unique for each summon. The user portion is the same for each of the 4 types.


            • #7
              I just summoned a Cronus Astaroth, followed by an Emerald Dragon

              I don't know if this code change fixed or modified anything besides that, but that's great already!


              • #8
                Hello there

                I'm trying to hit 2 Alexandras for a chaos gem requirement, and both of them are behaving strangely. After every hit on web3, it goes to a blank black screen, and if you reload the CA home page again and navigate to the monster, it shows added damage, but then when you hit again it goes to the black screen. So you can accrue damage, but you have to go through the process of hitting, reloading home page, navigating to monster... I thought it might be a bug for web3, so I tried it on iOS, and the Alexes are shown in my monster list, but when you click on them, it says 'Monster not found' but then loads up the monster image with the attack buttons (but they don't do anything when you try and click on them).

                I think this change to monsters might have caused some bugs...? Is anybody else experiencing this? (sorry if this is old news or talked about in another thread).


                • #9
                  Yes, just seen that myself as well


                  • #10
                    Maybe It is because of this? Anything to do with stamina the page will Show only blank Page. I can Not Battle or Hit Monsters


                    • #11
                      Looks like it had nothing to do with the code change, since it also affected Battles.

                      Also looks like the bugs didn't last too long, fortunately

                      @mods could you maybe move the posts to this thread?


                      • #12
                        Originally posted by gogoo View Post
                        I just summoned a Cronus Astaroth, followed by an Emerald Dragon

                        I don't know if this code change fixed or modified anything besides that, but that's great already!
                        Well that didn't last long, or it was just a fluke maybe.

                        In any case, yesterday it didn't let me summon an Emerald Dragon because of my Cronus Astaroth.


                        • #13
                          the only change I see and have verified so far is that the part before the ":" has been re-randomized for each player but is consistent throughout the different mpools and multiple monsters in the same mpool

                          the monster link is still the same because the user id is...obviously still the same

                          I guess if you were relentlessly gate crashed by guildemesh previously you now might have a reprieve

                          Another idea is that since the devs seem to be doing regular maintenance they can reset the monster codes each time, can't hurt
                          Last edited by LordFa9; 10-31-2019, 03:42 AM.


                          • #14
                            Well they did not fix the issue of monsters summon slots conflict. I tried to summon a Vargulis and got this message instead:

                            You have already summoned a monster, The Ancient Sea Serpent, or the timer has not run out on the previous monster you have summoned, try again in 26 hour(s) Go to the Monster Battle Page to engage your summoned bosses and monsters.

                            Nemo vir est qui mundum non reddat meliorem.