Improve overall structure #5

Closed
opened 2022-02-18 17:15:39 +01:00 by EpicKnarvik97 · 1 comment

A better structure would be to make the id into something that the player uses to identify the paid sign. The actual text to match would be specified in a "condition". A paid sign can have one condition for each line on the sign (#2). The required permission (#4) would be specified when creating the paid sign.

I'm not sure if case and color sensitivity should be specified for the condition or for the paid sign. Perhaps both.

Need to make matching just use a .matches method. One method that checks for if a sign matches a paid sign's conditions, one method that's used to see if two paid signs have identical conditions, and one to notify about similarities.

A better structure would be to make the id into something that the player uses to identify the paid sign. The actual text to match would be specified in a "condition". A paid sign can have one condition for each line on the sign (#2). The required permission (#4) would be specified when creating the paid sign. I'm not sure if case and color sensitivity should be specified for the condition or for the paid sign. Perhaps both. Need to make matching just use a .matches method. One method that checks for if a sign matches a paid sign's conditions, one method that's used to see if two paid signs have identical conditions, and one to notify about similarities.
EpicKnarvik97 added the
enhancement
label 2022-02-18 17:15:39 +01:00
Author
Owner

Fixed

Fixed
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 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: KnarCraft/PaidSigns#5
No description provided.