Quote:
Originally Posted by novicehacker
We can also use .SetParameter("name", object) to pass objects to javascript (running into a few bugs with it atm though, but I'm working on sorting them out). On a side note we can also subscribe to events with javascript code so that we can just fire events like onmessagerecieved, onlevelup, etc instead of needing the javascript code to keep checking for those actions as well.
I'm actually open to suggestions on the structure of the pw data in the backend as you're much more familiar with the information available.
|
What I currently do is this:
I have a PWProcess class that contains all the pw objects and functions, which I call from the GUI layer, so kind of like we will have with the javascript.
The PWProcess contains objects that are structured pretty much like PWI is, as this seemed to be the natural way to go about it. (e.g. a player object that contains functions to move, an itemList object as inventory which contains item objects, etc)
I have one shared Dictionary object (shared by all threads and classes) with all the offsets, read straight from the database, like this:
Code:
private void loadOffsets()
{
if (!loadedOffsets)
{
//Get offsets from database
//Open connection
OdbcConnection odbcConnection = new OdbcConnection(connectionString);
openConnection(odbcConnection);
//Read offsets table
OdbcCommand selectOffsetsCommand = new OdbcCommand(selectOffsets, odbcConnection);
OdbcDataReader offsetsReader = selectOffsetsCommand.ExecuteReader();
string name = "";
int value = 0;
while (offsetsReader.Read())
{
name = (string)offsetsReader[0];
value = (int)offsetsReader[1];
offsets[name] = value;
}
Debug.WriteLine("Read {0} offsets from database.", offsets.Count);
loadedOffsets = true;
//Close connection
odbcConnection.Close();
}
}
Then in each class such as player I read the offsets into local variables. This is not necessary of course, and does add a bit of bloat to each class (not that much), but it saves having to access the dictionary each time and ensures easier modification of database offset names (i.e. you don't have to track them down through everywhere in the class the offsets are used).
Then I 'hide' all the memory reading / writing parts by using properties like this:
Code:
public PWParty party
{
get
{
int address = MemFunctions.MemReadInt(processHandle, getPlayerAddress() + off_player_party);
if (address == 0)
{
return null;
}
return new PWParty(processHandle, offsets, address);
}
}
public float expLostOnRevival
{
get { return MemFunctions.MemReadFloat(processHandle, getPlayerAddress() + off_player_expLostOnRevival); }
set { MemFunctions.MemWriteFloat(processHandle, getPlayerAddress() + off_player_expLostOnRevival, value); }
}
Where, depending on the type of variable, they get a get and/or set property. There's about 20 or so classes like that.
Quote:
I also noticed you were tinkering with getting custom displays inside pw (saw your autopot screen somewhere), how complicated is that? If we could rig up some really basic gui creation functions that people could call that would be pretty epic as well, however I have no experience with that so I'm not sure how feasible it is.
|
Displaying stuff in itself isn't hard, but you have to do it in C++. Designing the menus and such is a bit of a hassle if you want to maintain the feel of PWI as you're stuck with their image files. The biggest issue is really dragging and dropping items/skills from a PWI menu to your own, as you have to work around some stuff then, and it makes displaying stuff a bit harder with all the z-axis thinking going on.
If all you want to do is some simple text showing and whatever, then it won't be hard at all, as long as you somehow inject a dll (written in C++) into the process. Then again, you'd have to set up some form of communication between the dll and your own C# framework, which I haven't done before, although it shouldn't be that hard.
dumbfck has been doing some very interesting work on an alternative method of ingame GUI creation, which I believe is more promising if you really want something modular. I'm not sure how far along he is exactly, but it was looking to be really sweet.
One thing I noticed, Jint doesn't support threading? That might be an issue if you have a multitude of scripts each being used for a varying amount of PW clients. I was also thinking, if displaying an inagme GUI is somehow not working out, maybe add hotkey support. Allow the user the numpad keys 0-9 as hotkeys to call some specific function in their script if they have it set up in their settings.
Were you planning on having the javascript side of things get a list of all the PW clients, so the user browses through the clients on there, or do you plan on having the javascript executed for each active client?
edit:
What I mean is, do you have something like this in the javascript
:
Code:
var clientArray = test.getPWclients("elementclient");
for(i = 0; i < clientArray.Length; i++)
{
print(clientArray[i].MainWindowTitle);
}
or do you have something like this in the loop structure, where you pass each individual client to the javascript as parameter:
Code:
if ((counter + i) % userscripts[i].tick_delay == 0)
{
Process[] pwClients = Process.GetProcessesByName(processName);
for (int j = 0; j < pwClients.Length; j++)
{
userscripts[i].loop(pwClients[j]);
}
}
edit: on second thought, that would probably require a separate running script for each individual client, or quite some hassle with the JS global vars (all as arrays for the individual clients)
Obviously, not exactly like this, as you won't be giving the script access to the actual processes, but more an encapsulation of them with whatever functions you need, like I mentioned before. There's quite a difference though, as the user either views all the processes as individuals (like in prophetbot) or as a whole (for example bots in parties, like I do). One way would perhaps be slightly more complex, but as we're assuming the user can code javascript that might not be an issue.
Then again, there are different levels of user, those that create the scripts, and those that merely adjust the settings in the scripts created by others.
Sorry for the wall of text, usually I'll be adding my thoughts over time with the edit button and as the day goes by things ... expand :D