G
got_bored_again
Guest
Ok, so after almost a full year there is a back-port update (nice to see this old pack is still maintained) - but, sadly, and as always with major-updates, there some game-breaking bugs making it almost un-playable in the intended way.
Let me list just some of them:
1.) client menu still shows 1.2.0
2.) island_join command doesn't work anymore - it returns an error: "That player cannot be found"
3.) BC-iron/-gold gear achievement / crafting - if you put a casted gera into crafting slot - it shows the bc gear - but you can't take it - and therefore can't get the achievement - replacement with script-fix needed
4.) /help x still throws random exception cause some mods don't register help-handler correctly
I could go on as I'm sure if I'm just tryin to get all achievements I would find many more issues - maybe still not fixed bugs from 1.2.0. What really upsets me - and you banned me already 4 times for complaining this: Why your release packs with such game-breaking errors? I know it's really hard work and takes time even with creative to grind through all achievements - but at least they should be tested if all are obtainable.
Also the custom mods like the ftb-island-mod with its /island_x commands should also be tested. Why it throws an error like "player not found" when it's supposed to read the island-name from json and the linked coords and just perform a tp with current player using this command? I don't know the MC/Forge-api - but as I've seen in many java-forums (still wonder why beginners who thnik starting learning java by creating a minecraft-mod seems a good idea) there are instances of Player and Command - so on server-side there should something like Player player=Command.getPlayer() or some like this to get the Player-object for wich player used the command. Also: Throwable.printStackTrace() - at least server-console should output a meaningfull exception-stacktrace like for broken /help-handlers - or some way to enable debug mode - so that java-devs can understand what's wrong and can make good bug-reports.
Go ahead - ban me again for this complaining - but please: FIX IT! And please fix your lazy release-cycle to at least someone takes the time to grind the achievements and test every command BEFORE releasing it to public. There's something like unittests you can automate such testing. And building a testsuite one time saves lot more time against someone has to grind all again after rebuilding. Is it really that hard to follow common java development practices?
Yes - I know - you don'T feel responseable for errors made by mod-devs (when they would do such testing there would be a ton less errors) - but at least you could relay found issues to them instead of just ignoring bug-reports at all.
Do what ever you want with this report - maybe I should start by reverse-engineer FML/Forge and fix the base errors made there by cpw and player wich causes many errors in mods that have to be made just to able to compile against fml/forge api.
Oh - and what version was it again Jeb once announced official mod-api for? 1.7? FTB is one of the biggest packs - why you don't bother those guys over at where ever now the main dev is (is it really M$?). Why you don'T use your "power" and just say: Ok, we just stop supporting new versions until there is an official mod-api - cpw and player have this power - why they don't use it to make MC better in the first place?
To quote star wars: much to learn you have ...
Let me list just some of them:
1.) client menu still shows 1.2.0
2.) island_join command doesn't work anymore - it returns an error: "That player cannot be found"
3.) BC-iron/-gold gear achievement / crafting - if you put a casted gera into crafting slot - it shows the bc gear - but you can't take it - and therefore can't get the achievement - replacement with script-fix needed
4.) /help x still throws random exception cause some mods don't register help-handler correctly
I could go on as I'm sure if I'm just tryin to get all achievements I would find many more issues - maybe still not fixed bugs from 1.2.0. What really upsets me - and you banned me already 4 times for complaining this: Why your release packs with such game-breaking errors? I know it's really hard work and takes time even with creative to grind through all achievements - but at least they should be tested if all are obtainable.
Also the custom mods like the ftb-island-mod with its /island_x commands should also be tested. Why it throws an error like "player not found" when it's supposed to read the island-name from json and the linked coords and just perform a tp with current player using this command? I don't know the MC/Forge-api - but as I've seen in many java-forums (still wonder why beginners who thnik starting learning java by creating a minecraft-mod seems a good idea) there are instances of Player and Command - so on server-side there should something like Player player=Command.getPlayer() or some like this to get the Player-object for wich player used the command. Also: Throwable.printStackTrace() - at least server-console should output a meaningfull exception-stacktrace like for broken /help-handlers - or some way to enable debug mode - so that java-devs can understand what's wrong and can make good bug-reports.
Go ahead - ban me again for this complaining - but please: FIX IT! And please fix your lazy release-cycle to at least someone takes the time to grind the achievements and test every command BEFORE releasing it to public. There's something like unittests you can automate such testing. And building a testsuite one time saves lot more time against someone has to grind all again after rebuilding. Is it really that hard to follow common java development practices?
Yes - I know - you don'T feel responseable for errors made by mod-devs (when they would do such testing there would be a ton less errors) - but at least you could relay found issues to them instead of just ignoring bug-reports at all.
Do what ever you want with this report - maybe I should start by reverse-engineer FML/Forge and fix the base errors made there by cpw and player wich causes many errors in mods that have to be made just to able to compile against fml/forge api.
Oh - and what version was it again Jeb once announced official mod-api for? 1.7? FTB is one of the biggest packs - why you don't bother those guys over at where ever now the main dev is (is it really M$?). Why you don'T use your "power" and just say: Ok, we just stop supporting new versions until there is an official mod-api - cpw and player have this power - why they don't use it to make MC better in the first place?
To quote star wars: much to learn you have ...