Hello, you need to inject into NostaleClientX.exe for now, an update is coming in few time that will require to replace EWSF.EWS in Nostale directory by the DLL.Quote:
When i try to inject the dll, nothing happens. Atleast a console window should pop up, i guess?
[Only registered and activated users can see links. Click Here To Register...]
1)Quote:
1) How can I hide the console when the game gets booted and make the 'loading screen appear'?
2) Is there any tip on how to make a 'box' have 'item' in it? Like the original upgrading window that can contain an equipment with drag and drop inside the empty box and then show the item inside it or inventories that contain item icons
void InitLogger()
{
Logger::Load();
Logger::IndentModuleName(" ");
}
void InitLogger(){}
extern "C" __declspec(dllexport) void __declspec(naked) FreeNostaleSplash() noexcept
{
__asm
{
pushad;
pushfd;
}
example->OnFreeNostaleSplash();
th = new std::thread([]
{
MainThread(hModule);
});
th->detach();
__asm
{
popfd;
popad;
jmp freeNostaleSplash
}
}
extern "C" __declspec(dllexport) void __declspec(naked) ShowNostaleSplash()
{
__asm
{
pushad;
pushfd;
}
InitLogger();
HMODULE origEwsf = LoadLibraryA("EWSF_orig.dll");
freeNostaleSplash = GetProcAddress(origEwsf , "FreeNostaleSplash");
showNostaleSplash = GetProcAddress(origEwsf , "ShowNostaleSplash");
example = new Example(config);
example->OnShowNostaleSplash();
__asm
{
popfd;
popad;
jmp showNostaleSplash
}
}
FARPROC freeNostaleSplash, showNostaleSplash;
Hi mate,Quote:
Well, nobody have answered you so I'll, he haven't got time to work on it past month so as well as there is no ETA, there is no date of release, not even sure it come out one dayQuote:
I would like to say I love your project. I've been having fun with that for a while now.
I wanna ask - any ETA for a new version release? Someone told me that you were planning to rewrite big part of the code (mostly packet management) and I wonder if there is any ETA for that update.
anyway - thanks for the release!
Seems like this "huge update" never went live :(Quote:
Quote:
To clarify a bit, me and a friend were working for few months on an already public server and therefore we added a lot of features/classes to the SDK but we ran into some limitations: there are a lot of things that should be reworked.
I don't want to publish the SDK in its current form, even though I heard some leechers were trying to sell some things I did for this SDK (typically, the trophy thing etc).
I am sending this message for two things:
1) the future of this project
2) to ask you for feedback, future testing, mostly community questions
1) The SDK will now be decomposed in multiple parts:
- An API decomposed:
- A low level layer - which basically represents the memory layout - that is used internally but that can also be used by you, especially when modifying something already existing
- A higher level layer - which uses the low level layer - that will be the recommended layer to use, when creating a new widget
- A module mechanism: you can create plugins that will be automatically managed by the inner "runtime". The goal is: you code the UI (or generate, cf. below), you code the logic of the UI, you ignore the rest)
- A huge documentation, that will come way later (we want to make the new architecture stable enough before writing it)
- A website containing:
- A Widget Builder (we started this project few days ago) that allows you to draw the UI you want, with the assets you want, which generates all the UI code, which is (as far as I know) the main issue people add, working with my SDK. Think of it as Qt Creator, or the GUI designer for C#/VB.net, or Figma. We are thinking of making this a "premium" feature (in the sense that it will not be available freely)
- A marketplace, where plugin (can be widget, can be an invisible feature, ...) creators can sell their creation code. We plan to add an audit mechanism to prevent bad people from attacking your server (even though you would have access to the code anyway). We are looking for suggestion on how to prevent leechers to get a plugin and share it, if you have any idea please feel
freeobligated to share it here!- Possibly, later on, more tooling (we have some amazing (we think) ideas, but we lack of time and hands
Regarding the current features such as the "NpcTalkRangeManager", "DiscordManager", ... Will become widgets available (freely) on the marketplace, meaning that the SDK itself will be a lot simpler, leaving us the time and energy to iterate and improve it. It also means that, for the game widgets, functionnalities per se, we will rely on you (ex: you created a nice clock? Come on the marketplace, share it freely, or share it with a fee).
2) For this part, I will ask questions and hope to have answers (please, if you ever tried/successfully created a widget, share with me your answer - users' answers are also appreciated, obviously).
- What were the biggest pains you experienced, while using the SDK?
- Were you able to compile it easily? (e.g. was reading the README.MD enough?)
- Were some players unable to run the game, while using the project you compiled with the SDK? Were you able to solve it? (If so, please describe how)
- Are there core features that you are interested in? By core features, I mean "blocks" that can be used to create other things (e.g. The widgets classes, ...), or stuff that deserves (should!) to be present on every private servers (like the possibility to add a custom cryptography for the packets but also for the game files, ...) - Features that we should not expect to see on the marketplace, basically.
- If you own a private server, would you be able to test new versions of the SDK?
- If you own a private server, would you be able to test community's plugins (from the marketplace) when we are auditing one?
- Would you be interested in the Widget builder?
- Would you be interested in the marketplace?
- Are you interested in a Discord group for everything (the SDK, the website)?
- I probably forgot interesting points, please, feel free to give your feedback on whatever you think is important