I don't know of any limitations in POL. You might want to keep the size divisible by 8x8.

And if I recall correctly, some clients even accept larger map widths as long as you keep the height 4096

You can try to install pkg-config and run the build again:
Cmake is complaining that it can't find that tool

Hi b0ris, sorry to hear the experience has been so bad. Which version of POL are you compiling? On GitHub, our action builds for (I think) Ubuntu 20.04 here: https://github.com/polserver/polserver/blob/master/.github/workflows/build.yml Your compilers need to have a recent version. For gcc, that's a...

That's a fair point. It might also be a good opportunity to change the default hash algorithm to something that is more expensive to brute-force. And a hash string that is more future-proof.

As a workaround for now, could you use a map of lower-case names to the original names in accounts.txt?

Cool! That's great!

If you are using the Modern Distro, you can try the command .decoratefacets

That might take a while but will create spawns, doors, etc for you

That looks fine to me. For Razor, do you have "Patch client encryption" checked on the start screen? You are using the 2D client, right? You could also try an older client, just in case something got changed. Also, feel free to join our Discord chat (the link is on the top of the "Con...

Weird. Can you post your Listener from uoclient.cfg here? And are you using Razor to remove client encryption?

[...] it never leaves the "Verifying account" screen and in the pol this apears: GuildManager Loaded Undefined message type 0x8B Client#1: Unexpected message type 0x8B, 62 bytes (IP: 127.0.0.1, Account: None) 0000 8b 89 f6 cc 4f 0d ad 77 f2 86 3c e1 8f 38 63 ce ....O..w ..<..8c. 0010 98 b...

... INSTALLING: Exported Vital - RegenRate and MaxValue functions ... Itemdesc has no 'graphic' specified, and no 'objtype' is valid either. Error reading configuration file pkg/items/runicAtlas/config/itemdesc.cfg: Configuration error Element: Container 0x9C16, found on line 1 Server Shutdown: loa...

It looks fine to me. Like someone rebound new spines to match the furniture

Congrats for the baby!

I'm not following the client data very closely. Do you mean verdata.mul? Here is a reference to UO file formats: https://uo.stratics.com/heptazane/fileformats.shtml It's a bit old but not much has changed since then. One thing that changed: after HSA, new fields were added to the structs. Especially...

Welcome! The map does look quite neat. It would be great to see it in action.

Are you already hanging with us on Discord?

That's because the core needs to support the newer clients. Your best bet would be to find other client versions or try to upgrade the scripts to a newer core.

You need to run "uoconvert" to create the map and statics files used by POL. This batch file can help you: https://github.com/polserver/ClassicDistro/blob/master/batchfiles/realmgen.bat But in summary, you need to convert all configs and at least the "britannia" realm: uoconvert ...

Yes, optimize for single-threaded performance and a few cores. At the moment POL can't effectively use that many cores because the architecture requires a global lock in many common operations. So it doesn't hurt to have more cores, but POL won't use all of them.

In the future: if someone has issues validating their email, just write us a message. We can manually validate them.

Welcome back! (And we may need some proof - like the source for an old core )

We've been using Discord for chatting. If you'd like to join us there: https://discord.gg/2hQTeyc

Which visual studio version do you have? Have you changed your version recently? If so, did you run cmake again?

Given that you have a linker error, I'd assume the compiled binary is looking for the wrong libraries.

It should be fixed in the latest commit.

Thanks Yukiko for summarizing our plans. Another thing on the oven is native Unicode support, which Bodom is working on right now.

Just to clarify: the "length < 3" condition is only for variable-length packets. This makes sense because you need at least 3 bytes in those cases: packet id (1 byte) + size (2 bytes).

It was already time for it

Let me know if there are any other suggestions to simplify the forums.

Moved to new board...

[Just a quick note that we now have a forum for POL100, and I moved the topic there.]