Free Allegiance Forums

listen less to voobs and more to vets when making GAMEPLAY changes.

_xJammer_ wrote:QUOTE (_xJammer_ @ Jan 29 2018, 01:01 PM) Belter carrier parked next to aleph. Do not know how to reproduce.

I tested it, can't reproduce it.

_xJammer_ wrote:QUOTE (_xJammer_ @ Jan 29 2018, 01:01 PM) Loadouts - just save the last loadout used along with Ctrl + w/e. Do not reset the loadout upon docking or restarting the game. (Like literally default loadout chosen = last launched loadout)

That is about how it is right now. The problem is just the before-mentioned multitude of ships/factions/cores which hides the fact.

_xJammer_ wrote:QUOTE (_xJammer_ @ Jan 29 2018, 01:01 PM) Now I have to repeatedly either Ctrl+1 every launch, or launch with useless cargo.

Ctrl+1 saves it, 1 restores it.

_xJammer_ wrote:QUOTE (_xJammer_ @ Jan 29 2018, 01:01 PM) P32 was having issues with camera being off-set by 10-20 degrees to the right ( his bullets were firing basically sideways). Not sure if he posted the report yet.

From LANS:
Oh, that happens sometimes if you have a gamepad or somesuch plugged in and not properly configured
Alleg will rotate the view a bit, it thinks it's getting input from the gamepad on where the camera should look
Solution is unplugging, and restarting

_xJammer_ wrote:QUOTE (_xJammer_ @ Jan 29 2018, 01:01 PM) Allegiance is spaghetti code. Someone grab unity + w/e networking engine and slap something together, will take nearly as long as fixing alleg bugs. Myself and Dj unfortunately kind of gave up on it atm.

Feel free. I'd expect that to take about 5 years of pro man-power. That is with re-using all the old graphics/sounds and stuff. I may be wrong though.
Allegiance currently has no bugs I'd call major, except the new ones introduced with this patch. Most of those are already fixed in the code-base. The server crash will probably take me something like 2 hours to fix once I can get at the crash logs.

Nan change in the loadout is good homie, xj is just being a little bitch like ush

Devs should always be reaching out for feedback from the community, but probably focus on the peeps giving constructive feedback as opposed to asanine “x should be y” input with no reasoning behind it

vogue wrote:QUOTE (vogue @ Jan 30 2018, 09:21 AM) Nan change in the loadout is good homie, xj is just being a little bitch like ush

Devs should always be reaching out for feedback from the community, but probably focus on the peeps giving constructive feedback as opposed to asanine “x should be y” input with no reasoning behind it

Its more of a comfort thing. Having to twiddle around every launch gets annoying pretty quick.

But I admit, I am not invested enough to argue or care about my complains being implemented - so feel free to completely disregard any feedback I'v given.

That’s fair, but let’s take a step back and look at the bigger picture. 9/10 times if a scout pilot doesn’t have a nan, it isn’t because they intentionally meant to do that. It’s because they didn’t know, forgot, etc.

I think what really rustled your jimmies was your loadout not saving, which is an understandable issue that can be addressed and makes sense. But you took it down a weird path that makes no sense. Hence my point above about explaining the rationale behind your thinking homie

_xJammer_ wrote:QUOTE (_xJammer_ @ Jan 30 2018, 08:35 AM) Its more of a comfort thing. Having to twiddle around every launch gets annoying pretty quick.

But I admit, I am not invested enough to argue or care about my complains being implemented - so feel free to completely disregard any feedback I'v given.

We have in the pipeline (but maybe not for a while) an implementation of gui buttons for saved loadouts that will act the same now as the ctrl+# loadout system. Won't make a difference for vets, will solve the use case problem of "I didn't know that feature existed"