The Installer from the current SVN mades no visible changes to the source code. The forge folder isn't there, no added files, nothing.
Took a look at a couple files and didn't find the forge hooks one would expect.
I tried two different files to run to install it. Setup.bat doesn't do much at all. It skips a bunch of things it can't find then recompiles the client, then some more misc actions.
Install.bat in the install folder pretends to patch like it used to in 1.8.1 but nothing actually happens to the code.
So.. the current SVN doesn't seem to be usable or I'm missing something.
The SVN isn't meant for the end user, or even the end mod maker. It's meant for working on forge.
Checkout the trunk/root branch to your MCP/forge
setup.bat creates 2 folders a src_base and a src_dev in the main MCP folder
Load up eclipse in the MCP workbench
Go to file -> Import -> projects from file system (or something like that)
browse to MCP/forge
And add the projects in there.
Then you can work in the forge_client/forge_server projects to work on forge. THE SVN IS NOT FOR MOD MAKERS, OR MOD USERS. IT'S FOR WORKING ON FORGE ITSELF
Don't expect to download the svn have be able to port your mod.
There are other things you need to work with, like the reliance on cygwin for a few of the scripts, and a few hardcoded paths. As I am stressing again, its NOT for mod makers.
The SVN isn't meant for the end user, or even the end mod maker. It's meant for working on forge.
Checkout the trunk/root branch to your MCP/forge
setup.bat creates 2 folders a src_base and a src_dev in the main MCP folder
Load up eclipse in the MCP workbench
Go to file -> Import -> projects from file system (or something like that)
browse to MCP/forge
And add the projects in there.
Then you can work in the forge_client/forge_server projects to work on forge. THE SVN IS NOT FOR MOD MAKERS, OR MOD USERS. IT'S FOR WORKING ON FORGE ITSELF
Don't expect to download the svn have be able to port your mod.
There are other things you need to work with, like the reliance on cygwin for a few of the scripts, and a few hardcoded paths. As I am stressing again, its NOT for mod makers.
The Installer from the current SVN mades no visible changes to the source code. The forge folder isn't there, no added files, nothing.
Took a look at a couple files and didn't find the forge hooks one would expect.
I tried two different files to run to install it. Setup.bat doesn't do much at all. It skips a bunch of things it can't find then recompiles the client, then some more misc actions.
Install.bat in the install folder pretends to patch like it used to in 1.8.1 but nothing actually happens to the code.
So.. the current SVN doesn't seem to be usable or I'm missing something.
Works fine here make sure you are putting the forge folder in your MCP workspacce (like you would with the release).
The SVN isn't meant for the end user, or even the end mod maker. It's meant for working on forge.
Checkout the trunk/root branch to your MCP/forge
setup.bat creates 2 folders a src_base and a src_dev in the main MCP folder
Load up eclipse in the MCP workbench
Go to file -> Import -> projects from file system (or something like that)
browse to MCP/forge
And add the projects in there.
Then you can work in the forge_client/forge_server projects to work on forge. THE SVN IS NOT FOR MOD MAKERS, OR MOD USERS. IT'S FOR WORKING ON FORGE ITSELF
Don't expect to download the svn have be able to port your mod.
There are other things you need to work with, like the reliance on cygwin for a few of the scripts, and a few hardcoded paths. As I am stressing again, its NOT for mod makers.
... i have never once needed cygwin to use the SVN unless its something you have changed recently, nor have i had problems with hardcoded paths if this is a new thing then it is true that forge is going down hill. ( i just downloaded and installed the svn with 0 errors without cygwin installed and in a custom path so im not sure were you are coming from here)
The SVN is for when ever the hell the community wants to do with it, if they want to start poring mods over using it then that's up to them, it helps forge because it finds bugs and helps the modders because they don't have to wait for forge to come out. (note that someh4x0r has already found several)
I can agree that you cant just download it and expect to use it like the normal release but i also have faith that most real modders can handle the little errors you sometimes get with the svn, hell you get far more using the release after a few MCP updates.
I will ask this if its not for mod makers who the hell is it for? Should we just let you sit around and trust that you will find every bug? Should we just ignore the development of an api that our mods rely on?
When did forge become about a few peoples egos and not about the community? I can see why FC ragequit. (Excluding SpaceToad here never had a problem with him)
I have posted an Idea in the Mod Ideas sub-forum regarding a Unified Modding System. I would hope that everyone, especially coders, would check it out and contribute towards seeing if it or something similar could be achieved, helping all of us in the community for the long-term while doing it.
This is a great asset to the modding community. I believe it makes up for a weakness in the Vanilla Minecraft programming. I am admittedly ignorant of practically all coding and programming knowledge. However, in the small part that I do understand, what you've done here is awesome.
I've used this along with RedPower2, BuildCraft, IndustrialCraft2 and Better Than Wolves. Until and unless Mineraft incorporates the possibilities that the Forge adds to the game, this is an almost essential part of my Minecraft gaming experience. So, instead of just asking or insisting that you update for 1.0. I have left you my best assessment and praise of your work with this project. All that and also THANK YOU, for what you've done here.
I simply can't wait for Minecraft Forge to update! Thank you, Eloraam and Spacetoad, for everything. Keep up the good work and please don't over-exert yourselves
I can agree that you cant just download it and expect to use it like the normal release but i also have faith that most real modders can handle the little errors you sometimes get with the svn, hell you get far more using the release after a few MCP updates.
I will ask this if its not for mod makers who the hell is it for? Should we just let you sit around and trust that you will find every bug? Should we just ignore the development of an api that our mods rely on?
When did forge become about a few peoples egos and not about the community? I can see why FC ragequit. (Excluding SpaceToad here never had a problem with him)
-snip-
-snipped for TL;DR-
I think he was mostly aiming that towards people intent on using the SVN in place of a stable release. It's not a point of contention that the Forge is 'for everyone, by everyone' but please, aim the pejorative elsewhere.
The warning was clearly well-meant.
EDIT:
"Don't expect support/100% success from something I have just publicly announced isn't for end-use and is absolutely guaranteed unfinished until noted otherwise"
I read that when I read LexManos's statement and I approve of the message wholeheartedly. There's no ego in telling people not to do something that isn't wise to do. There's ego in suggesting "most modders know what they're doing and can get around the little errors" like it's no big deal, when the fact is modders like me wouldn't waste their time working on any given release without some guarantee of stability, or furthermore - why bother updating anything when the player's can't even play it yet? To get a head start? Clearly if the Forge port was finished, we'd have the Client and the Source right now, so obviously something is missing.
It stands to reason it's not a great idea to use this in its unfinished form. I'm going to go with waiting.
EDIT 2:
After further consideration of pigalot's definition and my stance on the SVN, I have come to the conclusion that I'm not a real modder.
I know I should wait and all and I'm sorry for asking but ETA on release or just a percentage of porting done like 60% done maybe or w/e just to give us a feel of possible release?
Rollback Post to RevisionRollBack
GENERATION 21: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
There would be little point in putting out an unfinished version expect for the reason already given, to test it. For those modders who are willing, they can put forward efforts to test the areas of forge they know, or don't know, how to test in order to give the feedback that is asked.
Me, I'm a novice at best but I like to try and help out so I gave it a shot and reported my findings when I did so. When I can puzzle the response I got together I can figure out where to go from there. I mean when as I do tend to be busy with one thing or another. RL gets in the way. It will make me a better modder and coder for taking this and putting it together.
You are right and Lexmanos was of course right on this point. The SVN is not meant for general release and just isn't for modders, its for working on the Forge.
Thats it, its for working on the Forge.. Whether or not you want to put forward some effort in helping the Forge progress is your choice. Working with the SVN right now should of course, be with only the purpose of helping to update the Forge. Not with wholly the mindset of trying to mod with it. Then I come to the conclusion that the best way to test the Forge is to use the Forge. Which means to mod.
Of course, this thread keeps getting and will continue to keep getting people who want the Forge back, and some might try to use the SVN to mod and may even try to release the mod. That is where they would be wrong, releasing a mod dependent on the SVN Forge.
The IC2 forum has a 1.0.0 version out :ohttp://forum.industrial-craft.net/index.php?page=Thread&threadID=767
That's 1.0, the first version of IC2. I would say "Wow" if I was actually surprised.
EDIT:
Just to clarify, at the very top of the page you just linked:
"IndustrialCraft² recent version:: v1.23! (For Minecraft 1.8.1 Beta)"
If you give me your mailing address, I'll make you a big sign that says "Fail" on it for you to hang on your wall.
I think your end conclusion isn't clear, x3n.There would be little point in putting out an unfinished version expect for the reason already given, to test it. For those modders who are willing, they can put forward efforts to test the areas of forge they know, or don't know, how to test in order to give the feedback that is asked.Me, I'm a novice at best but I like to try and help out so I gave it a shot and reported my findings when I did so. When I can puzzle the response I got together I can figure out where to go from there. I mean when as I do tend to be busy with one thing or another. RL gets in the way. It will make me a better modder and coder for taking this and putting it together.You are right and Lexmanos was of course right on this point. The SVN is not meant for general release and just isn't for modders, its for working on the Forge.Thats it, its for working on the Forge.. Whether or not you want to put forward some effort in helping the Forge progress is your choice. Working with the SVN right now should of course, be with only the purpose of helping to update the Forge. Not with wholly the mindset of trying to mod with it. Then I come to the conclusion that the best way to test the Forge is to use the Forge. Which means to mod.Of course, this thread keeps getting and will continue to keep getting people who want the Forge back, and some might try to use the SVN to mod and may even try to release the mod. That is where they would be wrong, releasing a mod dependent on the SVN Forge.
True, but I found it a bit contentious that "real modders" would be willing to use this project and work around it as though its incumbent upon us to do so. Personally I'd prefer not to work towards something that might ultimately change [perhaps not, perhaps drastically] resulting in what would ultimately feel like lost time.
If it's your goal to progress the Forge development, this is the perfect tact to take. But to take offense to a simple precautionary statement, that was my main harp. I agree with you completely.
I wish FC and BTW all the best. We all benefit from good mods in the long run, even if they don't play nice with each other all the time. I bet that if nothing else we'll start to see some innovations in install-dir management mods.
Now, I'll be in my lair working on my 181 fabrication megacity. Things will update when they update. Begging won't change it. Better to use the time refining your designs and creating new ones!
Forge needs to be updated before Any other mod requiring Forge can update. IC has not updated, BC has not updated, nor has any other Forge required mod.
GIVE IT SOME TIME. Modding is no walk in the park. He has a life :tongue.gif:
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe SVN isn't meant for the end user, or even the end mod maker. It's meant for working on forge.
Checkout the trunk/root branch to your MCP/forge
setup.bat creates 2 folders a src_base and a src_dev in the main MCP folder
Load up eclipse in the MCP workbench
Go to file -> Import -> projects from file system (or something like that)
browse to MCP/forge
And add the projects in there.
Then you can work in the forge_client/forge_server projects to work on forge.
THE SVN IS NOT FOR MOD MAKERS, OR MOD USERS. IT'S FOR WORKING ON FORGE ITSELF
Don't expect to download the svn have be able to port your mod.
There are other things you need to work with, like the reliance on cygwin for a few of the scripts, and a few hardcoded paths. As I am stressing again, its NOT for mod makers.
Note that MSYS seems to work as well as Cygwin.
Unfortunately I've never gotten Eclipse to work correctly. It never seems to be able to figure out how to load the source provided by MCP correctly.
Works fine here make sure you are putting the forge folder in your MCP workspacce (like you would with the release).
... i have never once needed cygwin to use the SVN unless its something you have changed recently, nor have i had problems with hardcoded paths if this is a new thing then it is true that forge is going down hill. ( i just downloaded and installed the svn with 0 errors without cygwin installed and in a custom path so im not sure were you are coming from here)
The SVN is for when ever the hell the community wants to do with it, if they want to start poring mods over using it then that's up to them, it helps forge because it finds bugs and helps the modders because they don't have to wait for forge to come out. (note that someh4x0r has already found several)
I can agree that you cant just download it and expect to use it like the normal release but i also have faith that most real modders can handle the little errors you sometimes get with the svn, hell you get far more using the release after a few MCP updates.
I will ask this if its not for mod makers who the hell is it for? Should we just let you sit around and trust that you will find every bug? Should we just ignore the development of an api that our mods rely on?
When did forge become about a few peoples egos and not about the community? I can see why FC ragequit. (Excluding SpaceToad here never had a problem with him)
I use Netbeans so i can be much help there.
Thank you.
U.M.S. Thread
- The Cubic Chunks Mod is back! Be a part of it's rebirth and Development.
-- Robinton's Mods: [ Mirror ] for some of his Mods incl Cubic Chunks Mod, due to DropBox broken links.
- Dungeon Generator for the Open Cubic Chunks Mod
- QuickSAVE-QuickLOAD for the Open Cubic Chunks Mod
I've used this along with RedPower2, BuildCraft, IndustrialCraft2 and Better Than Wolves. Until and unless Mineraft incorporates the possibilities that the Forge adds to the game, this is an almost essential part of my Minecraft gaming experience. So, instead of just asking or insisting that you update for 1.0. I have left you my best assessment and praise of your work with this project. All that and also THANK YOU, for what you've done here.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-snipped for TL;DR-
I think he was mostly aiming that towards people intent on using the SVN in place of a stable release. It's not a point of contention that the Forge is 'for everyone, by everyone' but please, aim the pejorative elsewhere.
The warning was clearly well-meant.
EDIT:
"Don't expect support/100% success from something I have just publicly announced isn't for end-use and is absolutely guaranteed unfinished until noted otherwise"
I read that when I read LexManos's statement and I approve of the message wholeheartedly. There's no ego in telling people not to do something that isn't wise to do. There's ego in suggesting "most modders know what they're doing and can get around the little errors" like it's no big deal, when the fact is modders like me wouldn't waste their time working on any given release without some guarantee of stability, or furthermore - why bother updating anything when the player's can't even play it yet? To get a head start? Clearly if the Forge port was finished, we'd have the Client and the Source right now, so obviously something is missing.
It stands to reason it's not a great idea to use this in its unfinished form. I'm going to go with waiting.
EDIT 2:
After further consideration of pigalot's definition and my stance on the SVN, I have come to the conclusion that I'm not a real modder.
I don't think the tent mod would be updated as forge is still for Beta 1.8.1
-
View User Profile
-
View Posts
-
Send Message
Curse Premium'Industrail craft' hasn't updated. -edit for snark-
I could go on to say it's impossible for 'Industrail craft' to update, since it relies on Forge, and thus cannot update until this does.
Which begs the question:
"Really?"
meh i was wrong
There would be little point in putting out an unfinished version expect for the reason already given, to test it. For those modders who are willing, they can put forward efforts to test the areas of forge they know, or don't know, how to test in order to give the feedback that is asked.
Me, I'm a novice at best but I like to try and help out so I gave it a shot and reported my findings when I did so. When I can puzzle the response I got together I can figure out where to go from there. I mean when as I do tend to be busy with one thing or another. RL gets in the way. It will make me a better modder and coder for taking this and putting it together.
You are right and Lexmanos was of course right on this point. The SVN is not meant for general release and just isn't for modders, its for working on the Forge.
Thats it, its for working on the Forge.. Whether or not you want to put forward some effort in helping the Forge progress is your choice. Working with the SVN right now should of course, be with only the purpose of helping to update the Forge. Not with wholly the mindset of trying to mod with it. Then I come to the conclusion that the best way to test the Forge is to use the Forge. Which means to mod.
Of course, this thread keeps getting and will continue to keep getting people who want the Forge back, and some might try to use the SVN to mod and may even try to release the mod. That is where they would be wrong, releasing a mod dependent on the SVN Forge.
http://forum.industrial-craft.net/index.php?page=Thread&threadID=2144
Did you notice a trend of 1.0 1.15 and 1.23 on the public releases?
Just wonderin...
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThat's 1.0, the first version of IC2. I would say "Wow" if I was actually surprised.
EDIT:
Just to clarify, at the very top of the page you just linked:
"IndustrialCraft² recent version:: v1.23! (For Minecraft 1.8.1 Beta)"
If you give me your mailing address, I'll make you a big sign that says "Fail" on it for you to hang on your wall.
True, but I found it a bit contentious that "real modders" would be willing to use this project and work around it as though its incumbent upon us to do so. Personally I'd prefer not to work towards something that might ultimately change [perhaps not, perhaps drastically] resulting in what would ultimately feel like lost time.
If it's your goal to progress the Forge development, this is the perfect tact to take. But to take offense to a simple precautionary statement, that was my main harp. I agree with you completely.
LoL, maxell, rhetorical question is rhetorical.
Look at the link you provided. It says: IndustrialCraft² recent version:: v1.23! (For Minecraft 1.8.1 Beta)
It doesn't have a 1.0.0 version anywhere.
I wish FC and BTW all the best. We all benefit from good mods in the long run, even if they don't play nice with each other all the time. I bet that if nothing else we'll start to see some innovations in install-dir management mods.
Now, I'll be in my lair working on my 181 fabrication megacity. Things will update when they update. Begging won't change it. Better to use the time refining your designs and creating new ones!
http://www.minecraftforum.net/topic/1189510-minecraft-with-mead-meadcraft/
Forge needs to be updated before Any other mod requiring Forge can update. IC has not updated, BC has not updated, nor has any other Forge required mod.
GIVE IT SOME TIME. Modding is no walk in the park. He has a life :tongue.gif: