The Ashita Project goes live!

[atom0s]

Ashita uses the normal / common method of injection that is the most commonly used in any similar type of project that injects another DLL into a process.
All of which use standard API calls, so if Wine is complaining about this, then there is a lack of proper implementation of the emulated API that are being called.

These are the API calls used in the injection process: (Basically in order that they are called as well.)

• Create the suspended process (POL.exe)
  
  • CreateProcess (Creates the process with NORMAL_PRIORITY_CLASS|CREATE_SUSPENDED flags.)
  
  
• Create Memory Mapped File to pass configuration data to.
  
  • CreateFileMapping
  • MapViewOfFile
  
  
• Process the injection of Ashita Core.dll into the suspended process.
  
  • VirtualAllocEx
  • WriteProcessMemory
  • GetModuleHandle
  • GetProcAddress
  • CreateRemoteThread
  • WaitForSingleObject
  • GetExitCodeThread
  • VirtualFreeEx
  • CloseHandle

As I mentioned above, I am not a Linux person at all so if anyone that is familiar with Wine and perhaps coding can spot any issues here, feel free to let us know.

This is the most basic method of injection and part of it is required for Ashita to work.

[Khajit]

Any plans for some sort of temp item manager? Eg 50 billion temps load in VW.
Hit a macro with a plugin specific command to activate your temps.
Buffs start wearing
Hit macro again and it skips the ones that didn't wear off so that time isn't wasted reapplying bravers, monarchs, stalwarts and etc when I dont need to with something to fana/champions allowed to be used to overwrite the current buff. bonus points for screens.

[atom0s]

Any plans for some sort of temp item manager? Eg 50 billion temps load in VW.
Hit a macro with a plugin specific command to activate your temps.
Buffs start wearing
Hit macro again and it skips the ones that didn't wear off so that time isn't wasted reapplying bravers, monarchs, stalwarts and etc when I dont need to with something to fana/champions allowed to be used to overwrite the current buff. bonus points for screens.

Anything like this will fall into an extension so no there are no set plans for the core team to work on things like this. Not to say that it will never happen but our focus at the moment is on the core project and the shipped extensions that come with it. Feel free to pop over to our forums and leave a request post there though and perhaps one of the handful of people that are slowly picking up the project will invest their time into making it. We have a few extension developers already, and more will come in time.

[Tymon]

Yeah, thanks for the info. I wasn't asking for any kind of change to the work at all--sorry if it came off that way.

I just needed to know how it worked so that I could possibly engineer it to work myself.

[atom0s]

Yeah, thanks for the info. I wasn't asking for any kind of change to the work at all--sorry if it came off that way.

I just needed to know how it worked so that I could possibly engineer it to work myself.

If you are able to test and debug what is causing it to fail, we might be able to work on something to fix it but I can't make any guarantees. And your post didn't come off mean or anything.

[Sechs]

As for converting text files, just remove any 'input' words from your current gear swap macros if you use them.
Ashita doesn't need you to enter 'input' to do commands. Instead it's just direct input from the scripts as if you were typing them yourself.

Yes but as I mentioned before, there are a lot (well, "some" tbh, rather than "a lot") of commands which are windower-related and not game-related.
For instance the difference between wait and pause.
There are others too.
So just removing "/input" at the beginning of each line won't be enough.

Other features to the scripting weren't added as we didn't see much use of them.

It goes without saying, I can only talk for myself.
Personally I don't use spellcast a lot (I only use it for my SCH atm, and try to avoid extensive use when possible, it may be just me but I don't like things to get beyond a certain level of automatization, it takes away part of the "fun" from my gaming experience), so I still rely a lot on TXT macros.
I have a lot of them, sorted by folder. Each folder is a job.
The way I play is through keybinds.
F1-F5 (with alt and ctrl) I use to swap between jobs.
F6 displays on screen a list of current jobs-keys association.
Like F1 = MNK, alt+F1 = PUP, etc.
These are all bound in the init.txt file of Windower and I'm sure there would be no big issue in doing the same in Ashita.

F7 is a specific bind that changes each time I load a different job through the previous keys. It display job-specific keybinds, for which I use the G1-G12 keys on my keyboard.
Like: G1=TP set, G7=MDT, etc etc. They change from job to job.

