In 2.1 the event you're looking for is 'Jumping' rather than 'Jumped'. Jumped triggers in 2.2 only, and occurs when you arrive at the system. Jumping triggers in both 2.1 and 2.2, and triggers when you enter witchspace.
- Status
In 2.1 the event you're looking for is 'Jumping' rather than 'Jumped'. Jumped triggers in 2.2 only, and occurs when you arrive at the system. Jumping triggers in both 2.1 and 2.2, and triggers when you enter witchspace.
I've just released 2.0.0b4 This contains a number of fixes and tidy-ups. Instructions are the same as in the original post.
At this point EDDI 2 is pretty much ready to go. It is missing a few bits and pieces that will not be available until after 2.2 goes live, but I expect to release a full version of EDDI within a day of 2.2 hitting the servers.
Comments and suggestions on the various features EDDI provides are of course welcome. If you find any bad speech or other problems please let me know.
At this point EDDI 2 is pretty much ready to go. It is missing a few bits and pieces that will not be available until after 2.2 goes live, but I expect to release a full version of EDDI within a day of 2.2 hitting the servers.
Comments and suggestions on the various features EDDI provides are of course welcome. If you find any bad speech or other problems please let me know.
I understand that the 'Jumping' event comes from the NetLog and 'Jumped' comes from the JournalLog.
I am attempting to use 'Jumped' in 2.2 beta 5... ((EDDI commander continued)), ((EDDI location)), ((EDDI docked)), ((EDDI undocked)), ((EDDI entered supercruise)), & ((EDDI entered normal space)) are working fine for me.
Agreed that 'Jumping' works fine, and so does 'Shutup' ;-) , but I have a specific use for the ((EDDI jumped)) event.
Thanks for your patience, btw.
Last edited:
If it's 2.2 then yes the jumped event should trigger. I'll take a look to make sure it hasn't gone AWOL.
Yeah every item can be customised or just disabled.
I made a great little addition to the "Commander continued" earlier today just about got it working and something happened and something crashed and I didn't have a chance to save it or write it down.
I was thinking when the commander continued event happens it tells you what group server your on, and what ship your flying. Example:
"Welcome back commander, you are in the Lave system onboard your Fer De Lance "Death Blossom" flying the Mobuis group!" ofcourse the last bit would change from Solo/group name/open/CQC.
I was so bummed out when I crashed out and lost it and I didn't have time to work on it again.
Part of what I could remember
Is it ok to be asking for little bits of help on scripts I may be trying to write, dont wanna bog down the thread with these little bits and bobs.
Another little thing I drew up was a Cargo Report which I called from VA, but i found it never updated from the initial cargo & would repeat the "we are carrying" part for every item of cargo.
I was thinking when the commander continued event happens it tells you what group server your on, and what ship your flying. Example:
"Welcome back commander, you are in the Lave system onboard your Fer De Lance "Death Blossom" flying the Mobuis group!" ofcourse the last bit would change from Solo/group name/open/CQC.
I was so bummed out when I crashed out and lost it and I didn't have time to work on it again.
Part of what I could remember
Is it ok to be asking for little bits of help on scripts I may be trying to write, dont wanna bog down the thread with these little bits and bobs.
Code:
Welcome commander
{if event.mode = "Group":
you've just entered {event.group} group.
|elif event.mode = "Solo":
you are in Solo
|else event.mode = "Open":
you are in Open
}Another little thing I drew up was a Cargo Report which I called from VA, but i found it never updated from the initial cargo & would repeat the "we are carrying" part for every item of cargo.
Code:
{for cargo in ship.cargo:
We are carrying {cargo.amount} tonnes of {P(cargo.commodity.name)}.
}
Last edited:
FYI... ED 2.2 b6, EDDI 2.0.0b4, and still no trigger on ((EDDI jumped))
Also, still getting the playback of the 'Jumping' script from the Speech Responder after unchecking the 'Enabled' check box.
Also, still getting the playback of the 'Jumping' script from the Speech Responder after unchecking the 'Enabled' check box.
Last edited:
I'm having a particularly bad evening.
Bad update in Win 10 and had to roll back to system restore point supposedly time-stamped as earlier this evening. Restore worked fine except now EDDI won't launch at all and Voice Attack will not register it.
I've tried several unisntall and reinstalls, tried reinstalling .net packages... no joy.
Any suggestions would be appreciated.
Edit: A little digging and I found I'm repeatedly getting Crash Dumps generated and I'm getting this in the eddi.txt file in my AppData/Roaming/EDDI folder...
2016-10-12T04:16:20 EDDI:.ctor EDDI 2.0.0b4 starting
2016-10-12T04:16:20 EDDI:.ctor [E] Failed to initialise: System.NullReferenceException: Object reference not set to an instance of an object.
at Eddi.EDDIConfiguration.FromFile(String filename)
at Eddi.EDDI..ctor()
Edit #2: Ok, figured out that the configuration file got corrupted. Deleted the folder and EDDI now runs. Re-entered all the config data and I'm back.
Hope this minor crisis was educational for the rest of you! ;-)
Bad update in Win 10 and had to roll back to system restore point supposedly time-stamped as earlier this evening. Restore worked fine except now EDDI won't launch at all and Voice Attack will not register it.
I've tried several unisntall and reinstalls, tried reinstalling .net packages... no joy.
Any suggestions would be appreciated.
Edit: A little digging and I found I'm repeatedly getting Crash Dumps generated and I'm getting this in the eddi.txt file in my AppData/Roaming/EDDI folder...
2016-10-12T04:16:20 EDDI:.ctor EDDI 2.0.0b4 starting
2016-10-12T04:16:20 EDDI:.ctor [E] Failed to initialise: System.NullReferenceException: Object reference not set to an instance of an object.
at Eddi.EDDIConfiguration.FromFile(String filename)
at Eddi.EDDI..ctor()
Edit #2: Ok, figured out that the configuration file got corrupted. Deleted the folder and EDDI now runs. Re-entered all the config data and I'm back.
Hope this minor crisis was educational for the rest of you! ;-)
Last edited:
I made a great little addition to the "Commander continued" earlier today just about got it working and something happened and something crashed and I didn't have a chance to save it or write it down.
I was thinking when the commander continued event happens it tells you what group server your on, and what ship your flying. Example:
"Welcome back commander, you are in the Lave system onboard your Fer De Lance "Death Blossom" flying the Mobuis group!" ofcourse the last bit would change from Solo/group name/open/CQC.
I was so bummed out when I crashed out and lost it and I didn't have time to work on it again.
Part of what I could remember
Is it ok to be asking for little bits of help on scripts I may be trying to write, dont wanna bog down the thread with these little bits and bobs.
Code:Welcome commander {if event.mode = "Group": you've just entered {event.group} group. |elif event.mode = "Solo": you are in Solo |else event.mode = "Open": you are in Open }
Another little thing I drew up was a Cargo Report which I called from VA, but i found it never updated from the initial cargo & would repeat the "we are carrying" part for every item of cargo.
Code:{for cargo in ship.cargo: We are carrying {cargo.amount} tonnes of {P(cargo.commodity.name)}. }
Was it EDDI that crashed, or Windows? Were there any messages on-screen? If you could send me the %APPDATA%\EDDI\eddi.log and let me know the rough time/date it crashed then I can take a look to see if there is any particular issue.
Regarding the script, when you start up you will see two events. You receive a "Commander continued" event when you select the mode in which you want to play, and a "Location" that provides your location. The default for "Commander continued" is simply:
Code:
Welcome back {F("Honorific")}.where 'Honorific' is a script that works out what to call you depending on where you are and your local superpower status. You are certainly on the right lines with the script to say which mode you are in, you could add the following:
Code:
{if event.mode = "Group":
You are in the {event.group} group
|else:
You are in {event.mode}
}
aboard {ShipName(event.shipid)}.then the "Location" event will give you the details of where you are.
Note that if you are testing this in the 2.2 beta then the cargo won't update because the only place to obtain cargo (and commodities, and outfitting) is from the companion API, and that only provides the information from your live (2.1) ship.
Yeah I've found I've had to completely uninstall and delete EDDI2, reboot and reinstall helps with getting it back running at times. If you have custom personalities you've made, make a copy from the AppData/roaming/EDDI/personalies folder i think its called just to be safe
For the first item, I just checked it on my local system and edd.log shows the event turning up:
2016-10-12T11:12:48 VoiceAttackPlugin:VA_Init1 Searching for command ((EDDI jumped))
2016-10-12T11:12:48 VoiceAttackPlugin:VA_Init1 Found command ((EDDI jumped))
2016-10-12T11:12:48 VoiceAttackPlugin:VA_Init1 Executed command ((EDDI jumped))
Please could you start VoiceAttack, and let me know what it says in the log?
For the second item it appears that although the UI is updating when you check or uncheck enabled it isn't saving. I'll take a look and fix this: thanks.
UPDATE
Ah wait, is this when you're using the default personality or with a custom personality? If it's for the default personality then the "Enabled" checkboxes shouldn't be alterable, as you can't change the default personality. I'll change it so that these checkboxes are not accessible for the default personality.
Last edited:
What does it do? What does the eddi.log say for this speech?
ok I think I got the right bit from the eddi.log as its getting pretty long now
Code:
2016-10-12T12:30:57 ScriptResolver:resolveScript [D] Turned script Welcome back {F("Honorific")}.
{if event.mode = "Group":
You are in the {event.group} group
|else:
You are in {event.mode}
}
aboard {ShipName(event.shipid)}. in to speech Welcome back Lieutenant. You are in aboard your Anaconda.
Last edited:
Okay I took a look at this and the issue is that there's a define kicking around in the code that turns 'Group' in to 'Private group'. This isn't very pleasant, so I'm going to change it for the next release.
If you really want it to work now then you can change the middle bit of code to:
Code:
{if event.mode.name = "Private group":
You are in the {event.group} group
|else:
You are in {event.mode.name}
}but it will stop working come the next beta. The version you have at current will work with the next beta.
I can wait till next release if the current coding will work. in the mean time I can add my ranks & percentages etc.
Another thing I notice when I managed to jump into a conflict zone that the "Bond awarded" didn't always trigger. I also changed it a little from default so it would tell me where I got the reward from but never says it. I'll c&p it next time I'm at comp.
Totally loving working on scripts & big thanks for all the help you giving me.
Another thing I notice when I managed to jump into a conflict zone that the "Bond awarded" didn't always trigger. I also changed it a little from default so it would tell me where I got the reward from but never says it. I'll c&p it next time I'm at comp.
Totally loving working on scripts & big thanks for all the help you giving me.
When I first started EDDI 2.0 b1, I was exploring and noted that I couldn't edit/view any of the speech responder scripts without creating a copy. So, I created a copy to peruse the scripts and study Cottle.
All my experiences, up to this morning (CST here), had been in an exact, unaltered copy of the default scripts with all events enabled and I was consistently not getting an orange dottted, ((EDDI jumped)) message in the Voice Attack log, following a successful FSD system jump. I even deleted the copied personality and created a new copy of the default personality, with same results. Strangely, I never tried running off the default script.
After my Windows update debacle last night, I was forced to re-install EDDI with a blank slate and again created an exact copy of the default script with all events enabled.
After pondering your above comment, this morning, I checked again on ((EDDI jumped)) triggering in both the default and copied personalities and... it's triggering in both now.
I have no explanation for the change, my profile's ((EDDI jumped)) command has not been modified in any way and the personalities are still the default and an exact copy of the default.... but, heh, it's working now.
Apparently I have a gift for breaking it... so I'll keep trying and let you know what I find [cool]
- Status