Zombie

Members
  • Content count

    77
  • Joined

  • Last visited

3 Followers

About Zombie

Firestorm User

  • Name Zombiebrains
  • Class Shaman
  • Level 90
  • Realm Gul'dan
  • Race Troll

Recent Profile Visitors

1764 profile views
  1. Wow Goldpaw, I'm a big fan of your work. I would never have guessed that you would come here. Disclaimer: I do know this thread is quite old.
  2. .... read the title people... admin/gms and other staff has to count. players have to stop them...
  3. not having the blizzlike rate is not blizzlike to... it's unblizzlike either way. yet being able to play with blizzlike rate would be more blizzlike for the player.
  4. He meant that it has been implemented trinitycore. Firestorm has made their own branch of trinitycore a long time ago, So firestorm doesn't have the updates trinitycore has and vice versa. But since a lot of the core structure is probably still the same, it should be possible to implement it like trinitycore did.
  5. bumping allowed?
  6. if staff bands together maybe.
  7. (32 % 3) + 4
  8. he means that on retail everyone has the same exp rate. I get his argument. But being able to choose a real blizzlike exp rate is also blizlzike. So it's choosing one blizzlike or the other blizzlike. but none of our arguments matter, it's the staff that will choose if it can and should be implemeted.
  9. you are mistaken, this is for staff to count and for players to interrupt.
  10. doesn't matter, people can choose that for themselves. for grinding they can turn on 5x exp.
  11. We should await the verdict from the Staff
  12. But it's actually the 5x exp that is un blizzlike. the chooseable exp is more blizzlike since it enables players to use 1x exp to level. they can choose how blizlike they want their experience to be.
  13. but with the chooseable exp people can only choose 1,2,3,4,5 exprate thus closer to blizzlike
  14. it has been implemented on most trinitycore servers. so unless the core is radically different exp wise, it should be possible. The database would need another field per character where the the exp rate per char is saved. then in the core the function that handles the final exp to a char would be modified with the exp modifier.