Bug 137: (zippyzee) Multiple Bugs in One (Wrong)
Moderators: Community Managers, Developers
-
- Posts: 810
- Joined: Wed Aug 28, 2013 9:40 am
Bug 137: (zippyzee) Multiple Bugs in One (Wrong)
Bug ID : 137 - Multiple Bugs in One (Wrong) Bug Date : 2015/01/28 02:40:47 Assigned To : zippyzee Priority : Low Category : VGClient Sub-Category : Graphics: Character Severity : Minor (e.g. Cosmetic) Reproducible : Every timeDetails:
If an item is unequiped from the appearance slot the character doesn't default to the regular equiped gears appearance. Also if you unequip something from your regular gear even with appearance gear on the item vanishes from the visible view.
I'm just going to add this one here. Searches on the broker in game used to include whatever rarity you picked and above here searches are just that rarity (meaning no way to currently isolate mythic) This way is useful, but may need an additional category or switch it to the way it worked in game.
One more about the character Set level has adventuring level 50 max. Are we not going to be able to get to 55? When the level cap was added it sucked but by the end there was enough content to support it.... A lot would need to be left out to put the world back properly before the increase.
Originated From World: New Telon (1) Chunk : Khal (85) Location : -992 -50136 1516
- John Adams
- Retired
- Posts: 4581
- Joined: Wed Aug 28, 2013 9:40 am
- Location: Phoenix, AZ.
- Contact:
Re: Bug 137: (zippyzee) Multiple Bugs in One (Wrong)
Testers,
While we love bug reports, please do not put multiple bugs in 1 blob of text. It makes it impossible to assign it to the developer working the issue, and your issues will slip through the cracks. If you have questions for the development team, post a forum post - don't ask in a bug.
Posting this so others know, this is not the way to do it.
To address:
While we love bug reports, please do not put multiple bugs in 1 blob of text. It makes it impossible to assign it to the developer working the issue, and your issues will slip through the cracks. If you have questions for the development team, post a forum post - don't ask in a bug.
Posting this so others know, this is not the way to do it.
To address:
- Appearance Gear; doubt this is implemented (zippy?)[/*nermadu0]
- Broker Search: Might be valid (zippy?)[/*nermadu0]
- .setlevel = is a test command, won't be in-game at Release[/*nermadu0]
- Level 55 = The community will decide if they want 51-55 content, though the content team will add whatever data that was collected[/*nermadu0][/list:u]
I'll leave this 1 bug open to zippy (items/appearances) - the rest, not bugs.
Re: Bug 137: (zippyzee) Multiple Bugs in One (Wrong)
Appearances are not implemented fully. I'm not sure how complicated that is (if at all) but not a priority right now with so many other things to get done.
I agree in thinking the original Vanguard broker showed a range of rarities up to the chosen rarity. I never understood why. There's a minimal number of rarities, and having the others mixed in never made sense. I can change it, easily, any time, but it would take an argument why that is better than the current system for me to give it my utmost attention. The argument "this is an emulator, emulate!" might also work.
I agree in thinking the original Vanguard broker showed a range of rarities up to the chosen rarity. I never understood why. There's a minimal number of rarities, and having the others mixed in never made sense. I can change it, easily, any time, but it would take an argument why that is better than the current system for me to give it my utmost attention. The argument "this is an emulator, emulate!" might also work.
- John Adams
- Retired
- Posts: 4581
- Joined: Wed Aug 28, 2013 9:40 am
- Location: Phoenix, AZ.
- Contact:
Re: Bug 137: (zippyzee) Multiple Bugs in One (Wrong)
I'm with you Zippy. Any way to improve our server, we should do. If the multitudes complain about rarity globbing, we can change it. For now, what you have is fine. Same with Appearances; I know it's not there yet, nor does it need to be. This bug push was more to set an example to others. Great info, just improperly delivered.