Jump to content
Currently supported: All versions

Where to view update progress?

Torojima

By Torojima
in General Discussion

 Share

Recommended Posts

Xfel Tree Puncher

Xfel

Posted
Posted

The latest build (183) is missing the server-side ModLoader files. Additionally, I noted that in ForgeHooks line 222, a modloader method is used even though this would not be necessairy.

  • Replies 117
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Posted Images

Xfel Tree Puncher

Xfel

Posted
Posted

Er... no. At least not in the version I have. The common folder of fml only conatins the cpw.mods package. The ML classes for the client are in the client folder. The server folder doesn't exist.

LexManos Reality Controller

LexManos

Posted
Posted

Delete your server project

Everything was merged to client.

If you want to debug the Dedi-server environment, run MinecraftServer.main.

 

Nothing is missing, it was one on purpose to make everything a unified codebase.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

ShetiPhian Creeper Killer

ShetiPhian

Posted
Posted

Hey Lex I have a quick question for you.

 

The chunkX and chunkZ values from ModLoader's generateSurface are 16x bigger then the ones from IWorldGenerator

 

Am I correct in assuming this is intentional because it is providing chunk coordinates (as implied by the name) instead of block coordinates like mod loader?

LexManos Reality Controller

LexManos

Posted
Posted

Would sound like it yes.

ModLoader providing block coords is rather.. stupid...

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

LexManos Reality Controller

LexManos

Posted
Posted

With the imminent drop of 1.3.2 we've decided not to release officially for 1.3.1. {Though as you can see, there are plenty of builds that work for 1.3.1}

Current jenkins builds are for 1.3.2, so get to testing.

As long as we get good feedback. I plan on making a official release when 1.3.2 drops.

 

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

SanAndreaP World Shaper

SanAndreaP

Posted
Posted
  On 8/15/2012 at 10:45 AM, LexManos said:

...

Current jenkins builds are for 1.3.2, so get to testing.

...

 

So we should use the curr. 1.3.2 pre-release for the curr. Jenkins build?

 

EDIT: nvm. found out the answer ^.^

Don't ask for support per PM! They'll get ignored! | If a post helped you, click the "Thank You" button at the top right corner of said post! |

mah twitter

  Quote

This thread makes me sad because people just post copy-paste-ready code when it's obvious that the OP has little to no programming experience. This is not how learning works.

jex Tree Puncher

jex

Posted
Posted

1.3.2 is out  ;D ;D ;D ;D so that means forge will probably be out soon.

 

DISCLAIMER, I am in no way related to anything involving forge development so my views could be wrong and not reflect the views of the developers.

Viper283 Creeper Killer

Viper283

Posted
Posted
  On 8/16/2012 at 4:50 PM, jex said:

1.3.2 is out  ;D ;D ;D ;D so that means forge will probably be out soon.

 

DISCLAIMER, I am in no way related to anything involving forge development so my views could be wrong and not reflect the views of the developers.

 

don't worry about it, forge for 1.3.2 if officially out, just look at the thread

jex Tree Puncher

jex

Posted
Posted
  On 8/16/2012 at 9:31 PM, Viper283 said:

  Quote

1.3.2 is out  ;D ;D ;D ;D so that means forge will probably be out soon.

 

DISCLAIMER, I am in no way related to anything involving forge development so my views could be wrong and not reflect the views of the developers.

 

don't worry about it, forge for 1.3.2 if officially out, just look at the thread

it wasn't out when I said it I checked.

  • 2 weeks later...
LexManos Reality Controller

LexManos

Posted
Posted

There was never a official release for 1.3.1, there are a few early builds of 4.x that are 1.3.1

1.3.2 came out with almost no delay after 1.3.1 so if anyone devs a mod for 1.3.1, and not 1.3.2 they are.. well.. stupid.

However, we do not support it because its old.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing

Announcements



  • Recently Browsing

    • No registered users viewing this page.

  • Posts

    • bkbenji
      OpenAL.dll issue (causing crash)

      By bkbenji · Posted

      Is there a fix for this issue? I have tried reinstalling OpenAL.dll, switching Java versions, and even muting my game when it launched, but all of these attempts have resulted in my game crashing nonetheless. I have been dealing with this issue for approximately a week straight. I have not changed any sound settings, so I am very confused. Full Code: https://gnomebot.dev/paste/mclogs/beEBzpm "4/16/2025 12:16:30 AM 1000 Error Faulting application name: javaw.exe, version: **.**.**.**, time stamp: 23 0xd75c3041 24 Faulting module name: OpenAL.dll, version: **.**.**.**, time stamp: 0x647635a125 Exception code: 0xc0000409 26 Fault offset: 0x00000000000a2b05 27 Faulting process id: 0x10A0 28 Faulting application start time: 0x1DBAE81D04A6F2F 29 Faulting application path: C:\Users\********\curseforge\minecraft\Install\java30 \java-runtime-delta\bin\javaw.exe 31 Faulting module path: C:\Users\********\curseforge\minecraft\Install\natives\n32 eoforge-21.1.148\OpenAL.dll 33 Report Id: 28552180-f359-40cc-adeb-08dada7e99d8 34 Faulting package full name: 35 Faulting package-relative application ID:" Any sort of insight would be greatly appreciated, it's giving me a headache.
    • Calcifer
      I can't get this modpack running.

      By Calcifer · Posted

      I'm new to this, if that wasn't obvious. My friend and I are trying to make a modpack for 1.19.2. I've made a modpack previously with 0 issues before and many of the same mods. However, I can't seem to find the issue when trying to load up his new modpack.   Any help would be greatly appreciated.
    • SPROUTBAKES
      blocks addon

      By SPROUTBAKES · Posted

      BLOCK
    • PhysicalJP
      Minecraft modpack crashing on create world.

      By PhysicalJP · Posted

      Im trying to make a customized modpack for just myself using the atm9 modpack as a base. It was working till recently, when curseforge force updated all the mods in the pack. Currently every time I get to the main menu I try and create a world in single player and it just says saving world. then generates a crash report.    Crash Report: https://pastebin.com/xXESPfJs   Latest Log Part 1: https://pastebin.com/Cb2VpUyr  Part 2: https://pastebin.com/9SWVn4Dx
    • Thargor
      Minecraft Crashing upon joining save/server or when placing specific blocks

      By Thargor · Posted

      Okay, for him the config file looked like this: flywheel-client.toml: #Select the backend to use. Set to "DEFAULT" to let Flywheel decide. backend = "DEFAULT" #Enable or disable instance update limiting with distance. limitUpdates = true #The number of worker threads to use. Set to -1 to let Flywheel decide. Set to 0 to disable parallelism. Requires a game restart to take effect. #Range: -1 ~ 12 workerThreads = -1 #Config options for Flywheel's built-in backends. [flw_backends]     #How smooth Flywheel's shader-based lighting should be. May have a large performance impact.     #Allowed Values: FLAT, TRI_LINEAR, SMOOTH, SMOOTH_INNER_FACE_CORRECTED     lightSmoothness = "SMOOTH" There was no "INSTANCING", so we changed "DEFAULT" to "OFF", but this didn't help. Changing it to "INSTANCING" didn't work as well.

  • Topics

×
×
  • Create New...

Important Information

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

  I accept