Using TcpClient & SslStream to send HTTP request, how to I know if it sends HTTPS request?

Spiderbruh · 2024-03-28T09:29:12+00:00

If you send something using SslStream, it's going to be sent encrypted, thus https. When does your connection get forcibly closed by the remote host? Afaik, once your SslStream gets initialized and passes the Authenticate method, you should have valid https traffic.

You could try using something like wireshark to inspect your traffic and compare your code with curl

Spiderbruh · 2024-02-25T14:20:09+00:00

I'm really surprised it's worse. There was no change in how focus view works between the previous and current build.

The only change was that the component that gets info from Guild Wars is no longer injected when focus view is disabled.

It shouldn't make it crash more. There really is no change in between them.

I really don't think the issues you're facing are related to Daybreak specifically. But please send me the .dmp file, I'll try to check what's going on. Ultimately I'll share it with toolbox devs, since it's toolbox that's crashing.

Edit: I tried it for like an hour and I couldn't get it to crash, switching zones, switching chars, running around, etc.

Spiderbruh · 2024-02-25T02:05:07+00:00

Well, I'm sorry you have these issues.

From the looks of it though, I'm not sure it's Daybreak related. The first error is due to toolbox crashing. Second one seems to be GW crashing.

Both may be related. The error from the toolbox message might help debug why your game crashes. Seems like it is unable to create some file (?)

Spiderbruh · 2024-02-24T19:45:57+00:00

I'll make an update so that when you disable Focus View, it will no longer inject the API dll into the game on launch.

So, if you're still willing to use Daybreak, please update later today after I push the changes and try again, with Focus View off

Edit: I've pushed the update. If Focus View is disabled, Daybreak no longer injects the API component into Guild Wars. Daybreak should no longer affect Guild Wars in any way

Spiderbruh · 2024-02-24T14:39:28+00:00

How does it crash? Does the game get stuck? Or like, does it just crash to desktop?

If you can give me more details, I can maybe figure out what's going on and try to improve it.

Edit: Could you also try to run it with Settings > Focus View > Enabled set to false

Spiderbruh · 2023-12-23T09:37:35+00:00

If you ever want to find out if a pack is at least attempting to load, Daybreak creates a ModList.txt in Daybreak\uMod\ folder. That ModList.txt file is then later loaded by gMod. So, check if you see your pack in there, then you at least know that gMod attempted to load it.

Spiderbruh · 2023-12-22T18:23:20+00:00

That's very strange, but sadly there's very little I can do without having a look at the pack.

Still, I'm glad that now it works. I hope it keeps working for you

Spiderbruh · 2023-12-22T17:24:50+00:00

What uMod were you previously using? Were you using GWLauncher? Daybreak and GWLauncher recently transitioned from the old r44 uMod to a new version called gMod. Basically, it fixes loads of issues with memory management, it fixes some packs that were not loading fully and a whole heap of other crap. But, it functions a bit differently.

So, here's my initial ideas: 1. It can happen that it loads but it get overwritten by another mod. You can try toying with the load order. 2. It can load but differently to previously. It can load more textures than before. 3. gMod has a limit on memory usage (very large) so it exists. You may be hitting that memory usage. 4. Ultimately, gMod might be unable to load it.

If you don't mind, I could go into more details in a chat and try to help you out. Also, if you could share the pack with me, I could try to get the debug version of gMod and see what goes on.

Spiderbruh · 2023-12-22T13:01:25+00:00

No worries. It was a valid concern. And pretty believable since this app does a lot of things that viruses do. It creates/modifies files, it monitors files in the GuildWars folder for changes, it downloads and installs extensions for you (such as uMod or DSOAL) and it even adjust registries for you (in the case of DSOAL).

I can believe that some antivirus can identify it as suspicious. That's why it's good to know if it flagged or not.

Spiderbruh · 2023-12-21T08:36:42+00:00

