Jump to content
Please read the rules and FAQ before starting a new topic
Currently supported: All versions

Execution failed for Task "decompileMC" Java heap space + Unable daemon process

Furkos

By Furkos
in Support & Bug Reports

 Share

Recommended Posts

Furkos Tree Puncher

Furkos

Posted
Posted

Hey guys,

 

I wanted to start programming a mod for Minecraft viá Java.

I followed the instruction and downloaded Java JDK 7, Eclipse & Forge.

 

Everything went fine, but when I opened CMD in the Forge Folder and typed :

"gradlew setupDecompWorkspace" it gave me an error after 3-4 minutes.

 

The error said : "decompileMc FAILED;

FAILURE: Build failed with an exception.

* What went wrong: Execution failed for task ':decompileMC'.

> Java heap space"

 

After google'ing a couple of minutes I found some ways to solve this problem.

Next I wrote "gradlew -Dorg.gradle.jvmargs=-Xmx3072m setupDecompWorkspace"

 

I got 16gb workspace so this shouldn't be a big problem, right ?

Now the "Java heap space"-error was solved, but a new error occured.

The new error said : "unable to start the daemon process"

 

So I googled for a solution for this problem.

It said I should go to C:\Users\MyUser and delete the .gradle folder. I followed the instruction but it gave me the same error over and over,

no matter how much heap space I gave Java or how often I tried to start the decompileMc new there were always the same 2 errors.

 

Any idea, what I could do ?

 

Thanks for your help and sorry for the bad english.

 

 

Furkos

Link to comment
Share on other sites
Killer7TNT Tree Puncher

Killer7TNT

Posted
Posted

I have the same problem.

 

(my results)

 

 

This set of MCP mappings was designed for MC 1.8.8. Use at your own peril.This set of MCP mappings was designed for MC 1.8.8. Use at your own peril.

 

#################################################

        ForgeGradle 2.1-SNAPSHOT-9fb7522       

  https://github.com/MinecraftForge/ForgeGradle 

#################################################

              Powered by MCP unknown             

            http://modcoderpack.com           

        by: Searge, ProfMobius, Fesh0r,       

        R4wk, ZeuX, IngisKahn, bspkrs         

#################################################

:deobfCompileDummyTask

:deobfProvidedDummyTask

:getVersionJson

:extractUserdev UP-TO-DATE

:extractDependencyATs SKIPPED

:extractMcpData SKIPPED

:extractMcpMappings

:genSrgs SKIPPED

:downloadClient SKIPPED

:downloadServer SKIPPED

:splitServerJar SKIPPED

:mergeJars SKIPPED

:deobfMcSRG SKIPPED

:decompileMc FAILED

 

FAILURE: Build failed with an exception.

 

* What went wrong:

Execution failed for task ':decompileMc'.

> GC overhead limit exceeded

 

* Try:

Run with --info or --debug option to get more log output.

 

* Exception is:

org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':decompileMc'.

at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:69)

at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:46)

at org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:35)

at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:64)

at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)

at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:52)

at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)

at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:53)

at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)

at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:203)

at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:185)

at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:62)

at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:50)

at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor.process(DefaultTaskPlanExecutor.java:25)

at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter.execute(DefaultTaskGraphExecuter.java:110)

at org.gradle.execution.SelectedTaskExecutionAction.execute(SelectedTaskExecutionAction.java:37)

at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)

at org.gradle.execution.DefaultBuildExecuter.access$000(DefaultBuildExecuter.java:23)

at org.gradle.execution.DefaultBuildExecuter$1.proceed(DefaultBuildExecuter.java:43)

at org.gradle.execution.DryRunBuildExecutionAction.execute(DryRunBuildExecutionAction.java:32)

at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)

at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:30)

at org.gradle.initialization.DefaultGradleLauncher$4.run(DefaultGradleLauncher.java:155)

at org.gradle.internal.Factories$1.create(Factories.java:22)

at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)

at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:52)

at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:152)

at org.gradle.initialization.DefaultGradleLauncher.access$200(DefaultGradleLauncher.java:33)

at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:100)

at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:94)

at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)

at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:62)

at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:94)

at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:83)

at org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:94)

at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28)

at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)

at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:43)

at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:28)

at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:77)

at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:47)

at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:51)

at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:28)

at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:43)

at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:170)

at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:237)

at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:210)

at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35)

at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)

at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:206)

at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169)

at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)

at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)

at org.gradle.launcher.Main.doAction(Main.java:33)

at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)

at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:54)

at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:35)

at org.gradle.launcher.GradleMain.main(GradleMain.java:23)

at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:30)

at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:127)

