Chris3606
Chris3606
Currently, the NuGet package for this project targets .NET Standard 1.0, as well as a a coulple other .NET framework targets:  I propose that, in addition to the current...
In somewhat size constrained maps compared to the number of rooms, the current rooms generators allow a situation to occur where only 1 room of potentially many are placed, because...
While ripple and shadowcasting cover a great many cases, it may not be difficult to allow for the support of customized algorithms for sources. If SenseSource could be subclassed in...
Currently, with respect to FOV/LOS/SenseMapping, the options are: 1. Create `FOV` instance. This allocates an array of doubles the size of the map under the hood, and is suited for...
Currently, SpatialMap implementations require you to pass the position of an object in when it is added, and call the Move function whenever it moves. This can be inconvenient, since...
Since `PolygonArea` keeps track of outer and inner points separately, it should be possible to support `PolygonArea` as an input to `DoorFinder` (or at least provide a version of `DoorFinder`...
Although it does not fit all use cases, it can be useful to have either a flag for the existing implementation, or a separate message bus implementation that uses weak...
GoRogue currently provides a very simplified version of a [disjoint set structure](https://en.wikipedia.org/wiki/Disjoint-set_data_structure). The structure is very efficient but subject to some limitations, namely; - It simply identifies sets by integer...
See #210 This fix could easily be backported to GoRogue v2.
Currently, `RectanglesToAreas` does not preserve the original placer of the room; it may be useful to have such an option.