your-land/bugtracker
your-land
/
bugtracker
44
20
Code Issues 2.5k Projects 2 Wiki

Heraldic shields: Dragon and Party-per-pale #6278

New Issue
Closed
opened 2024-02-11 11:22:53 +00:00 by Chache · 9 comments
Chache commented 2024-02-11 11:22:53 +00:00
Copy Link

I made two new heraldic designs to be available for castle shields representing cities' coats-of-arms.

The first of them, a dragon, is historically accurate and I think I've managed to make a design that's both recognisable and fits into the 16x16 square. Maybe Cold Drake is interested in using this design for its coat-of-arms.

The second, "party per pale" is simply the technical term (see: [https://en.wikipedia.org/wiki/Division_of_the_field#Common_divisions_of_the_field]) for a vertical division of the shield into two halves.

Party-per-pale allows the further possibility of having a heraldic design consisting of 3 vertical stripes of different colours, stacking the "pale" design on top. I know Rubodyke is requesting to have a coat-of-arms with such a design in cyan-white-green from left to right, which is currently not possible. With the party-per-pale design, that coat of arms could be made with:

castle_shield_cyan.png^(castle_shield_green.png^[mask:castle_shield_mask_partyperpale.png)^(castle_shield_white.png^[mask:castle_shield_mask_pale.png)

supposing the new mask is named castle_shield_mask_partyperpale.png

I made two new heraldic designs to be available for castle shields representing cities' coats-of-arms. The first of them, a dragon, is historically accurate and I think I've managed to make a design that's both recognisable and fits into the 16x16 square. Maybe Cold Drake is interested in using this design for its coat-of-arms. The second, "party per pale" is simply the technical term (see: [https://en.wikipedia.org/wiki/Division_of_the_field#Common_divisions_of_the_field]) for a vertical division of the shield into two halves. Party-per-pale allows the further possibility of having a heraldic design consisting of 3 vertical stripes of different colours, stacking the "pale" design on top. I know Rubodyke is requesting to have a coat-of-arms with such a design in cyan-white-green from left to right, which is currently not possible. With the party-per-pale design, that coat of arms could be made with: `castle_shield_cyan.png^(castle_shield_green.png^[mask:castle_shield_mask_partyperpale.png)^(castle_shield_white.png^[mask:castle_shield_mask_pale.png)` supposing the new mask is named castle_shield_mask_partyperpale.png
Dragon.png
361 B
Party_per_pale.png
298 B
Dragon.png Party_per_pale.png
👍 9 ❤️ 1
flux added the
1. kind/enhancement
3. source/art
 labels 2024-02-11 19:15:03 +00:00
AliasAlreadyTaken commented 2024-02-12 08:50:10 +00:00
Owner
Copy Link

Please PR :)

Please PR :)
🚀 1
whosit commented 2024-02-14 07:25:13 +00:00
Member
Copy Link

Added:
e42604fba4
Screenshot 2024-02-14 102156

Moved dragon one pixel up to fit better.

Added: https://gitea.your-land.de/your-land/castle_shields/commit/e42604fba43d1703c61294d728fc9231e2432f0e ![Screenshot 2024-02-14 102156](/attachments/8d366633-8195-4ec7-aee3-d4faaa96e61a) Moved dragon one pixel up to fit better.
Screenshot 2024-02-14 102156.png
11 KiB
❤️ 1
whosit added the
5. result/fixed
 label 2024-02-14 07:25:37 +00:00
AliasAlreadyTaken added this to the 1.1.123 milestone 2024-02-14 07:46:13 +00:00
AliasAlreadyTaken added
4. step/ready to QA test
ugh/QA OK
 and removed
5. result/fixed
 labels 2024-02-14 07:46:27 +00:00
AliasAlreadyTaken commented 2024-02-14 08:23:48 +00:00
Owner
Copy Link

QA

Looks nice IMO and is added to the demo shields as well

QA Looks nice IMO and is added to the demo shields as well
Boot commented 2024-02-14 12:07:44 +00:00
Member
Copy Link

Party-per-pale allows the further possibility of having a heraldic design consisting of 3 vertical stripes of different colours, stacking the "pale" design on top. I know Rubodyke is requesting to have a coat-of-arms with such a design in cyan-white-green from left to right, which is currently not possible. With the party-per-pale design, that coat of arms could be made with:

castle_shield_cyan.png^(castle_shield_green.png^[mask:castle_shield_mask_partyperpale.png)^(castle_shield_white.png^[mask:castle_shield_mask_pale.png)

Will that work when?

> Party-per-pale allows the further possibility of having a heraldic design consisting of 3 vertical stripes of different colours, stacking the "pale" design on top. I know Rubodyke is requesting to have a coat-of-arms with such a design in cyan-white-green from left to right, which is currently not possible. With the party-per-pale design, that coat of arms could be made with: > > `castle_shield_cyan.png^(castle_shield_green.png^[mask:castle_shield_mask_partyperpale.png)^(castle_shield_white.png^[mask:castle_shield_mask_pale.png)` Will that work when?
whosit commented 2024-02-14 13:02:15 +00:00
Member
Copy Link

castle_shield_cyan.png^(castle_shield_green.png^[mask:castle_shield_mask_partyperpale.png)^(castle_shield_white.png^[mask:castle_shield_mask_pale.png)

Will that work when?

It does work as texture combinator (the string Chache wrote)...
But current way of how shields are defined in the mod is limited to just 2 colors + 1 mask...
Should not be too hard to update it to take just custom texture strings too?

`castle_shield_cyan.png^(castle_shield_green.png^[mask:castle_shield_mask_partyperpale.png)^(castle_shield_white.png^[mask:castle_shield_mask_pale.png)` > > Will that work when? It does work as texture combinator (the string Chache wrote)... But current way of how shields are defined in the mod is limited to just 2 colors + 1 mask... Should not be too hard to update it to take just custom texture strings too?
Boot commented 2024-02-19 17:01:13 +00:00
Member
Copy Link

Should not be too hard to update it to take just custom texture strings too?

What update could it be part of? Maybe already with the 1.1.123?

> Should not be too hard to update it to take just custom texture strings too? What update could it be part of? Maybe already with the 1.1.123?
AliasAlreadyTaken commented 2024-02-20 14:38:59 +00:00
Owner
Copy Link

The new charges will be in with 1.1.123, multicolour will not.

A three-colour setup reuqires a rewrite. Two colours are easy using black and white masks. If a third colour comes into play, we could support 4 or 5 colours as well. But not with the current code or update. If this is a wish, please open a new issue.

The new charges will be in with 1.1.123, multicolour will not. A three-colour setup reuqires a rewrite. Two colours are easy using black and white masks. If a third colour comes into play, we could support 4 or 5 colours as well. But not with the current code or update. If this is a wish, please open a new issue.
Boot commented 2024-03-09 10:37:04 +00:00
Member
Copy Link

That party-per-pale would be nice to implement the shield of the Republic.

That party-per-pale would be nice to implement the shield of the Republic.
👍 1
flux added
5. result/fixed
 and removed
4. step/ready to QA test
 labels 2024-03-28 22:23:32 +00:00
flux commented 2024-03-28 22:23:39 +00:00
Member
Copy Link

this is live

this is live
flux closed this issue 2024-03-28 22:23:39 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
1. kind/balancing

Depends on balancing

  
1. kind/breaking

something that alters or disables an existing game mechanic

  
1. kind/bug

Something is not working

  
1. kind/construction

A build needs fixing

  
1. kind/documentation

Needs proper documentation

  
1. kind/enhancement

New feature

  
1. kind/griefing

players despoiling builds or nature

  
1. kind/invalid

Not a valid report, e.g. created by mistake with no content.

  
1. kind/meme

issue is mostly a joke

  
1. kind/node limit

something which works for or against the node limit

  
1. kind/other

Something not within the other kinds

  
1. kind/protocol

something concerning how staff should react to player requests, or how players should treat each other

  
2. prio/controversial

not likely to happen w/out a lot of discussion

  
2. prio/critical

Very important

  
2. prio/elevated

something players are eager to have fixed

  
2. prio/good first issue

the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem

  
2. prio/interesting

one of us has real interest in getting this implemented or fixed. however, more research might be needed.

  
2. prio/low

Not so important

  
3. source/art

art needs to be created or found for this to exist. includes sound, 3d modelling, and in-game building.

  
3. source/client

Issue is with the minetest client, or with player client configuration or the technical details of their setup

  
3. source/engine

Issue is due to a bug or feature of the minetest engine

  
3. source/ingame

Problem and solution exist in-game, e.g. builds or player moderation

  
3. source/integration

Two or more nonbuggy mechanics conflict, or our attempts to rectify conflicting mechanics have created a new bug

  
3. source/lag

A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues

  
3. source/license

A licensing problem is involved

  
3. source/mod upstream

Problem is upstream (not engine/client)

  
3. source/unknown

   
3. source/website

Affects the website

  
4. step/approved

Alias has approved this feature, someone should implement it

  
4. step/at work

Being worked on

  
4. step/blocked

we plan to do this, but other work has to be finished first

  
4. step/discussion

issue is under discussion, a solution has not been dictated or agreed upon

  
4. step/help wanted

Need some help

  
4. step/needs confirmation

   
4. step/partially fixed

this is mitigated or partially solved, but more work needs to be done

  
4. step/question

More information is needed

  
4. step/ready to deploy

has been QA tested by another person. has no outstanding issues. might be installed on prod, but needs final testing

  
4. step/ready to QA test

the code is supposedly fixed, but needs to be tested.

  
4. step/want approval

Someone can quickly implement this if Alias approves the change/feature

  
5. result/cannot reproduce

   
5. result/duplicate

This issue or pull request already exists

  
5. result/fixed

problem is fixed

  
5. result/maybe

not planned currently, but maybe some day

  
5. result/wontfix

the reported issue won't be changed, whether it's intentional or not.

  
ugh/petz

yet another petz bugz.

  
ugh/QA main

That's something we can only wait and see whether it hapens again: On the main server

  
ugh/QA NOK

Fix didn't yield the expected results

  
ugh/QA OK

tested

No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
Milestone
Clear milestone
No items
No Milestone
1.1.123
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#6278
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?