Showing Posts For CuriouslyStrong.6925:
Should blind make you miss EVERY time? I would think that blindly swinging a weapon nearby an enemy should land a hit at least a couple times…
The Orbs were removed, why weren’t the NPC’s? People farm them now since they respawn instantly. You get world exp for them and since they respawn instantly, a group of 3-5 can just continuously run in circles farming them. They should probably either be removed or given the invincible buff or not give world exp…
Here’s my python wrapper, I know there’s others out there but I was bored so…
GuildWars2API
- Language: Python
- Admin: CuriouslyStrong.6925
- Url: https://github.com/ngenator/guildwars2api/
I wrote a python wrapper for the API. It will look a bit weird because I separated out the resources to their own classes in the hopes of having it return actual objects instead of just json dicts. I sort of stopped halfway though… It still works fine returning the dicts but I definitely prefer objects to dicts so I may fix it up the way I originally planned it. Anyways, here it is:
What’s with all the wildlife?
im beginning to think that either we wont get a fix for atleast a few months, or never get one. it’d be nice if anet would be straight up with us and just tell us its not possible
Oh, it’s possible. I even provided one way to do it 
Remove skins and other customization.
Each enemy player would show up as a default (or even random) character of whatever race they are. Their armor would be the color of their Borderlands for the week. Their armor would be the default level 80 armor for its type and their weapons would be the default skin for its type.
There you go, 1/2 to 2/3 of the information about each character has been removed and no longer has to be sent for each player.
Why not (other than Fashion Wars 2 of course)?
Bump? Still no acknowledgement that this has been seen
If you take a look at the display for trading gold for gems here: http://i.imgur.com/k2DfF.png you can see that the values are way off and that they don’t even make sense after 75. Those should actually be silver, not gold.
Now, if you look at gems for gold, the same problem is starting to appear: http://i.imgur.com/r3BoK.png
It looks to be a conversion error from the integer value to the gold, silver and copper value. It seems like it went unnoticed because the prices never reached 1g until recently. I wrote out a formula for my trading post scraper, you can see how it is supposed to work: http://i.imgur.com/xLlS8.png
Ninja Edit: For anyone wondering, the code is python and the int function automatically floors the value http://docs.python.org/library/functions.html#int
I guess it’s not a huge deal, but it should still be noted and fixed
(edited by CuriouslyStrong.6925)