Announcement

Collapse
No announcement yet.

"Battle Royale" conflicts with an Epic IP

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    Hoping to see an explanation from Epic about this here. Sounds really upsetting.
    Regards,
    Kia.

    Comment


      #17
      Battle Royal is not IP'd to epic and this is so ridiculous. If this is not accepted by the marketplace team, I will be so disgusted.

      Comment


        #18
        This is amazing, to see Epic display such behavior after its being accused of similar from Bluehole. I thought the point of the motto was that we were all in this together not just here to give Epic a free lunch! My concern is this is just the beginning, that Epic will do similar to any title on UE4 that shows such success and their recent products show they arnt above going outside of UE4 community Gameloft style. Its so sad to see Epic, who we thought was our friend, treat its community with such disrespect, to act just like those big publishers they talk down about from their moral high ground of so called independence.

        I really hope you get this sorted and that its simply an error on the part of someone with a lack of understanding in the processes but with the pattern displayed by Epic (and Tencent) its hard to ignore this as a one off
        Last edited by MonsOlympus; 09-27-2017, 04:14 AM.

        Comment


          #19
          This is amazing

          Comment


            #20
            Wow Epic. Seriously? I want to hear a word from Epic regarding this.
            Shouldn't Japanese book writer sue Epic as well in this case?



            ToxinGaming your inbox disabled?

            I have been waiting for your BR asset to be approved to purchase on UE4 marketplace only, due to personal preference of having it for easy reuse in future. However, just saw your thread today and it is quite disappointing sadly.
            Last edited by unrealjin; 09-27-2017, 05:14 AM.

            Comment


              #21
              Tim Sweeney replied: https://twitter.com/TimSweeneyEpic/s...21636886106112
              Regards,
              Kia.

              Comment


                #22
                Kind of expected it to be a misunderstanding to be honest... never be too quick to jump the gun!

                Comment


                  #23
                  Hi everyone,

                  It is not our policy to restrict people from using Battle Royale. Using the term Battle Royale is fine because it has emerged as a video game genre.

                  The marketplace team has a longstanding policy that we won’t allow content on the marketplace if it’s listed in a way that is going to be confusing for buyers. “Paragon Rocks” would be an issue, for example, if we thought that people would think this was Epic created content.

                  However, we also let people use genre descriptors in their packs (Deathmatch, CTF, etc). I think this is the first time those two things have intersected, which is what caused the issue. It was the intent of the reviewer to recommend a change to the name in order to avoid confusion, but not require it. However, that doesn’t come across in the review, so we’ll update the review feedback to clearly flag when there’s a recommendation.

                  I would like to point out that the pack was not sent back to the seller specifically because of its use of “Battle Royale” in the title. The seller received feedback for other issues, and we’re working with him to have a successful release.

                  I apologize to ToxinGaming and our community that we’ve created this confusion and concern, and we’ll work to do better next time.

                  Thanks,
                  Josh

                  Comment


                    #24
                    Originally posted by Unreal_Josh View Post
                    Hi everyone,

                    It is not our policy to restrict people from using Battle Royale. Using the term Battle Royale is fine because it has emerged as a video game genre.

                    The marketplace team has a longstanding policy that we won’t allow content on the marketplace if it’s listed in a way that is going to be confusing for buyers. “Paragon Rocks” would be an issue, for example, if we thought that people would think this was Epic created content.

                    However, we also let people use genre descriptors in their packs (Deathmatch, CTF, etc). I think this is the first time those two things have intersected, which is what caused the issue. It was the intent of the reviewer to recommend a change to the name in order to avoid confusion, but not require it. However, that doesn’t come across in the review, so we’ll update the review feedback to clearly flag when there’s a recommendation.

                    I would like to point out that the pack was not sent back to the seller specifically because of its use of “Battle Royale” in the title. The seller received feedback for other issues, and we’re working with him to have a successful release.

                    I apologize to ToxinGaming and our community that we’ve created this confusion and concern, and we’ll work to do better next time.

                    Thanks,
                    Josh
                    Thank you for the update. All I wanted was some clarification. Yes, I am fixing my submission for the other issues.

                    Thanks again for looking into it.

                    Comment


                      #25
                      Hey toxingaming i buyed your template at gumroad with paypal but i don't got the download link or the receipe email your template would help me a lot because i m working on a advanced pubg with lot s of useful new functions in my plan your template was the base for my project so i really need it i m not so pro in programming i m a good designer and 3d modeler and i know enough of blueprints to change it how i need it pls pls answer me i m trying to contact you and gumroad for hours and didn't got anything i m working on a small 2 man indie team and our budget is close to 0

                      Comment

                      Working...
                      X