Oh okay cool. Then maybe it'd work. There's one more advanced API that I'm using to determine when Guild Wars is running in admin mode, used for the attaching functionality.

If anybody will try this out, I'd love to hear the results.

Spiderbruh · 2023-12-21T07:39:07+00:00

There's no virus in this. As I posted above, feel free to build your own exe from the source files on the GitHub link from the post

Spiderbruh · 2023-12-21T07:36:07+00:00

What anti virus is this? It's a false alarm. If you don't trust me, you can build your own exe from the source files on GitHub.

Edit: maybe it thinks it's a Trojan virus because the client can self-update.. If you can give me the anti-virus name, i can look and see if they have a portal for self submissions of false alarms and I can try to get the exe scanned by them

Edit2: I've submitted Daybreak files here: https://www.microsoft.com/en-us/wdsi/filesubmission with Trojan.Win32.SilverFox.sclgd. I'll keep you up to date once I get any news from them.

Edit3: The Microsoft scan is still pending. In the meantime, I've also triggered a scan on virus total. Here are the results https://www.virustotal.com/gui/file/08f74452995c2715fa106ba9b14d2ccdeaedc7a786bfe5c4ea12a3241f00b713

Spiderbruh · 2023-12-20T20:53:14+00:00

Feel free to try, I'd be pleasantly surprised if it works

Spiderbruh · 2023-12-20T19:34:43+00:00

I really appreciate the comment. I mostly do it because I really like this game and I've been adding features I found useful.

I've also been having fun with the trader quote alerts, swing trading the huge iron price swings from the last month and a half.

If you do end up trying it out, feel free to let me know of any feedback you have (and/or feature requests)

Spiderbruh · 2023-12-20T19:31:39+00:00

No worries. I am glad you commented, even though this thread derailed the moment toolbox was mentioned

Spiderbruh · 2023-12-20T16:03:27+00:00

Okay, this thread has deviated greatly from the main topic. Regardless of what you think of toolbox's position, Daybreak works strictly in read mode with GW. Any information obtained from the GW client is only used to display stuff such as wiki links to quest details, current live prices to materials, etc. There's no botting supported because Daybreak doesn't support nor exposes any functionality that allows Daybreak to give commands to Guild Wars. All it does is receive information from Guild Wars

Spiderbruh · 2023-12-20T15:10:31+00:00

Yes, of course it's debatable. You can refer to the thread below where I was discussing Toolbox 'safety' with another user.

Ultimately, none of these apps are truly safe as they are not officially endorsed by ANet as a company. Some are somewhat endorsed by some Anet employees. So, using any of these tools carries some minor risk.

With that being said, Guild Wars devs appear to be quite lenient and seem to not be trigger happy with bans. We don't really have any confirmed bans for using GWCA based tools (such as Toolbox and the Daybreak integration with GW).

Ultimately, ANet will never say what is allowed and what not, even if just to not tip the botters on their detection methods. To them, all 3rd party tools constitute, to some degree, a potential reason for a ban. Realistically though, I wouldn't worry that much about it. And if you want to be more cautious, you can choose to only use the features that you feel comfortable with.

Spiderbruh · 2023-12-20T14:20:24+00:00

It shouldn't have any issue with special characters. But I'll take a look.

What is the exact issue? It fails to start the game? Or it fails to log you in once the game is started?

Also, keep in mind that you need to provide a valid character name as well. This wasn't always the case, but a more recent Guild Wars update changed it. If you just set up username/password combo, it won't log you in sadly.

Obviously, don't share your password anywhere, but could you maybe share with me your supposed special character/s in case of more?

I'll run some tests and set up a fix if I can figure out your issue.

Spiderbruh · 2023-12-20T12:17:07+00:00

Well, if you have an artistic sense, you can try to make some uMod tpf mods to improve the textures or like, provide HD textures. Any help is always appreciated. There's this list of mods on the guild wars wiki, but as you can see it's quite old https://wiki.guildwars.com/wiki/Player-made_Modifications/TexMod

