MegaGlest Forum
Archives (read only) => Vanilla Glest => Bug report => Topic started by: ZaRo on 3 November 2009, 09:12:02
-
You shouldn't do "string ro resourceClass" :)
Place: source\glest_game\types\resource_type.cpp line 121
Picture:
(http://img338.imageshack.us/img338/1430/stringroresourceclass.jpg) (http://img338.imageshack.us/i/stringroresourceclass.jpg/)
And yes, I know that "fun" isn't a resourceClass :)
Best regards
ZaRo
-
What Glest version is this?
-
What Glest version is this?
glest 3.2.2
-
we should totally have "fun" resources!
ok, seriously, i have never had this happen, so could you describe your problem a bit more? does it always say "ro"?
-
we should totally have "fun" resources!
ok, seriously, i have never had this happen, so could you describe your problem a bit more? does it always say "ro"?
Dude he changed the XML.
-
i had never encountered the error before (and i have messed with all of the XMLs), i just wanted to know how fix it in case someone asks me...(and i thought it was more serious)
-
No Zoythrus, he changed the resource type in one of the resource XMLs.
-
i thought the typo was the "ro" thing...
-
i thought the typo was the "ro" thing...
What "ro" thing?
-
it says, "converting from string ro ResourceClass" at the bottom of the pic
-
Yea that's the typo.
-
never mind. lock this thread please, we're just going around in circles!
-
It's a completely pointless post. He's pointing out it should say to instead of ro, but he only encountered this error because he put the string 'fun' in the XML attribute that SHOULD contain either tech, tileset, static, or consumable. Not 'fun'. :P
No real need to change it. No body will ever hopefully see this error unless they screw up BIG in their XML (which means they didn't use my Glest Guide!)
-
It's a completely pointless post. He's pointing out it should say to instead of ro, but he only encountered this error because he put the string 'fun' in the XML attribute that SHOULD contain either tech, tileset, static, or consumable. Not 'fun'. :P
No real need to change it. No body will ever hopefully see this error unless they screw up BIG in their XML (which means they didn't use my Glest Guide!)
Oh come on.
Here I come up with a perfectly resonably bug, where to find it and what to do to fix it, and all I'm getting is useless posts on how I found the error. Could we please grow up and fix the bug?
Best regards
Zaro
-
Thanks for testing ZaRo. This has been fixed in GAE trunk revision 306.
-
Thanks for testing ZaRo. This has been fixed in GAE trunk revision 306.
No. Thank you! :D
ZaRo