I feel like this is by far the worst fix ever, this is basically a huge flip off to the actual skilled people out there, since right now it will just be a matter of ping, and then again, good internets.
I have no idea what Tig wants to achieve, but he certainly killed all of the hours of my activity on bootcamp. [/ego]

Whiskypickle a dit :

I doubt a rule telling people not to post if a room doesn't work would stop people from doing that at all. =p But the link to the Module API and adding the tags are nice ideas.
Is that really necessary? I mean i'm sure it would be obvious enough if a module doesnt have an official tag next to it that it's unofficial.

Unofficial module is not really a common module it's runing 24h/24h but it's not in the /module list. This tag could help people to find new Module wich are no as popular as others or just new and unknown yet.

Galaktine a dit :

Version 1.118:

- Shamans can build correctly on maps with vertical scrolling.

Good job admins.

Whiskypickle a dit :

There's already a lot of tags in that subforum, it gets to a point where it's confusing to read over. I'd rather not add more tags unnecessarily, especially when it's common sense that any module that isn't official is unofficial.

No the issue there are two kinds of unofficial modules now.
those that run automatically in rooms and the other has to be manually run by lua members

then theres official modules which run automatically an award shop cheese. *capped at 2mins per cheese*

Woah, now your name it automatically saves at login *-*

save password feature when

Whiskypickle a dit :

Sentinels have been instructed to leave duplicate and similar threads in the Bugs section alone so that Tigrounette can keep better track of the bugs and issues players have posted. As a result, please do not report any threads that have an existing or similar thread already made. We will no longer be locking them.

Please note that bugs that have a special dedicated thread for them (E.g. the Community Platform) do not apply to this rule, you may still report these threads.

I know you guys don't have any contorl over this, and we spoke about it on Skype when I was wondering about my reports; but I still find this really ridiculous. It's much cleaner, and just as easy, to look at one central thread where five users are having issues, rather than five threads by five users with no replies, or only one or two people trying to help.

And what of things on the Bugs list that are known? Or sync bugs (aka stuff that's been known since TFM's existence)? Do those now get left open too?

Personally I think the Bugs List is good enough for bugs Tig should 'keep better track of'. Or, like Haru said, one single thread for one single bug and then close the duplicates. I don't see how having multiple threads is easier to keep track of; one thread with lots of posts with "yes I have the same problem" is easier.

Illusionyx a dit :

Personally I think the Bugs List is good enough for bugs Tig should 'keep better track of'.

Bugs list always ends up out of date after a few updates. I used to work with Dracoleaf on it but he's since been removed; and I feel bad bothering other sents. :(

So what if there's a significant, but not so obvious game altering bug that gets reported once and a few players reply to it but not so much so it won't spread like fire? Will Tig prioritize an other bug just because it has a shitton of threads but less significant or one that doesn't really affect gameplay that much?

Also, this just going to make the Bug subforum even more messy and more difficult to look at.

Haruhitastic a dit :

Bugs list always ends up out of date after a few updates. I used to work with Dracoleaf on it but he's since been removed; and I feel bad bothering other sents. :(

Oh, that makes sense. :x Would it be possible to make a new topic or are people not that bothered by it? >_<;;

Vogul a dit :

Will Tig prioritize an other bug just because it has a shitton of threads but less significant or one that doesn't really affect gameplay that much?

this too.

tbh all this new update does is make the section messier. If you want to prioritize by # of users affected or whatever, keep one thread and let users report their own circumstances and say "i have this too" and look at the post count. But that's not a good way to organise your priorities.

Whiskypickle a dit :

Is that really necessary? I mean i'm sure it would be obvious enough if a module doesnt have an official tag next to it that it's unofficial.

There are three types of modules:
1: Official module scripts, those that have a special # room.
2: Unofficial scripts, approved by admins, those that can be loaded with /module in tribe house but have no special # room.
3: Unofficial scripts, not approved by admins, those that can only be loaded with /lua in your tribe house by regular users if you happen to have the code.

2 and 3 are really quite different because the difference is that one is admin approved while the other is not...and that actually means one of them can be loaded with /module and you don't need to find the code. So having an unofficial tag for admin approved modules would be quite helpful :)

I'm sure you know all this but it's just that from a user stand point, it's actually helpful to have these.

For the new rule in the Bugs subforum, what makes it better to track than before?

And threads that aren't affected by that rule are the stickied threads of that subforum, I hope?

Bolinboy a dit :

If it has a stickied thread, like Platform, Shaman Update, Module API, then it can be locked, however it doesn't matter if it is on the bug list or not.

Can we at least report everybody who says that it's known after someone say sit is?

Bugs is a shitfest enough when there's a new update but now? I don't think I'm gonna touch it anymore to be honest.