#Making embed wider
66 messages · Page 1 of 1 (latest)
no
not even a fancy workaround?
not a good one, no
I've managed to be a bit hacky and make it wider, but it only makes the background wider - the content doesn't fill
Embeds are flex to the screen
you can't have 5 inline fields
Depends on your monitor resolution, so consistent results are almost impossible
:/
doesn't seem to be taking up anywhere near enough
I've seen wider embeds than mine before
they flex to content
So it refuses to let me have more than 3 fields in one line? outright?
yes that's how discord works
and can't get around that?
you'd have to make a single field show up as multiple, or similar for the description
gotcha
Idk
no, fields are fixed to 3 per line
Yeah, but wider titles might make the embed itself wider to accommodate longer titles
I don't have any ideia if it works tbh
I tried forcing the embed wider, that made the background wider to fit the content but it refused to fit more inlines
.
you'd need to not use 5 fields
unfortunately, discord doesn't allow html insertion
on mobile it will look sht either way lol
running on no sleep, here - is there a reason Cargos is being pushed over, I've padded the strings to a length of 25
const embedTemplate = {
'embeds': [
{
'type': 'rich',
'title': 'Active Ships',
'description': `\n\n${emojis['sloop']} Sloop, ${emojis['brig']} Brigantine, ${emojis['galleon']} Galleon\n\n${emojis['gold_hoarders']} Gold Hoarders\n${emojis['merchant_alliance']} Merchant Alliance\n${emojis['order_of_souls']} Order of Souls\n${emojis['athenas_fortune']} Athenas Fortune\n${emojis['reapers_bones']} Reapers Bones\n\n*\\*ship is captained*`,
'color': 0xe6c400,
'fields': [
{
'name': '** **',
'value': '\u200B',
},
{
'name': 'Server 1',
'value': '\u200B',
'inline': false,
},
{
'name': ships.map(ship => {
const display_name = `${ship_by_capacity[ship.capacity]} ${ship.emissary} ${ship.name.padEnd(25, ' ')}`;
return display_name;
}).splice(0, 3).join(' '),
'value': '\u200B',
'inline': false,
},
{
'name': ships.map(ship => {
const display_name = `${ship_by_capacity[ship.capacity]} ${ship.emissary} ${ship.name.padEnd(25, ' ')}`;
return display_name;
}).splice(3).join(' '),
'value': '\u200B',
'inline': false,
},
{
'name': '** **',
'value': '\u200B',
'inline': false,
},
],
},
],
};
@high sandal mentioning as it was your advice
any advice what to use in place?
but not sure if discord processes tabs to have them work as such
{
'name': ships.map(ship => {
const display_name = `${ship_by_capacity[ship.capacity]} ${ship.emissary} ${ship.name.padEnd(8, '\t')}`;
return display_name;
}).splice(0, 3).join(' '),
'value': '\u200B',
'inline': false,
},
{
'name': ships.map(ship => {
const display_name = `${ship_by_capacity[ship.capacity]} ${ship.emissary} ${ship.name.padEnd(8, '\t')}`;
return display_name;
}).splice(3).join(' '),
'value': '\u200B',
'inline': false,
},
closest I've got with tabs
another tab ruins it
fine tune with spaces or ?
spaces wouldn't be reliable
font differences would break it just due to how spacing works
an alternative would be to make a table and send it as an image ig
you can?
no
discord wouldn't be able to process it
discord, as well as 90% of the internet, uses unicode
the other 10% uses ascii
everything you're sending here is using unicode, spaces are unicode, tabs are unicode, the zwsp \u200B is unicode
ahah I did it
const display_name = `${ship_by_capacity[ship.capacity]} ${ship.emissary} ${ship.name.padEnd(8, '\t')}\t`;}
for some reason adding another tab without using it in the pad function works
ah yeah since that's not how tabs work lol
but if I pad to 9, it doesn't