Each time I press a "job key" it displays the job-specific bindings through echo (same as it does when I press F7), it swaps my macro book and it also swaps my keybinds.
On some jobs I also load/unload different plugins.


All of this stuff and probably more than I can think right now is done through windower specific commands. You can't do this with just game command.
That's why windower scripting, altough very simple, was offering a better degree of interaction for players like me, without having to resort to XML scripting (or lua scripting, if we're talking about Ashita).

Maybe it's just me, but you should seriously think about re-working the TXT macros interaction part of Ashita.

[atom0s]

If you want, upload your text scripts somewhere like Dropbox or similar. We can take a look into how you handle various things and see what other features you are wanting to see adding.

[Uzor]

Is there a plugin like the one for Windower that displays how long until various status effects like Protect wears off?

Or one that shows how long until Refresh lasts on party members.

I went through the plugin list on the website, but I didn't find one, but maybe I just missed it.

[atom0s]

Is there a plugin like the one for Windower that displays how long until various status effects like Protect wears off?

Or one that shows how long until Refresh lasts on party members.

I went through the plugin list on the website, but I didn't find one, but maybe I just missed it.

Currently, no. But you are free to post a request on our forums and see if one of the people working on various plugins wishes to tackle another project.


As for the launcher, I just posted the new beta launcher I've been working on, you can find the new topic here:
http://www.ffevo.net/topic/2918-ashita-launcher-beta/

After a short beta this launcher will be released with the main package and the source will be released / uploaded to a site such as github.
(The file is unprotected for those wanting to look at what it does already.)

Sneak peak:
http://imageshack.us/a/img825/6832/launchermain.png

More pictures in the official thread.

[atom0s]

The launcher has been updated to v1.0.0.1 to correct an issue with launching causing crashes.

Edit:

The launcher has been updated to v1.0.0.2; which includes some new features.

[atom0s]

Sorry for the triple post.

I have released the source of the new launcher here:
https://github.com/atom0s/AshitaLauncher

Feel free to browse, submit issue reports, pull requests, etc. We encourage our users to get hands on with the project.

[atom0s]

Ashita 1.0.2.5 Released

Hello everyone, have some updates to our project to share with you.

----------------------------------------------------------------------------------------------------
Ashita Version: 1.0.2.5
----------------------------------------------------------------------------------------------------
    Change: INTERFACEVERSION 1.40
    Fixed : [Core] Macro commands getting out of order.
    Fixed : [Core] Bug 10: Keyitem out of range.
    Added : [Both] Resources handling overhauled and recoded.
    Added : [Both] Resources: Added new methods for obtaining full item and spell info.
    Added : [Both] Resources: Added new methods for obtaining region and zone names.
    Update: [Extn] Bootstrap/AshitaAPI updated to reflect new resource changes.
    Update: [Extn] LuaCast events changed; removed onZoneIn/onZoneOut. Added onHandleOutgoingPacket / onHandleIncomingPacket.
    Fixed : [Extn] LuaCast: Fixed entity info exposure, ID = ID, Index = Index. Also added AnimationPlay.
    Added : [Extn] LuaCast: AshitaCore:GetResources() now implements IResources and its objects.
    Fixed : [Extn] IInventory GetEquipCount / GetEqipItemID returning gil when no item was equipped.
    Fixed : [Extn] Typo in IItem UseDeley -> UseDelay

See previous change information in our release log here:
http://svn.ffevo.net/ashita/release/ChangeLog.txt

This update has brought some fixes and a handful of requests, along with the past two updates to the project.
Some information on various plugins that you have possibly grown used to:

DrawDistance

• Now has configuration settings to automatically apply when you load this extension.

Lotomatic

• Now supports profiling and requires that you use it.
• Now supports 'passall' and 'lootall' commands.
• Now supports auto-sorting similar to LightLuggage. (Use 'sort on' command.)
• Now supports multiple items in a single line. (Separate with comma.)

Bootstrap

• Updated to handle new IResource changes. (Fully handles IResources class.)

LuaCast

• Updated to handle new IResource changes. (Fully handles IResources class.)
• Removal of onZoneIn / onZoneOut events.
• Addition of onHandleOutgoingPacket / onHandleIncomingPacket events.
• More info here: http://www.ffevo.net/topic/2868-luacast/?p=27744

This change to LuaCast allows users to create a feature full event system all inside Lua by parsing incoming and outgoing packets. This allows for an even more dynamic system based on the packets contents all through scripting.


