×

Langue

Fermer
Atelier 801
  • Forums
  • Dev Tracker
  • Connexion
    • English Français
      Português do Brasil Español
      Türkçe Polski
      Magyar Română
      العربية Skandinavisk
      Nederlands Deutsch
      Bahasa Indonesia Русский
      中文 Filipino
      Lietuvių kalba 日本語
      Suomi עברית
      Italiano Česky
      Hrvatski Slovensky
      Български Latviešu
      Estonian
  • Langue
  • Forums
  • /
  • Transformice
  • /
  • Suggestions
  • /
  • [Maps] Double perming
[Maps] Double perming
Hophipmice
« Citoyen »
1380444120000
    • Hophipmice#0000
    • Profil
    • Derniers messages
    • Tribu
#1
  0
I have suggested this once in my other account but the thread died so I'll resuggest it.

What is double perming?
Double perming will give rights to mapcrews to double perm your map, such as if there's a P6 and it should also go down as P7, mapcrews will be able to make it P7 and P6 in the same time, with a command, it should be something like /2perm
1
2
3
4
5
 [Map cats, should be separted by a comma]

How will people be able to submit these maps?
I think it should have its own thread, named double perming and people post with the following formatt:
@xxxxxx cat1 cat2
Lemodile
« Censeur »
1380445680000
    • Lemodile#0095
    • Profil
    • Derniers messages
    • Tribu
#2
  0
Although I think this will rarely be needed, you could just as easily export your map twice and set one as P6 and one as P7.

What's the benefit of doing things in the way you suggested?
Hophipmice
« Citoyen »
1380445800000
    • Hophipmice#0000
    • Profil
    • Derniers messages
    • Tribu
#3
  0
Lemodile a dit :
Although I think this will rarely be needed, you could just as easily export your map twice and set one as P6 and one as P7.

What's the benefit of doing things in the way you suggested?

Listen, you have a P7 wich is also a P6 map, if you suggest it to be a P7 map, it wont work as a P6 map anymore(wont be permed) but if you ask for it the be P6, you wont get a P7 map.
Papero
« Citoyen »
1380446460000
    • Papero#9240
    • Profil
    • Derniers messages
    • Tribu
#4
  0
Lemodile a dit :
Although I think this will rarely be needed, you could just as easily export your map twice and set one as P6 and one as P7.

What's the benefit of doing things in the way you suggested?

for maps that do not fit well into some categories but are being used as fillers.
Syrius
« Consul »
1506612720000
    • Syrius#8114
    • Profil
    • Derniers messages
    • Tribu
#5
  0
support!
Antonio
« Sénateur »
1506612840000
    • Antonio#9975
    • Profil
    • Derniers messages
    • Tribu
#6
  0
Marciskris a dit :
support!

same
Anythin
« Consul »
1506622020000
    • Anythin#0095
    • Profil
    • Derniers messages
    • Tribu
#7
  0
Generally maps don't fit in more than one category. If they do, they're usually put as P9 instead. So the odds of this suggestion being useful are pretty low.
Syrius
« Consul »
1506946440000
    • Syrius#8114
    • Profil
    • Derniers messages
    • Tribu
#8
  0
Anythin a dit :
Generally maps don't fit in more than one category. If they do, they're usually put as P9 instead. So the odds of this suggestion being useful are pretty low.

1.) Really? What about very needed "mechanism with no shaman" category? These mechanisms are in competely different spirits than normal P7 map. So easy-breakable/not needed shaman maps need to be permed in competely different category. Then this could mix (P6+P7).
2.) What about "racing with shaman"? This was used for harder racing maps. Again, (P4+P17).
Anythin
« Consul »
1506949140000
    • Anythin#0095
    • Profil
    • Derniers messages
    • Tribu
#9
  0
P7 is for "no shaman" maps, so if the map is better off without a shaman there is no problem putting it as P7. Regardless of what other P7 maps look like.

We also already see several maps in p4 that are possible to finish solo, albeit difficult, without the need for a shaman. In these cases, P9 is an option too.
  • Forums
  • /
  • Transformice
  • /
  • Suggestions
  • /
  • [Maps] Double perming
© Atelier801 2018

Equipe Conditions Générales d'Utilisation Politique de Confidentialité Contact

Version 1.27