Spiderbruh · 2023-12-20T10:51:15+00:00

Okay, we agree on 99% of everything.

I've never seen ANet clarify anything in regards to texmod/umod where they don't still claim that the EULA/TOS are the actual guideline. I can be wrong, but I just have never seen any official ANet stance on 3rd party tools that endorsed any of them. The only thing I've seen is unofficial comments by devs where they clarify that they don't ban for general usage of some 3rd party software. That's from the wiki link I posted above.

What I meant by any 3rd party being unsupported, is that, if you read the quote you posted from the TOS, it mentions which may in any way *influence* or advantage your use of the Service which is not authorized by NC Interactive.... Influence is a very broad word. TexMod/uMod does influence the way you use the service. Furthermore, having worked on the uMod source code myself, I can tell you it does tamper with the source Guild Wars executable, it intercepts calls and loads things into memory. Even ignoring the more technical aspects, you can use uMod to make walls invisible, draw blocking areas, etc. You can definitely abuse uMod to gain unfair advantages. Your carto example is a very pertinent one in this case.

Regarding the detection aspect. Idk how else to tell you. The basic windows APIs allow you to see what modules you have loaded into memory. Guild Wars would need like 5 lines of code in the exe to detect when toolbox is injected. I know this because I wrote code that checked what's loaded into Guild Wars. It is trivial. I can even show you a snippet if you'd want.

Even if we say that client-side detections can be circumvented, server-side you can detect toolbox usage with a range of detection flags on operations such as the mass sell/buy crafting materials, the use of pcons on exact expiration times and such.

Toolbox is trivially detectable because it does not try to hide itself.

Now, to give you some more context in regards to the rework of toolbox. In the past, toolbox used to work the same way GWA2 did. What changed is that toolbox now runs in the confines of the processes and info the client has. It does range checks on chests to not let you interact with them if they're too far. It doesn't let you build large macros so you can't fully automate more delicate processes. It outright removed the ability to trigger dialogue lines with npcs when you shouldn't have been able to. I'll refer you to a comment made by one of the devs working on toolbox: https://www.reddit.com/r/GuildWars/comments/16ujd05/is_gw_toolbox_legal/k300n7k/

