0 Members and 2 Guests are viewing this topic.
(...)
Following the idea of in-game map making, a polybug tracker would be nice, a player would be able to identify a polybug and register it. Later that polybug point would be visible to the mapper.
...PC vs Mac is like AK47 vs M4A1...
I know that you can group them (mentioned it in my last post in a similar way).The idea is that users could add their own tools to the tools menu via scripting/plugins.But i guess grouping could work out well.
The config menu button was inspired by Chrome. The other idea was to have a tab with config like you can see in mockup 6.The menubar could have the same settings so you have two ways to reach it.
Map settings somehow don't work yeah. Any idea where to put them in the map tab?
Welcome page would get displayed when you run PW2 it would show the last opened maps and other information and links to other stuff like help so you could get started easily.
I personally find Mirandas Config is just confusing and forces you to search stuff. Too many options and a inconsistent GUI.But I thought about a tree like structure and i have ideas how to make it work - if we really need it.I hope we don't need it though. There is enough space in the right side in the config to show all settings IMHO.
I'm not sure were else the texture stuff should go and i think it's currently ok it was there in PW and no one complained .If then it has to get yet another sidebar.
Quote from: As de Espada on June 30, 2012, 08:41:49 amFollowing the idea of in-game map making, a polybug tracker would be nice, a player would be able to identify a polybug and register it. Later that polybug point would be visible to the mapper.I think it would actually be easier to just fix the whole cause of polybugs, than to make tools to handle them.