{5} Accepted, Active Tickets by Owner (Full Description) (3 matches)
List tickets accepted, group by ticket owner. This report demonstrates the use of full-row display.
Mad Martian (3 matches)
Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#95 | Path-finding is suffering regressions | Entity Sub-system | defect | 3 years ago | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Even on a perfectly flat surface with direct, uninhibited line of sight between two points, a pathing mob will stagger and even backtrack on the way. This is ridiculously unnacceptable path-finding behaviour. This issue was first reported from Minestom |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#80 | Deploy KeyCloak Infrastructure | Infrastructure | task | 5 years ago | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
OIDC + 2FA w/ LDAP IFSince someone has been trying to steal the source code from this project since yesterday the time has come to do something about this. And it just so happens that this is precisely what I do in my day job. The task is to implement this security (Open ID Connect with Two-Factor Authentication and LDAP Identity Fedration) using KeyCloak (I already have experience with it). Here are the necessary steps involved
Server resources are already pretty tight, and KeyCloak is not light-weight at all (it runs on WildFly, the new name for JBoss, which is a cousin to Apache Tomcat, none of which means anything to you does it?). If that's the case then I'll have to revist. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#58 | Villager Economy System | Blocks and Items | enhancement | 5 years ago | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PreambleThe purpose of this ticket is to introduce an economy system or manager that alters supply and cost of goods offered by villagers given certain market drivers most typically being demand and sale frequency. Please discuss this idea here using the comments on this ticket. Think about some of the issues raised by this idea and post your thoughts and ideas about how to handle these here using this ticket. Supply and Demand ControlsIt seems to be agreed that villager offers should be influenced / driven by the frequency an item is bought or sold:
Issues to Consider
Currency UsedPresently the villagers accept items in exchange for other items, they have no concept of currency. Issues to Consider
New Trader EntityRather than modify the villagers, introduce a new entity type exclusively designed for buying/selling goods using currency instead of in-game items. Issues to Consider
RarityNot all items are created equal, dirt is literally dirt cheap and diamonds or rhenium ingots are extremely expensive. This implies two things for each item based on its rarity:
Issues to Consider
Price PointHow should the initial prices be calculated? it seems there are different categories of items and price pointing everything may be unnecessary:
Issues to Consider
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||