Minimum log requirement for RMTs

Status
Not open for further replies.
Darkmalice

Darkmalice

Level 3
is a Tiering Contributoris a Site Content Manager Alumnusis a Forum Moderator Alumnusis a Top Contributor Alumnus
I believe that a log requirement for RMTs would benefit the RMT thread.

The purpose of this is twofold. Firstly, it will encourage people to play their team before creating a RMT on it (and they should test it out before making the RMT, but there's no way of knowing if they do so without logs). This will promote a higher standard in the average RMTs so people aren't wasting their time reading horrible RMTs. Whilst there will be people who won't put their logs up, such people will be the ones who don't read the rules or check other RMTs before creating their RMT, in which case they would be locked under breaking another rule (e.g. not having adequate descriptions for their teams).

The second purpose is to make the teams easier to rate. Team raters will see how the player uses Pokemon individually and as a team, and how he deals with other players' teams. As such, they will gain a greater understanding of the team's strategy, and they will be less likely to make suggestions that don't work with the team e.g. placing Scizor in a stall team.

I think five logs would be suitable for a RMT, though I wouldn't mind a larger or a slightly smaller number. People are, of course, free to have more logs than the minimum requirement.

Battles not on shoddy would obviously be excluded from this rule.
 
Having to read a whole log would make reading a single thread extremely long and boring. And anyway, RMT is meant to help on the team assembling aspect of competitive play, not on the battling skills one (if you have a good team but you don't know how to play it, then you should sign up to the Battling101 program). Also people who play on WiFi have no way to save a log, and hence requiring a "proof" only to shoddy battlers would result into a discrimination towards those users.

I think that we (moderators) can already recognize teams that have been tested enough and team that haven't been tested at all, so, in most cases, the latters will be locked\deleted anyway.
 
I would agree with Haunter. Even for a good set, pruning for 7-10 logs that showcase both the success and failure of the set takes a good deal of time unless you're testing out a lead. It would be a hassle for many players, and not result in much gain. Instead, a player should be encouraged to discuss commonly utilized strategies in his Pokemon descriptions and threat lists if applicable.

I am not opposed to the idea of 1-2 logs as a proof of testing.
 
I have actually tried this prior to the suggestion you made and it helps in some areas, like RaikouLover's rate. He was able to see how the team is played and make a rate from there. It helps, but it makes the thread long and boring like Haunter mentioned. I'm thinking about putting hide tags around it, though, just to make it shorter. Is that allowed?
 
Yeah, you're allowed. There's nothing wrong with adding a log or two, it's just that I don't want it to be obligatory. Also yes, use the code tag as it makes the thread easier to be read.
 
If most of you are against the obligation of logs in RMTs but support their encouragement, could we make a point regarding logs in the "How to make an RMT (Required Reading) Message"? Here's the link to the post (it's pretty easy to find): http://www.smogon.com/forums/showthread.php?t=50298)

Just a simple point saying something like "One to three logs are encouraged to be placed in RMTs to give raters an idea on how to use the team to gain a greater understanding of the team. However, this is only a suggestion and is not necessary. If logs are used, they should be in code tags, so that RMTs are not clogged up with piles of long text."
 
Status
Not open for further replies.
Back
Top