{"action":"created","issue":{"url":"https://api.github.com/repos/InWorldz/halcyon/issues/6","labels_url":"https://api.github.com/repos/InWorldz/halcyon/issues/6/labels{/name}","comments_url":"https://api.github.com/repos/InWorldz/halcyon/issues/6/comments","events_url":"https://api.github.com/repos/InWorldz/halcyon/issues/6/events","html_url":"https://github.com/InWorldz/halcyon/issues/6","id":107434525,"number":6,"title":"Expose Grid Name through llGetEnv","user":{"login":"zauberparacelsus","id":548168,"avatar_url":"https://avatars.githubusercontent.com/u/548168?v=3","gravatar_id":"","url":"https://api.github.com/users/zauberparacelsus","html_url":"https://github.com/zauberparacelsus","followers_url":"https://api.github.com/users/zauberparacelsus/followers","following_url":"https://api.github.com/users/zauberparacelsus/following{/other_user}","gists_url":"https://api.github.com/users/zauberparacelsus/gists{/gist_id}","starred_url":"https://api.github.com/users/zauberparacelsus/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zauberparacelsus/subscriptions","organizations_url":"https://api.github.com/users/zauberparacelsus/orgs","repos_url":"https://api.github.com/users/zauberparacelsus/repos","events_url":"https://api.github.com/users/zauberparacelsus/events{/privacy}","received_events_url":"https://api.github.com/users/zauberparacelsus/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2015-09-21T02:34:03Z","updated_at":"2015-10-14T05:24:29Z","closed_at":null,"body":"This is a suggestion that I thought may be useful, which is that by passing the \"grid_name\" parameter to llGetEnv, it will return the name of the grid that the script is running on.  For example, run it on InWorldz, it'll return \"InWorldz\".  Run it on InWorldz Beta, it'll return \"InWorldz Beta\".  Run it on HalcyonGrid2000, get \"Halcyon Grid 2000\" in return.\r\n\r\nI figure that this function will be useful to scripts written for Halcyon.  If OpenSim or WhiteCoreSim include a similar extension for llGetEnv, Halcyon can probably follow that extensions convention to reduce the work needed to get opensim scripts to work with Halcyon."},"comment":{"url":"https://api.github.com/repos/InWorldz/halcyon/issues/comments/147938005","html_url":"https://github.com/InWorldz/halcyon/issues/6#issuecomment-147938005","issue_url":"https://api.github.com/repos/InWorldz/halcyon/issues/6","id":147938005,"user":{"login":"kf6kjg","id":1157224,"avatar_url":"https://avatars.githubusercontent.com/u/1157224?v=3","gravatar_id":"","url":"https://api.github.com/users/kf6kjg","html_url":"https://github.com/kf6kjg","followers_url":"https://api.github.com/users/kf6kjg/followers","following_url":"https://api.github.com/users/kf6kjg/following{/other_user}","gists_url":"https://api.github.com/users/kf6kjg/gists{/gist_id}","starred_url":"https://api.github.com/users/kf6kjg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kf6kjg/subscriptions","organizations_url":"https://api.github.com/users/kf6kjg/orgs","repos_url":"https://api.github.com/users/kf6kjg/repos","events_url":"https://api.github.com/users/kf6kjg/events{/privacy}","received_events_url":"https://api.github.com/users/kf6kjg/received_events","type":"User","site_admin":false},"created_at":"2015-10-14T05:24:29Z","updated_at":"2015-10-14T05:24:29Z","body":"Well, I figured out a \"cleanish\" way:\r\n```csharp\r\n        public string GetEnv(string name)\r\n//...\r\n                case \"grid_name\":\r\n                    ret = m_config.Configs[\"GridInfo\"].GetString(\"gridname\", \"GridInfo gridname missing from region server's Halcyon.ini!\");\r\n                    break;\r\n                case \"grid_nick\":\r\n                    ret = m_config.Configs[\"GridInfo\"].GetString(\"gridnick\", \"GridInfo gridnick missing from region server's Halcyon.ini!\");\r\n                    break;\r\n//...\r\n```\r\nThis does mean, as I stated in my region xml idea, that every region could technically have a different grid name.  An administration problem, not really a showstopper.  And this is far faster than trying to use XMLRPC calls or whathaveyou! :D\r\n\r\nI suggest that `sim_channel` and `sim_version` stay almost like they are, with some minor exceptions. I'll explain my thought process first: first, these two are copying from LL's system and should therefore be as meaning compatible as possible; second, these have existing meaning and shouldn't be upset unless there's reason.\r\n`sim_channel` to me, based on LL's and Inworldz' usage, is the software name - in this case \"Halcyon Server\". Yes that's an incompatible change from InWorldz: the product's name has changed and it cannot be called by the old name anymore, at least not without causing confusion on other grids.\r\n`sim_version` has a problem. Following the LL format makes the most sense for scripts coming from that grid, but InWorlds implemented a different format.  My suggestion is to revert it to the LL-style version numbering so that scripters get back what they expect: \"11.22.33.9876\" as documented on the LSL wiki instead of \"InWorldz 11.22.33 R9876\" or \"Halcyon 11.22.33 R9876\" as the code currently returns."}}