at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)

Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded

at org.jetbrains.java.decompiler.struct.StructMember.readAttributes(StructMember.java:50)

at org.jetbrains.java.decompiler.struct.StructMethod.readAttribute(StructMethod.java:105)

at org.jetbrains.java.decompiler.struct.StructMember.readAttributes(StructMember.java:57)

at org.jetbrains.java.decompiler.struct.StructMethod.<init>(StructMethod.java:78)

at org.jetbrains.java.decompiler.struct.StructClass.<init>(StructClass.java:116)

at org.jetbrains.java.decompiler.struct.StructClass.<init>(StructClass.java:75)

at org.jetbrains.java.decompiler.struct.StructContext.addArchive(StructContext.java:167)

at org.jetbrains.java.decompiler.struct.StructContext.addSpace(StructContext.java:100)

at org.jetbrains.java.decompiler.struct.StructContext.addSpace(StructContext.java:78)

at org.jetbrains.java.decompiler.main.decompiler.BaseDecompiler.addSpace(BaseDecompiler.java:36)

at net.minecraftforge.gradle.tasks.ApplyFernFlowerTask.applyFernFlower(ApplyFernFlowerTask.java:98)

at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75)

at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:226)

at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:219)

at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:208)

at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:585)

at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:568)

at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80)

at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61)

at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:46)

at org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:35)

at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:64)

at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)

at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:52)

at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)

at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:53)

at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)

at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:203)

 

 

BUILD FAILED

 

Total time: 6 mins 23.678 secs

 

Link to comment
Share on other sites
perromercenary00 Dragon Slayer

perromercenary00

Posted
Posted

 

create a plain text file,

name it

gradle.properties

inside this file write 

org.gradle.jvmargs=-Xmx2048M

 

this will set the memory limit to 2G

 

save it and drop it inside the forge folder, there next to the build.gradle file from your mod

 

that solve this problem for my, but I still stuck whith other two problems,  may you run into them in short

 

Link to comment
Share on other sites
  • 7 months later...
robijnvogel Tree Puncher

robijnvogel

Posted
Posted

Sorry for the necro, but I have some additional information that people who find this via Google, like me, could find useful:

 

For me it wouldn't let me set the memory flag higher than 1GB, because it used my 32-bit Java Runtime as default.

Therefore, the content of my gradle.properties file needed to be:

org.gradle.java.home = C:/Program Files/Java/jdk1.8.0_101
org.gradle.jvmargs = -Xmx2g

 

I actually needed more than 2 GB of memory for my particular Gradle daemon though.

I walk amongst titans.

Link to comment
Share on other sites
  • 2 years later...
WaningMatrix Tree Puncher

WaningMatrix

Posted
Posted (edited)

Sorry for necroposting but I know a lot of people get this error while setting up  

gradlew setupDecompWorkspace

Firstly I'd suggest you to follow ForgeDocs and use intelliJ to create your mods. Follow the whole documentation page and if you still get the " :decompileMC  Ran out of Java heapspace " (on step 5 in docs) error. All you have to do is to click on Gradle on the righthandside in intelliJ Idea and click on Gradle settings (gear icon) and set the Gradle VM arguments to  

-Xmx1400M

Check below for pictures explaining the process.unknown.png

 

Make sure you have at least  2 gigs on RAM allocated to JVM. You can check whether its fine or not by going to 

Start Menu> Search Configure Java and open it> In the Java tab click on View> Set the Runtime Parameters to -Xmx3G or -Xmx2G based on how much RAM you have on your computer, 2G should be also fine.

unknown.png

And now go to intelliJ and in the Local Terminal just type in 

gradlew setupDecompWorkspace

Allow it ~5 to 15 minutes to setup the workspace and you should be good to go! :)

Happy coding!

Edited by WaningMatrix
Link to comment
Share on other sites
DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

Please don't necropost, and no saying "sorry for" does not excuse you.

Please don't set the Xmx in your ide or on your system every (modern) Forge MDK ships with a gradle.properties that sets this for you.

If you are using an MDK that is old enough to not have this then know that you will not receive support on this forum.

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/: 100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing

