Forum > Noggit

Noggit 3 [r104] Custom continent crash [WoW 3.3.5a]

<< < (2/2)

MidnightWolf:
Well, if the approved tutorial is not working it IS related somehow to noggit. If there wouldn't be any error, we'd drown in custom user made maps already but that seems not to be the case. A fresh tutorial is required or a proper explanation why this is not working properly, even when it is done by hand.

I disagree with you on the user's part. I don't think the wow modders are made up of people who don't care about the editing programs they use. First off it is everyone's(developer+user) interest to have a bugfree program to use therefore reporting encountered bugs is not a favor to do, as long as there is a clear method doing it (I'd prefer a forum section where bugs can be posted as topics as opposed to the current bugtracker method [too "developerish"] ). I don't see a reason why would a user leave an annoying bug unreported when he bumps into it each time he uses the program. Even though I think modding wow requires a lot of understanding (thus expert people), there will be always newbies or people who simply don't understand things easily. To that end there should be a built in help menu or something, and a link pointing to this forum (even I had hard times finding this board) so people can get help easier and/or report bugs.
What discourages people here is the pressure to report bugs. In a working community this shouldn't be needed as per the reasons explained above.

schlumpf:

--- Quote from: "MidnightWolf" ---Well, if the approved tutorial is not working it IS related somehow to noggit. If there wouldn't be any error, we'd drown in custom user made maps already but that seems not to be the case. A fresh tutorial is required or a proper explanation why this is not working properly, even when it is done by hand.
--- End quote ---

How is the tutorial connected to Noggit? If Cromon's tool creates corrupted files, that's not an issue with Noggit. On why it won't work for you: I don't know. And I can't test. How should I test without data to test with? A public new version of Noggit won't fix that as well.


--- Quote ---I disagree with you on the user's part. I don't think the wow modders are made up of people who don't care about the editing programs they use. First off it is everyone's(developer+user) interest to have a bugfree program to use therefore reporting encountered bugs is not a favor to do, as long as there is a clear method doing it (I'd prefer a forum section where bugs can be posted as topics as opposed to the current bugtracker method [too "developerish"] ). I don't see a reason why would a user leave an annoying bug unreported when he bumps into it each time he uses the program. Even though I think modding wow requires a lot of understanding (thus expert people), there will be always newbies or people who simply don't understand things easily. To that end there should be a built in help menu or something, and a link pointing to this forum (even I had hard times finding this board) so people can get help easier and/or report bugs.
What discourages people here is the pressure to report bugs. In a working community this shouldn't be needed as per the reasons explained above.
--- End quote ---
In the whole time, I worked on Noggit, people never cared but mostly just complained. There are people flaming developers for the bugs and that the software is useless and shit. There are people claiming that the whole reverse engineering work is bullshit and useless. Does that motivate developers? I guess not. Sure, its in the interest of both, to have bug free software (well, more the interest of the users).
You can always report bugs by mail (schlumpf__@hotmail.de), bugtracker (^) and whatever you like. Just claiming "it does not work" without any data to use for the developer won't help though.
People don't report errors because they prefer to cry about it, flame or just dismiss work.
This general flaming attitude encountered in this community of wow modding (as mostly seen on mmowned) is a reason why developers prefer to have things semi-private to be able to control stuff a bit. There is no pressure, but the versions published in that private section are beta versions and beta versions are intended to be tested. If you claim to test stuff and never do, that doesn't help anyone.

Well, I don't really care. Thing is: people flame, developers get demotivated, applications keep being shitty, people flame more.

Steff:

--- Quote ---fact is that people are lazy in general which means even the smallest step required to get stuff discourages them from doing so
--- End quote ---

Then fuck up such people. We spend TIME in developing so I think it not to much for others to spend time helping. If not they can go away and do something else with free time. And if a user have not enough motivation to register on a bugtraker he is not realy helpfull with beta testing. Testing meens not using the tool but realy test new functions and other stuff we write in the beta board. And we have around 10 people doing this realy good in the moment. And i want to say a big thanks to them now!


--- Quote ---Also: All files should be read from the disk, no matter if ADT, WDT, BLP or XML. There should be no difference codewise
--- End quote ---

104 had the bug. it read WDT only from a patch file. I Fixed this.


--- Quote ---is everyone's(developer+user) interest to have a bugfree program
--- End quote ---

And thats why I have closed developing to a group that will help finding the bugs and release it if they are gone and the normal users can use it (and i think we are near to this point). I hade enough of flaming and stupid posts that noggit is shit and dont work, without any helping information why and what did not work. And the clue was that in 60% the errors had nothing to do with noggit. I just made a new continent last week with eluos tutorial. And it works fine for me.

Excuse the hard words. Its normaly not my way but it also gets me on my nervs now, and I want to point this out. And by the way there are many oterh things you can help. Writing tutorials, help writing the noggit manual, be active here on the baord. All this will give me more free time to do more development.

MidnightWolf:
Well then if Eluo's tutorial works for you in r104 then I must be doing something wrong. I've attached my files.

[Edit] Might be a good idea to write out which version(s) of the program(s) were used for making the tutorial [/Edit]

Anyway I totally understand your point, no one likes when people flame their work. All I can say to that however is:
--- Quote from: "Steff" ---Then fuck up such people.
--- End quote ---
There are always idiots/trolls and clowns who act like that but that shouldn't give a reason to stop development or close public access. Ban them if you feel like it.

Testing is done by using the tool actually; which can be done by anyone who uses the program (I can be considered a tester too when I use r104 to build stuff). That way you might have 100 very good people who test, not only 10. Again, this needs full public access to betas so people don't think noggit is dead or things like that. Remember, all they see is a year and a half old release.

Yeah, people sometimes mix things up. WoW modding is a bit complicated though, there are many realtions and overlaps between things (only people with a lot of experience and knowledge can oversee all of that), and that can explain why most of the reports tends to be false. There is no need to jump on these poor guys however.

All in all, the developers decide what to do. Community members can only make suggestions like I do.

Zim4ik:
Try to remake your *.wdt file of location.

Navigation

[0] Message Index

[*] Previous page