Errorcode Chard! is that a new one? / Niobe Torment a Joke?
So i am currently bothered by Errorcode "Chard".
What s happening is that you get kicked out of game with that Errormessage. Every 8 minutes even after ihave made Scan Repair solution. Which mostly never finds anything.
Ok, so i thought i search the internet and found many a people having those issues around November - Dezember 2018.
Now we have Januar 2019. Means this Error is not fixed yet.
Also i wasnt able so far to find any help here on Bungie Forum for it.
Again i searched and found this List of errors on Kotaku Website:
[i]98. SNAIL
97. CHICKEN
96. DUCK
95. PONY
94. CAT
93. SHEEP
92. ELK
91. BOAR
90. HARE
89. APPLE
88. PEAR
87. BLUEBERRY
86. MOOSE
85. RABBIT
84. BEETLE
83. CHERRY
82. LEMON
81. LIME
80. NEWT
79. BAT
78. GRAPE
77. PINEAPPLE
76. OLIVE
75. GOPHER
74. GRASSHOPPER
73. JACKAL
72. BUFFALO
71. GROUNDHOG
70. GRAPEFRUIT
69. JACKFRUIT
68. CENTIPEDE
67. ZEBRA
66. BUTTERFLY
65. CABBAGE
64. LEMUR
63. ELEPHANT
62. BLACKBIRD
61. FLATWORM
60. MONKEY
59. BUCK
58. CARP
57. LIONFISH
56. KIWI
55. VULTURE
54. CHIPMUNK
53. CAMEL
52. PELICAN
51. COCONUT
50. GOOSE
49. GOOSEBERRY
48. MONGOOSE
47. CATTLE
46. KINGFISHER
45. CASHEW
44. URCHIN
43. BUZZARD
42. JASMINE
41. BABOON
40. BULL
39. CARIBOU
38. TANGERINE
37. PENGUIN
36. TURTLE
35. LEECH
34. BEAGLE
33. CHIMPANZEE
32. FLY
31. LION
30. ELDERBERRY
29. HAWK
28. CURRANT
27. BLACKCURRANT
26. LEOPARD
25. TAMARIND
24. STINGRAY
23. CATFISH
22. GUITAR
21. PANTHER
20. CHOKEBERRY
19. CHIHUAHUA
18. TAPIR
17. LETTUCE
16. CHINCHILLA
15. TANGELO
14. ANTEATER
13. TRUMPET
12. LEMMING
11. TERMITE
10. CHIVE
9. MARIONBERRY
8. BEE
7. WEASEL
6. FLAMINGO
5. CACO
4. BEAVER
3. CHUPACABRA
2. SAXOPHONE
1. GOAT[/i]
Know what? This list does not even has the Code "Chard", so looking at the Titel of my Thread and asking it. Is this a new one and what can YOU do Bungie to fix it.
How am i supposed to play Game when i will be kicked every 8min.
I am using this game as a hobby for over 3500 hours allready so far. And i keep on going if i could.
[u][b]Fix it and just for the fun to mention another thing which bothers:[/b][/u]
The New Niobe Labs Torment Event is a big joke only good for Bungie itself to stay in the media. Because this payed Event/Annual Pass content cant be played by everyone. No single Person has the brainpower to make/produce a fast solution for himself to have a good game experience. Its a Wave/Horde mode Event with shooting Puzzles/Riddles inbetween, which are so hard encoded that no single person will / can do it solo. Ergo people cant play content which they payed for. Only thing you can do, is wait for streamers with thousand of watchers/Brains helping them to finish it.
Why Bungie, do you have such awfull gamedesign, where people are passive watchers? Thats totally stupid gamedesign. It only fuels your public relation in the media and not giving people/customers a moment of personal glory in the game to be a real part in the opening of Bergusia. The immersion is gone. GREAT :(
[i]UPDATE: Interesting fact. I had the Emblem in use which counted my 240 ascended chests opened so far. Which normally should also gave me allready the "Fastidious miser" Triumph. But thats also a bug in the system for monthes. Anyway, after switching to another emblem the "chard" error was gone after having several frustrating kicks before.[/i]
Your role as a moderator enables you immediately ban this user from messaging (bypassing the report queue) if you select a punishment.
7 Day Ban
7 Day Ban
30 Day Ban
Permanent Ban
This site uses cookies to provide you with the best possible user experience. By clicking 'Accept', you agree to the policies documented at Cookie Policy and Privacy Policy.
Accept
This site uses cookies to provide you with the best possible user experience. By continuing to use this site, you agree to the policies documented at Cookie Policy and Privacy Policy.
close
Our policies have recently changed. By clicking 'Accept', you agree to the updated policies documented at Cookie Policy and Privacy Policy.
Accept
Our policies have recently changed. By continuing to use this site, you agree to the updated policies documented at Cookie Policy and Privacy Policy.