Ranger Archive
Thread: No one noticed the changes to examine?
--------------------------------------------------------------------------------
Fred_Skinner wrote:
--------------------------------------------------------------------------------
Rancorrider4 wrote:
Flynn makes a couple of outstanding points. Having no knowledge of a creature proir to harvesting it the first time, and having it show as blank on examine is great. It's a Ranger accrueing knowledge.
...snip...
--------------------------------------------------------------------------------
I don't see that... like killing a horse to learn how to ride one... should be able to know a lot just by observation.
--------------------------------------------------------------------------------
HUH?
Fred, go back and read my original post about it, Rancor (thanks for the support) didn't exactly quote me correctly. Let me re explain.
OK, You have never killed a Kimogila on Lok, (for sake of discusion) You examine it and see that it has lokian leathery meat, woo hoo! (big deal),
You kill it, harvest the hide and move on.
The NEXT Kimogila you see, you examine it, it tells you that the Kimo has (Avowo)Lokian leathery hide.
Now, you learned something about the Kimo since your first run in with one.
I don't know that we get to know the stats on that Avowo, maybe it updates a "resource schematic" in our data pad telling us the specifics about that resource, I don't know.
Maybe at Master we get to see the stats on the hide as well as it's name.
Point being you could never have known the name of the hide or the stats on the hide unless you have killed one previously and harvested that resource.
Just a thought
DeltaXi65 wrote:
Guys,
Examine not only is working correctly - they've made it a lot easier to understand. Killer is now "Deathblows: Y/N", the specials that the critters use are correctly being displayed now, and the numbers next to the "meat/hide" type are gone - why, I'm not sure.
So this makes examine a lot more useful.
B
Sounds like examin has a new bug added with the change to features, I noticed and /buged this fresh new bug myself.
So I disagree somewhat, its not working correctly.