If expr is a numerical expression, it means a story index: only the number of stories and the information on the specified story is returned.
So if you have 'expr' and a number (say 0) then you will get info only for the storey starting at story 0.
Not sure how this works in the USA version as there is no 0 story.
If you set it to 1 then you will get info for story 1.
I think your problem will be you can't REQUEST the story because that can only be done in the 2D script - where you then can't save parameters.
You can't REQUST the current story in the parameter script because this can no longer be done.
If you set 'expr' as a string then you can get all info for all storey as an array.
Again from the manual ...
n = REQUEST ("STORY_INFO", "", nr, t)
FOR i = 1 TO nr
nr = STR ("%.0m", t [4 * (i - 1) + 1])
name = t [4 * (i - 1) + 2]
elevation = STR ("%m", t [4 * (i - 1) + 3])
height = STR ("%m", t [4 * (i - 1) + 4])
TEXT2 0, -i, nr + "," + name + "," + elevation + "," + height
REQUEST Story_Info will work in 2D and parameter scripts.
I just don't know a way that you can find the current story in the parameter script so you can save a parameter with the height for that story.
One of the forum moderators. Versions 6.5 to 25 Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10 Dell Precision 3510 - i7 6820HQ @ 2.70GHz, 16GB RAM, AMD FirePro W5130M, Windows 10
The solution of my case was to use the "Story_Info" request (as you told me) and creating parameters (with arrays) using the request extracted data.
After that I called the "Home_story" request in order to get the proper "index" of current story.
With a combination of this parameters I could find the current height.
With GLOB_CSTORY_HEIGHT things were pretty much easier. Now the road is more winding.