JavaScript is required to use Bungie.net

Service Alert
Destiny 2 will be temporarily offline tomorrow for scheduled maintenance. Please stay tuned to @BungieHelp for updates.

Forums

2/16/2009 4:32:10 PM
0
Yea, I got this on a 3-post, almost 30,000 character report I typed up for one of my Private Groups. I was [i]not[/i] pleased. 5 hours of my life was dedicated to fixing that problem- and I only got through the first two posts without any major issue. For the third, I had to actually literally map out every single one of the problem spots using process of elimination, and manually type up every problem spot- link and all- from the open Word document that I had, straight into Bungie. What I did was take the text from the thread, then I cut it down, line-by-line, until I was able to post it. I did this from the bottom of the text to the top, and then the top to the bottom. Then I cut out the sections that hinted they had problems with it from the Word Document, and I cut out sentence-by-sentence until I was able to post it, and (using this) I was able to find the exact lines that were causing issue. I then rolled over to Word, and mapped the entire post with highlighters. I found out that I had three sections with major issues in them, one of them was simply a line (which I bit the bullet on and just cut out) but the other two sections were large, and important. So I had to go to a Bungie.net window and type these things up, word-for-word, hyperlinks and all, until I got past those sections and was able to post it. I think the idea behind this was a smart one, but I also think that it's becoming increasingly apparent that this was a bad move on the WebTeam's part. This is the one part of the update that I, hands-down, think is absolutely horrible.
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon