View Single Post
  #45  
Unread 01-26-2005, 11:18 AM
ger's Avatar
ger ger is offline
Steward of the Faithful
This person is a EQ2Map developer.
Interface Author - Click to view interfaces
 
Join Date: Nov 2004
Server: Antonia Bayle
Posts: 580
Default

Quote:
Originally Posted by Morgor
Here are a few questions for SOE:

1. What scripting functions are available (if statements? math operations (other than +, -, *, /)? string manipulation?), and what is the proper syntax for each of these?

2. What types of ISO entities are allowed? (I noticed that " works, but   and some others seem to cause problems)

3. Is there other DynamicData, other than the DynamicData objects in equi_gamedata? If so, how do we access them?

4. What are acceptable values for the DynamicData property of objects? (Can we perform math or other functions on DynamicData?)

5. Can we have a more complete list of objects, their acceptable properties and events, and the function of these objects, properties, and events? The Word document is a nice primer, but only serves as an outline, when it comes to describing objects, events, and properties.

6. Certain objects have implied relationships (such as ImageStyle objects and RectangleStyle objects, for buttons). Could you please give us more detail on how these associations work, and document dependencies?

7. Almost all of the default pages have some sort of "magic" going on with them, that is not dependent on DynamicData or events (for example, how does the quest journal work?). How can we access this data? Are there reserved names?

8. How do we access root from inside an event value? (root.parent.object.property doesn't seem to work, and neither does / or parent.parent.parent beyond a page that has ismodule set to true)

9. Can we store and read data in text documents? If so, how?

10. How can we send / commands from our interface pages? Some already work, but others (like /show_window) don't. Many of us would like to show our custom interface pages by using OnPress events, etc.
Just a note on the scripting/command function questions. It seems that the EQII macroing system was kept intentionally limited to prevent in-game automated play problems. I would expect that certain features we'd like to see in mods are going to be similarly limited for exactly the same reason—no sense gimping macros only to have players get around it by installing mods that do the same thing.
Reply With Quote