Conversation
Can use:
std::string message = "Testing fmt::format";
g_logger.info("{}", message)
|
|
||
| --[[ | ||
|
|
||
| Servers_init = { |
There was a problem hiding this comment.
This table Servers_init must be deactivated before being merged into the main repo
There was a problem hiding this comment.
This table
Servers_initmust be deactivated before being merged into the main repo
Yes, we will revert when everything is ok, this makes it easier to test.
| #include "inputmessage.h" | ||
| #include "outputmessage.h" | ||
| #include "framework/core/graphicalapplication.h" | ||
| #include "client/game.h" |
There was a problem hiding this comment.
I think
This implementation could be achieved without including #include "client/game.h".
A new enum GameFeature should be created in const.h, and also defined in gamelib/const.lua. To activate it, it must be enabled in game_feature and then activated in gamelib/protocollogin.lua
example:
m_xteaEncryptionEnabled , m_checksumEnabled , m_sequencedPackets change the boolean from lua
https://github.com/mehah/otclient/blob/085a7876ba8164cb8eb08385812b12ceeec007aa/modules/gamelib/protocollogin.lua#L135-L148
in order to be able to login in protocol 11.00 in canary 14.xx
|
if anyone has 1> vc17\vcpkg_installed\x64-windows-static\include\fmt\base.h(458,28): error C2338: static_assert failed: 'Unicode support requires compiling with /utf-8'
1>(compiling source file 'otclient/x64/OpenGL/unity_QAHRA73EM9MJH98D.cpp')add https://github.com/mehah/otclient/blob/main/vc17/otclient.vcxproj#L261-L262 <AdditionalOptions>/utf-8 %(AdditionalOptions)</AdditionalOptions>in vc17otclient.vcxproj me test:
|
…version This commit removes the hardcoded MAX_HEADER_SIZE constant from OutputMessage and replaces it with a dynamically initialized m_maxHeaderSize based on the client version (7 for >= 1405, otherwise 8), similar to InputMessage. All references to MAX_HEADER_SIZE have been removed, and buffer positions (m_writePos, m_headerPos) are now initialized based on m_maxHeaderSize. This ensures consistency and future-proofing for different protocol versions that require varying header sizes.
13.14 was already broken before, from what I saw, I'll try to fix it About the build solution, I always use cmake, even in visual studio, so I hadn't noticed that it broke the solution, I have an open pr to add a workflow in gha to build windows with solution, thus avoiding future problems like this. Thanks |
javiertringol
left a comment
There was a problem hiding this comment.
What's missing for this to be approved? It's been 37 days since Canary approved 14.05
and 2 weeks since 14.12
What's missing? How can the community help?
|
vllsystems
left a comment
There was a problem hiding this comment.
I'm using this since 13/06 and no crashs, no kicks, no breaks.
Sounds good to me.
This comment has been minimized.
This comment has been minimized.
bateunatrave
left a comment
There was a problem hiding this comment.
tested for a long time without problems.
The 14.12 charms window (which has been completely changed) needs to be tested and fixed. From the comments here, it's clear that it wasn't properly tested. If it had been tested, you would have seen that the charms window doesn't work. If anyone has UI/module knowledge, they can do this so we can merge it. |
|
I'm happy just being able to login. Also, many times we have to use the cipsoft client — like with the Wheel or Forge — and then go back to the OTC client. I guess it'll be the same with Charms. |
|
I've had it done for a while in PR #1171. I made sure not to break backward compatibility. i create two UI (.otui)
At that time, I was just missing information on where to get the charm data from version 14.00, since it's not retrieved from the proto or server. |
|
@kokekanon if you want, here is a example of the latest image from Cipsoft. And yes, those informations like description do not come from proto or server (they're hardcoded on client-side, like the magical archive is). If you need more support regarding the image extraction, tell me. I can help you.
|
i don't use canary, quick test works
I have to check if I broke something in 13.40 I don't like modifying PRs that aren't mine, especially if I don't have the author's permission. I'll reopen my PR, take the 14.00 header fix, and merge it with the features and packets I already have there. |
|
@kokekanon looks great! If you want, commit in the same branch. Then we can adjust anything if necessary. |
With these exchange rates does it work out at 15.00? |
|
this PR is being closed for PR merge #1171 1171 |









Description
Support to version 14+
Type of change
Checklist
Co-Authored-By: Eduardo Dantas eduardo.dantas@hotmail.com.br