Along with these changes we have had a handful of new member submitted extensions including the following:

• GearSwap - Allows gear swapping based on certain conditions.
• Clock - Displays real-life time.
• Alias - Allows for alias binding for short-commands.
• AshitaIRC - Allows for communicating with an IRC server in game.

Another user is in the works of an InfoBar replacement for Ashita as well.

Feel free to check out the project:
http://www.ffevo.net/forum/80-ashita/

You can also always find us on IRC at:
Server: irc.ffevo.net
Port: 6667
Channel: #fface

[Kohan]

Thank you for further updating this thread. I've been off work for a few weeks, but I've spent them sick, and I haven't even played with this once. I'm glad that you and your team have the ambition to continue working on this, and I hope you continue to do so.

[Julian]

Nice! I've always wanted an irc plugin that would let you connect to wherever, but Aikar was always a dick to me.

Looking more and more tempting to make the switch every day.

edit: Alias and Gearswap both look like good starting steps for a light "spellcast-like" replacement.

[atom0s]

Ashita 1.0.2.6 Released!

Hey everyone, more updates again! This time a lot of love for LuaCast.

----------------------------------------------------------------------------------------------------
Ashita Version: 1.0.2.6
----------------------------------------------------------------------------------------------------
    Change: INTERFACEVERSION 1.41
    Fixed : [Both] Resource dat parsing adjustments to fix invalid ability/spell data.
    Fixed : [Both] GetEquipItemID is now spelled properly.
    Fixed : [Both] ItemData by name is now const char*.
    Update: [Both] Resource ItemData is now GetItemByName/GetItemByID
    Update: [Extn] LuaCast: Added missing GetItemByName/GetItemByID functions.
    Update: [Extn] LuaCast: Added IInventory bindings to fully support inventory data in Lua.
    Added : [Extn] LuaCast: inventory.lua helper file for various inventory data.
    Added : [Extn] LuaCast: Added various extension files to extend math, string, table.
    Update: [Extn] LuaCast: Added memory handling functions.
    Update: [Extn] LuaCast: Updated main.lua for example usage.
    Fixed : [Extn] LuaCast: Fixed Player crafting information reporting wrong data.
    Change: [Extn] LuaCast: CraftSkills is now properly CraftLevels as it is in the SDK.
    Update: [Extn] Lotomatic: Added pass/loot commands to pass or roll on all current treasure pool items.
    Fixed : [Extn] AshitaAPI: Various structure definitions using wrong data types.

With this update we have a few bug fixes mostly to extensions.

Lotomatic

• Added /lotomatic pass command to pass all current items in treasure pool.
• Added /lotomatic loot command to loot all current items in the treasure pool.
• WARNING: These commands do not check if you have rolled an item already. Use with caution!

LuaCast

• Added missing GetItemByName/GetItemByID functions.
• Fixed crafting information returning wrong data.
• Fixed CraftSkills to be CraftLevels to match the SDK properly.
• Added IInventory bindings to allow users to fully read inventory info from Lua.
• Inventory reading includes:
  
  • Inventory (All inventory bags included.)
  • Storage
  • Current Equipment
  • Treasure Pool Data
• Added memory handling functions.
• Added several helper Lua files to extend some built in objects. (Math, String, Table)

With these new changes to LuaCast you can now do A LOT of customization.
Here are some new examples of whats changed:

Reading Current Equipment Information

local inventory = AshitaCore:GetDataModule():GetInventory().Inventory;
local equipment = inventory.Equipment;

for k,v in pairs( equipment ) do
    local item = GetItemFromEquipmentSlot( v.Slot + 1 );
    local itemName = function() if (item == nil) then return ''; else return item.Name; end end
    print( string.format( '[Equiment Info]: Slot: %d - ItemIndex: %d - ItemName: %s', v.Slot, v.ItemIndex, itemName() ) );
end 

Using the new memory stuff to mimic AllMaps extension:

