196
Utilities and 3rd Party Applications / Re: Modding Tool: Raw Explorer (Beta 3.1 - Updated 4/27/2012 - Oops)
« on: April 28, 2012, 06:46:44 am »If my submission to the token library was accepted that UNDERGROUND_DEPTH thing may be my fault, due to not really understanding how to set those kind of things.No I've checked it and it's formatted right. The problem seems to be that the program isn't stopping you from inputting integers that are beyond the accepted ranges. I've checked a couple of other areas where an integer should be limited and they suffer from the same problem.
Also one more thing, the [SYN_INGESTED] token currently has no "allowed on" or "usage" areas. Whenever I try to add a usage area I then get the message "Unhandled exception has occurred in this application". Clicking on the "details" button does absolutely nothing different from clicking on "Continue". The other [SYNDROME_X] tokens appear to function fine though.
Edit: Another thing! Currently there are a few values which can technically accept negative values (Namely the [MATERIAL_VALUE:X] token). I was just wondering if your "integer" argument would naturally allow for those or no (considering that the limits were fixed that is).
Edit2: And another! I seem to have some problem at times getting the changed definition to send to the website. As far as I can tell if you just change the arguments on a thing that already has at least one argument defined then it doesn't send to the website when you click "save". If the token doesn't have any arguments defined or if you change the description then it sends, but if it has some arguments defined and you only change the arguments it doesn't send. The same thing also appears to happen if I only edit the "allowed on" field without changing the description field.
Edit3: One more! Anytime that I create an ALL:ALL usage token it changes the current displayed information for the token to unknown and blanks out all of the fields in the editor until I redownload the token definitions (after it has been applied).
Final Edit: I just noticed that if I right-click anywhere in the definition editor that isn't in a field then I have the "Customize Layout" option. Selecting this then opens up a menu that looks a little complex for the average user to be intended to open and looks more like something you would be using to edit the layout so I wasn't sure if you wanted it to be able to be accessed.
Sorry for dropping all of these various bugs/questions into your lap overnight! I guess that's what I get for throwing up 200-300 more token definitions in the middle of the night when nobody else is online. Anyways, I'm out for the night!
Thanks for the bug reports! I'll try to get fixes out for the most important ones first.
Apparently the Argument Grid decided to just stop validating input entirely at some point. It just let me put in the value "cat" on something that is an integer only. I'm not sure when that broken. UPDATE Found and fixed the problem for next version.
Far the items that were just questions:
It will accept negative numbers just fine, but you have to change the typeData to allow it. If the typeData is blank it will only accept posative values. To accept negative numbers use something like "-1000000 1000000". Thinking about this now I see that I need to add a better way (so you don't need to know the full range). What do you think of setting typeData to "+-" to allow the full range of positive and negative numbers?
