| Board | Ideas.old [context] |
|---|---|
| Sender | Astark |
| Date | Wed Dec 21 08:47:39 2016 |
| To | all |
| Subject | re all the ideas |
| Rakshasa : Personally not a huge fan of letting them morph R10 ideas. I already think it's an overpowered race and I'd like to leave it be, rather than giving it a buff. I understand ascension is a tremendous time investment but I'm not a fan of buffing the race. Tank Status : Yes this should be possible. I think we would go with raw number instead of percentage, since that's the information you see in "group". Mastery List : Technically possible, but not without a significant amount of work I don't think. Only way I see to do it would be to build a table in the actual code, that contains all of the help file information. Then we'd have to tell the mastery list command to reference the table with each mastery that it displays. It would also mean that we have to make a code change each time we want to update that file, instead of just editing a help file which is plain text and editable within the game. Questing : No, we will not separate hard and normal quests into separate timers. Between questing, achievements, and repeatable quests, it is not incredibly hard to earn QP. Pleveler (private note to imm): Yes we can make this run repeatable on a more frequent basis. Smithing : This sounds fairly similar to enchanting, although I understand that enchanting is not available to every class. This wouldn't be trivial to design, implement, test, and balance. Can't really say any more on it without much longer discussions. |