local allMaps   = { 0xE9, 0xFF, 0xFF, 0xFF, 0xFF, 0x50, 0xE8, 0xFF, 0xFF, 0xFF, 0xFF, 0x0F, 0xBF, 0x96, 0xFF, 0xFF, 0xFF, 0xFF, 0x83, 0xC4, 0x04 };
local addr      = FindPattern( allMaps, #allMaps, "x????xx????xxx????xxx" );
if (addr ~= nil and addr ~= 0) then
    addr = addr + 6;
    
    local data = { 0xB8, 0x01, 0x00, 0x00, 0x00 };
    WriteArray( data, #data, addr );
end 

Obtaining information about a spell:

local res = AshitaCore:GetResources();
print( 'Zone 4: ' .. tostring( res:GetString( 'areas', 4 ) ) );
print( 'Zone 4: ' .. tostring( res:GetString( 'areas', res:GetString( 'areas', 4 ) ) ) );

local spell = AshitaCore:GetResources():GetSpellByID( 1 );
print( string.format( 'Spell ID: %d',           spell.ID ) );
print( string.format( 'Spell MagicType: %d',    spell.MagicType ) );
print( string.format( 'Spell Element: %d',      spell.Element ) );
print( string.format( 'Spell ValidTargets: %d', spell.ValidTargets ) );
print( string.format( 'Spell Skill: %d',        spell.Skill ) );
print( string.format( 'Spell MP: %d',           spell.MP ) );
print( string.format( 'Spell Cast: %d',         spell.Cast ) );
print( string.format( 'Spell Recast: %d',       spell.Recast ) );
print( string.format( 'Spell ResourceID: %d',   spell.ResourceID ) );
print( string.format( 'Spell IconIndex: %d',    spell.IconIndex ) );
print( string.format( 'Spell Name: %s',         spell.Name ) );
print( string.format( 'Spell Description: %s',  spell.Description ) );

print( string.format( 'Required Count: %d', #spell.RequiredLevel ) );
for k,v in pairs( spell.RequiredLevel ) do
    print( string.format( 'Job: %d -- Level: %d', k, v ) );
end 

With the new additional support files I also wrote a command parser to handle incoming commands easier and cleaner. You can use the new command parser like this. (This is from the new main.lua that is included with LuaCast)

----------------------------------------------------------------------
-- func : onHandleCommand
-- desc : Event callback for onHandleCommand event.
----------------------------------------------------------------------
function onHandleCommand( cmd, nType )
    -- Parse the command into arguments..
    local args = cmd:GetArgs();
    
    -- Validate this is a LuaCast command..
    if (args[1] ~= "/luacast") then
        return false;
    end
    
    -- Handle LuaCast wave command..
    if (args[2] == 'wave') then
        AshitaCore:GetDataModule():SendCommand( '/wave', CommandType.Typed );
        return true;
    end
    
    return false;
end
events.Add( "onHandleCommand", "luaCast_onHandleCommand", onHandleCommand ); 

With these updates to LuaCast users can now pull any data they wish from FFXI's memory and use it to their advantage to create whatever they desire.

Here is a list of all the new memory functions:

• GetFFXiBase()
• UnprotectMem()
• FindPattern()
• ReadUChar()
• ReadChar()
• ReadUShort()
• ReadShort()
• ReadULong()
• ReadLong()
• ReadULonglong()
• ReadLonglong()
• ReadFloat()
• ReadDouble()
• ReadArray()
• ReadString()
• WriteUChar()
• WriteChar()
• WriteUShort()
• WriteShort()
• WriteULong()
• WriteLong()
• WriteULonglong()
• WriteLonglong()
• WriteFloat()
• WriteDouble()
• WriteArray()

Feel free to check out the project:
http://www.ffevo.net/forum/80-ashita/

You can also always find us on IRC at:
Server: irc.ffevo.net
Port: 6667
Channel: #fface

[Sechs]

Wow, things are getting more and more interesting it seems

[atom0s]

Here's a very rough API page for LuaCast now:
http://www.ffevo.net/wiki/index.php/LuaCast_API

Doesn't really detail everything but I'll update it over time.

[Yugl]

Does this mean we can use Lua as a spellcast or do we still need someone to build the user-friendly stuff?

[atom0s]

Does this mean we can use Lua as a spellcast or do we still need someone to build the user-friendly stuff?

It has the full potential to be used as a Spellcast replacement now but it still needs user written stuff to actually begin to work how people want it to.

[Pebbs]

Does this mean we can use Lua as a spellcast or do we still need someone to build the user-friendly stuff?

Yugl, could you clarify "user-friendly stuff"? Spcifically what would make it easier?