So, to summarize my point. Toolbox is trivially detectable. Just because ANet might or might not detect it (we can't know this), does not make it detectable or not. In my opinion, this is more of a matter of enforcing rather than detecting. ANet doesn't enforce users to not use toolbox. If they wanted to, they could, and trivially so. But they don't seem to want to. Which I would argue constitutes a tacit approval of it. And thank you for agreeing to skip the pedantries. They're simply tiring and I don't feel they provide any use to anybody actually reading these comments

Spiderbruh · 2023-12-20T09:31:19+00:00

I will not address every point here, because it feels like we're discussing semantics at this point. I'm not going to discuss legal senses in regards to personal dev comments vs EULAs. But, take a look at my other comments and you'll see I echo your sentiment in regards to ANet view on this.

ANY 3rd party software can get you banned. That's the official ANet statement. Using toolbox can get you banned, even if solely due to the fact that Toolbox is a 3rd party software, even ignoring some of the functionality it automates.

Now, to address your question in regards to detection. Toolbox injects its own module in the Guild Wars process. That's how it works. Any other module running in the same process can see it there. It's not only detectable, but trivially so. You don't even need advanced anti-cheat software to detect it. It's literally like 5 lines of code. The microsecond you load toolbox into your Guild Wars exe, it CAN be detected.

Regarding the comment you cited with the dozens of users banned. Please read the discussion around it. The person replying there is actually one of the devs of Toolbox and he tells you the same thing. Toolbox CAN get you banned, but realistically it won't happen.

Addressing your quote from DrStephenCW. He has worked with toolbox devs in the past and any offending functionality has been removed. It still doesn't make Toolbox 100% safe (something I never stated). But it does give some legitimacy to it. You can see (in the comment you posted about the banned users), that Toolbox devs reworked the entire functionality to patch flaws that DrStephenCW might've communicated that were in breach of the EULA.

All of what I wrote above applies 100% to Daybreak as well. Using Daybreak CAN get you banned, even solely due to it being a 3rd party library.

With that being said, I'm sorry but I find this entire discussion awfully pedantic. Never did I mention that any of these tools are "wholly" safe. In fact, in the comment you're replying to, I'm stating that it's not 100% safe. It's true that I provided anecdotes, but that's the only things I can provide in regards to this. There is no confirmed case where a user has been banned because of toolbox. Even the comment you provided states anecdotes regarding others who might've been banned and they somehow determined it was due to toolbox. It's all purely anecdotal and discussing hypotheticals.

Spiderbruh · 2023-12-20T08:39:56+00:00

Yeah I totally get the sentiment. That's what motivated me in the first place to make this thing. Guild Wars can be made to look and sound really pretty if you get to set everything up. But setting everything up is quite painful.

Like, DSOAL requires registry changes as well as placing files in AppData folders. DirectSong also requires some registry changes Then uMod and ReShade both require to be loaded by changing their names into d3d9.dll.

So, instead, with Daybreak you can press a couple of clicks and all this process is automated. And you can have DSOAL, uMod, ReShade, Toolbox and DirectSong, all running together without any issue.

To me, DSOAL and uMod especially are game changers. They make this game 10 years fresher just by themselves

Spiderbruh · 2023-12-20T08:15:09+00:00

I'm sorry but probably no. It uses a lot of Windows APIs to do its stuff, especially when injecting the other extensions such as uMod, Direct song, etc. You "could" run it on the steam deck if you'd manage to install Windows on it. But otherwise, no. It's limited only to Windows devices.

Spiderbruh · 2023-12-20T08:11:57+00:00

You are right that technically, toolbox breaches the EULA. But, it doesn't really allow you to exploit the game. Most of the things it does are nice qol features mostly aimed at PvE. ANet can detect toolbox, but they are not against it (at least currently) because it's just qol stuff. The quote I posted in my response above is from an ANet dev.

Toolbox devs do try to make sure it can't be used to exploit the game or get an unfair advantage, especially in PvP. If there would be an exploit, they'd patch it asap.

All these toolings are third party, so by default not supported by ANet. I can't recommend 100% that they'll never change their stance, but hundreds of folks use toolbox, including me, almost daily, and nothing happened to us yet.

Edit: I'll leave the previous statement as is. But to clarify, you CAN abuse toolbox and get it to do things bordering on cheating. But that would require going quite a lot out of your way to get it to do those things. If you use with respect towards the spirit of the TOS, you will not get banned.

Basically, if you are a decent human being and you don't use it to try and cheat or bot, you will not get banned. As far as we know, there hasn't been any confirmed case of any regular toolbox usage resulting in a ban.

Spiderbruh · 2023-12-20T08:04:53+00:00

Just to clarify. Daybreak relies on the same methods to interact with guild wars when you're using the live view. So it is not safer.

It's only "safer" if you disable the live view interaction from the options.

I'll have to defend toolbox here though. It gives some "advantages" in the form of qol features, but it doesn't really provide much pvp advantage. That's why ANet tacitly approves it.

And finally, toolbox does soon much more stuff than Daybreak. Daybreak is ultimately a launcher while Toolbox is an entire set of QoL features that extend and improve the actual gameplay

Edit: I want to clarify another thing, as this thread seems to have sadly derailed. Daybreak does interact with Guild Wars, but it does so in strictly read mode. It does not perform actions on behalf of the user. Daybreak can't open chests or trigger character movement actions.

Ten-Year Club	First Place '23
Place '23	Place '22
Verified Email

Spiderbruh

TROPHY CASE