Announcements



  • Recently Browsing

    • No registered users viewing this page.

  • Posts

    • RAJAHOKI
      SLOT BANK Lampung 🚀 slot maxwin akun pro kamboja Anti Rungkat

      By RAJAHOKI · Posted

      Akun Pro Kamboja adalah pilihan terbaik bagi Anda yang mencari pengalaman bermain slot Maxwin dengan transaksi mudah menggunakan Bank Lampung. Berikut adalah beberapa alasan mengapa Anda harus memilih Akun Pro Kamboja: Slot Maxwin Terbaik Kami menyajikan koleksi slot Maxwin terbaik yang menawarkan kesenangan bermain dan peluang kemenangan besar. Dengan fitur-fitur unggulan dan tema-tema menarik, setiap putaran permainan akan memberikan Anda pengalaman yang tak terlupakan. Transaksi Mudah dengan Bank Lampung Kami menyediakan layanan transaksi mudah melalui Bank Lampung untuk kenyamanan dan keamanan Anda. Dengan proses yang cepat dan efisien, Anda dapat melakukan deposit dan penarikan dana dengan lancar dan tanpa hambatan. Anti Rungkat Akun Pro Kamboja memberikan jaminan "anti rungkat" kepada para pemainnya. Dengan fitur ini, Anda dapat merasakan sensasi bermain dengan percaya diri, karena kami memastikan pengalaman bermain yang adil dan menyenangkan bagi semua pemain.  
    • admin 2
      BINGO188 | SITUS SLOT GARANSI KEKALAHAN 100 SALDO KEMBALI JIKA KALAH BEBAS IP TANPA TO | SERVER THAILAND PALING GACOR HARI INI

      By admin 2 · Posted

      BINGO188: Destinasi Terbaik untuk Pengalaman Slot yang Terjamin Selamat datang di BINGO188, tempat terbaik bagi para pecinta slot yang mencari pengalaman bermain yang terjamin dan penuh kemenangan. Di sini, kami menawarkan fitur unggulan yang dirancang untuk memastikan kepuasan dan keamanan Anda. Situs Slot Garansi Kekalahan 100 Kami memahami bahwa kadang-kadang kekalahan adalah bagian dari permainan. Namun, di BINGO188, kami memberikan jaminan keamanan dengan fitur garansi kekalahan 100. Jika Anda mengalami kekalahan, kami akan mengembalikan saldo Anda secara penuh. Kemenangan atau uang kembali, kami memastikan Anda tetap merasa aman dan nyaman. Bebas IP Tanpa TO Nikmati kebebasan bermain tanpa batasan IP dan tanpa harus khawatir tentang TO (Turn Over) di BINGO188. Fokuslah pada permainan Anda dan rasakan sensasi kemenangan tanpa hambatan. Server Thailand Paling Gacor Hari Ini Bergabunglah dengan server terbaik di Thailand hanya di BINGO188! Dengan tingkat kemenangan yang tinggi dan pengalaman bermain yang lancar, server kami dijamin akan memberikan Anda pengalaman slot yang tak tertandingi. Kesimpulan BINGO188 adalah pilihan terbaik bagi Anda yang menginginkan pengalaman bermain slot yang terjamin dan penuh kemenangan. Dengan fitur situs slot garansi kekalahan 100, bebas IP tanpa TO, dan server Thailand paling gacor hari ini, kami siap memberikan Anda pengalaman bermain yang aman, nyaman, dan menguntungkan. Bergabunglah sekarang dan mulailah petualangan slot Anda di BINGO188!
    • RAJAHOKI
      SLOT BANK panin 🚀 SLOT Gacor Pgsoft alibabaslot AKURAT

      By RAJAHOKI · Posted

      Mengapa Memilih AlibabaSlot? AlibabaSlot adalah pilihan terbaik bagi Anda yang mencari slot gacor dari Pgsoft dengan transaksi mudah menggunakan Bank Panin. Berikut adalah beberapa alasan mengapa Anda harus memilih AlibabaSlot: Slot Gacor dari Pgsoft Kami menyajikan koleksi slot gacor terbaik dari Pgsoft. Dengan fitur-fitur unggulan dan peluang kemenangan yang tinggi, setiap putaran permainan akan memberikan Anda kesenangan dan keuntungan yang maksimal. Transaksi Mudah dengan Bank Panin Kami menyediakan layanan transaksi mudah melalui Bank Panin untuk kenyamanan dan keamanan Anda. Dengan proses yang cepat dan efisien, Anda dapat melakukan deposit dan penarikan dana dengan lancar dan tanpa masalah.  
    • TileEntity
      Exception in server tick loop

      By TileEntity · Posted

      Delete the jei-server.toml file in your config folder and test it again
    • TileEntity
      My Forge 1.20.1 wont load even without mods

      By TileEntity · Posted

      java.util.ConcurrentModificationException at java.base/java.util.HashMap.computeIfAbsent(Unknown Source) at Genesis//com.moonsworth.lunar. ... Looks like an issue with the Launcher - Make a test with another Launcher like MultiMC, AT Launcher or Technic Launcher or try the original one

  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept