YOUR CREATIONS & GUIDES


uiWebPrevious1uiWebNext

#1 [en] 

I am often puzzled as to whether a mission is truly broken or if circumstances (seasons, not fully killed spawn, whatever) are just preventing me from doing so. I'll try and keep this post updated with post number, description and status. Users can report their experiences and possible ease the burden on support staff if we can cut down on the number of mission submitted if answers can be found here. Format I'll suggest is:

Post No. - Mission Giver - Allegiance - Problem - Result

Example:

002 - Antonni Benios - Sap Slaves - Kill a Gibbai of level 200 or higher in Garden of Confusion; Are named / bosses to be included in missions ? - To be determined

Edited 2 times | Last edited by Fyrosfreddy (5 years ago)

---

#2 [en] 

Loot Level 240 (Great) Kincher



Went all thru Maze... into Highgrove ... /tar all the way through.


To be Confirmed

---

#3 [en] 

By me the issue with C011V001_10769 is confirmed, I was unable to find Great Kincher in Grove of Confusion. Added to task #9971.

#4 [en] 

Got it again ... no target reticule appears on map.

---

#5 [en] 

Q250 Broken Mission Fight in the Matis Lands.

Loot:
1 Morsels of Magnificent Forest Kincher Flesh of at least quality 240.
1 Morsels of Magnificent Forest Kipesta Flesh of at least quality 220 from a corpse.







Error: There are no q240 Kincher in Grove of Confusion.
























[/url]

Last edited by Gisli (5 years ago)

#6 [en] 

Likely this is not mission related but I can NOT take the reward ... any reward


---

#7 [en] 

Fyrosfreddy
Likely this is not mission related but I can NOT take the reward ... any reward



It is reported and confirmed (task #7485)

#8 [en] 

Fyrosfreddy
Likely this is not mission related but I can NOT take the reward ... any reward
Check sys.info
For me it texts "You win: 20000 dappers" just after i click chest in daily mission window and only after it it open window with choices (which is unable to resolve).
Forced dappers. Richness.

#9 [en] 

No reward offer - C005V003-10784

[/img]

Last edited by Fyrosfreddy (4 years ago)

---

#10 [en] 

C011V004_11012

Asks for 1 tuft of superb forest gibbai hair of q180+.

Frightening Gibbaïs are level 179, everything else above are nameds 210+. Not sure whether they would even drop "superb" quality.

---


My home is always sweet Yrkanis..

#11 [en] 

I have gotten cred in the past by killing nameds .... just did as a test, not sure if it is universal.

---

#12 [en] 

C011V004_11159

Asks for "1 superb forest kirosta flesh", at least level 190.

Per my research, Might Kirosta (level 193) in Hidden Source should do. I triple-checked that the mission setting is for mobs level 150-199, and that "superb" materials will be found in level 150-200 regions.

I have killed several Mighty Kirostas, not one single drop. Either I am extremely unlucky, or this is bugged.

Last edited by Mjollren (3 years ago)

---

#13 [en] 

Sidenote, the topic title may be "Guide to broken missions", but the main purpose is to report bugs (and things that end up not being bugs, but still).

Therefore I think the group of 5 related topics should be moved under Technical Support or a more appropriate section :)

---

#14 [en] 

This is reported on gitlab, and gitlab is public. Unfortunately, we will soon change the location of the bug report.

---

Jadeyn | Senior Game Master | Polyglot/Multilingual
Ryzom Support Team

#15 [en] 

Mjollren
Sidenote, the topic title may be "Guide to broken missions", but the main purpose is to report bugs (and things that end up not being bugs, but still).

Therefore I think the group of 5 related topics should be moved under Technical Support or a more appropriate section :)

After encountering these early mission failures and entering them as bug reports, quite often they turned out not to be bugs at all ... as is often shown in each of these threads.

It was subsequently suggested to Ryzom staff, that this thread structure be created for the following purposes:

a) To filter out the ones that were were not bugs just "not completed" by a particular player on a particular occasion. This saved an overburdened Ryzom staff from wasting time and allowing them to focus on other things.

b) To provide players doing the mission at a later date the information that it was in fact a broken mission. That way they didn't wast untold hours doing something that can not be done.

c) When it's not bugged but maybe it couldn't be completed because of season or at target mob had been killed, and to provide the unsuccessful players with the "How To" to complete it such as "wait for named [insert mob here] to respawn

d) Sometimes a player would get say a mission in forest to dig a mission mat and that mat might not exist in forest, but another playe might post where that mat ould be found in another region.

e) The location for posting bug reports is not very well indexed. The goal here was to index them by region and level so they could hopefully determine specific missions withrout haveing to read thro the list by date reported. The location for posting bug reports has changed so often that if there was a recycle bin for all the bookmarks I've used since missions came in game, I'd have noticeable extra room on my storage drives (Ok exaggerrating but it is a lot) :)

f) Technical support requests for bugs are made with the expectation that bugs will be at some point fixed. These, for the most part had not been fixed, and players were told "Yeah, it's broken, drop this mission and pick another one." I kept a list of the Mission Numbers for the broken ones sho that when I took a new batch, id imeidtaely drop it and use one of my 4 "re-rolls". I'd not be surprised if the Re-roll feature was added at least in part because of this.

I haven't done any DMs for ages since having achived the "Spirit of Sally Field Title" ... so not sure if the mindset towards these has changed but hoped it might explain the genesis behind the thread creation.

---

uiWebPrevious1uiWebNext
 
Last visit Monday, 25 November 04:11:34 UTC
P_:G_:PLAYER

powered by ryzom-api