I always thought ub suicide was something that was needed.

After some research I believe that:

9. Language for engine messages (xxx has left, xxx has joined...) in game lobby uses the hosts language setting (this should be the users language setting): my russian is a bit rusty!

May be impossible to fix. It appears that the lobby messages are sent by the host as nameless messages rather than displayed by each persons individual client. This is why they get the hosts settings instead of the users local settings. Unless we can somehow trap these messages and de-localize them I'm not sure what we can do.

Edit: I just spent an hour or so trying to work out if I could hook onto a message being sent to me to change its language but I cannot find such a spot, it seems the actual displaying of the message is handled by moho, I'd be happy to be proved wrong though.

Does anyone know someone who uses a non-English version of Demigods? I'd like to know what the 1.20 patch changed on their installation.

That's the same thing I have on my install. However, I'm using an English version. I'm not sure if other localized versions have different effects of the patch. Are you running a nonEnglish version hedgie?

I seem to remember it being said that the new Demigods were not localized, thus it would be assumed they default to the English settings. However I cannot find a tool tip for the increased attack speed buff, I get the feeling it was added to the tooltip and then decided against and then never removed from the tool tip.

Edit: Confirmed that if you run the game in a different language the English is used by default when no translation is present.

re: NonEnglish Install

Is this confirmed with an initial nonEnglish install and not just changing the Demigod initiation files? I know I sound like a stick-in-the-mud, but I try to make sure all the bases are covered. If we currently believe the patch was not localized, then we can change the blueprint string reference and it will work out.

re: Oculus not attacking beneath him

I investigated this a while back. The end result is no one could tell me why the unit could not attack beneath him. I'm guessing that it is an engine limitation which prevents units from firing through themselves. This would be annoying, but not horrible. What makes it broken is that the targeting and movement routines are also not functioning correctly. If Oculus locks onto a unit that moves beneath him, he will never switch to another target unless ordered to or if that unit dies. The Rook also suffers from this problem with his trebuchet. Something isn't quite right with the targetting routines with minradius weapons.

Pretty close to exactly beneath, I'd say within 1 map unit of his center. It is easy to replicate. Target a warrior and then right click to move next to it. He sometimes starts his attack animation but usually not.

Here is my fix for the TB and QoT state bug where they change do Ice or Opened state respectively on death regardless of what state you are in before death. I have sent this to Ptarth in a PM but it's probably best to have this here so anyone can see it.

To Ptarth: This version is even newer than the newest version I sent you, the latest version I sent you had a silly bug in it.

http://www.mediafire.com/file/jhyz0myznnz/StateFix.v.1.0.2.zip

Oh I just changed the global variable to be "self.Sync" however since it wasn't in a function it was throwing warnings because Self didn't exist. The line wasn't needed anyway so I just removed it.

Heh, it's Norwegian, Uhellig Gud is Unholy God the extra n at the end is a long story.

PS: Hopefully you don't go to the Bahamas, everything I try to fix seems to lead to a dead end written in moho. I have spent an couple of hours trying to track down either a place where the restriction on the distance is in place (This seems to run into a moho dead end) or find a way that I can change targets if this occurs. I thought I had some luck in the Weapon.lua however I can't seem to get any modifications to that file to have any effect, can you confirm or deny that LOG() works in mods?

lazy... too much work to explain, but you can update your website to current in 2-3 days or so, eh.

WHAT IS THE N?

Rawr: the "hard barrier" is a map fix. 

How maps work in demigod is there is a black and white 2D bitmap that the game loads on startup. One color represents "void" space that you cannot walk into. Currenly, it is virtually impossible to get monks stuck on the light-side. It can happen easily on dark however. I would guess this is the case because the dark side of the bitmap was copy-pasted a few pixels off. All you would have to do to fix it is edit the bitmap to be the proper block. 

Monk fix... meh. Hard to say. Demigods have all sorts of targeting and moving issues as it is. 

--

you should update your semi-active. Including me ;; I provide enough support I think I count dammit. 

re: RAWRRR on Summon Idols

I don't disagree that it may be a better solution. However it is a balance fix. In the last few patches the values to make minions steer were purposefully adjusted. I don't know whyk so o don'tthink they should be adjusted until then.

re: RAQRR on Map Barrier

I don't really know much about maps, I'm deferring to Hedgie and mrappard on this one. I seem to recall them talking about things. However I haven't looked it up recently.

re: awuffeablehedgie on map BMP

What is this file? I took a quick look, but couldn't find anything. The best I found was the minmap, but that has nothing to do with anything. mrappard suggested it was the *.scmap.

re: awuffleablehedgie as semi-active

I removed the plee to the community and job lists because it didn't go anywhere. I'll put up a new version with you and some others.

re: updated buglist

Yeah. I'll get around to it tomorrow or the next day. I also need to grab the items from the last page too. The forum has issues with me editing and it saving what I edit.

re: Oculus Autoattacking

Well, as a guiding principle the UberFix fixes bugs, it doesn't incorporate balance changes. I do believe that Oculus was intended to attack all targets within his range, and that him currently being unable to attack targets below him is indeed a bug. Saying it is a positive feature because it is more realistic isn't a valid argument. This entire game is not realistic, really if you can wear 5 helmets at the same time...

re: LOG in Modding

It does work. Did you read the short introduction to modding a wrote a page back? It contains some information on it. I think. Maybe. Anyway, here is a short guide to the LOG command.

LOG('text :' .. repr(value) .. 'second value :' repr(value2))

I don't know if there is a difference between " and '.
I don't know if there is a difference between .. and ,.

Don't use LOG on a table that refers to another table. The function tries to list all nested tables, and this usually ends up in a recursive listing that runs the Logger out of memory. Someone wrote and posted a version that only captures the top level links, but I lost it a while back and haven't managed to dig it out yet.

You'll often get /000 in your Logs. I don't recall what causes them, but on the GPG modding forum there is a version of log that strips it out. I just read around it.

Only use LOG within functions. If you try to use it as part of a table (like in a blueprint) it will break.

re: Moho targetting issues

Yeah. I ran into the same dead end. I believe I posted about it in one of my 18 page discussion posts. I might not have. I hear that I write too much anyway. If I haven't tell me and I'll write up something about it so no one has to reproduce my failed efforts.

re: Thread Volume

In the last couple of weeks the thread has increased by many pages. Many of the posts are are easy to understand and contain worthwhile information, however a significant portion are not. It would be great if everyone could try to follow the following rules.

• Don't post twice in a row, just edit your previous post.
• Try to cut back on the unnecessary chatter.
• Try to use formatting more. It is sometimes hard to follow what people are saying. (I know I'm really hard to understand sometimes.) I like bullets, indents, and bolded headings.
• Don't quote entire posts

re: Thread Diversity

It seems to me that the thread is becoming very divergent. I see discussion on general chatter, bug reports, bug fixes, balance change suggestions, and official release information. What do you guys think about creating different threads for each of these different areas instead of one general thread?

RE: Thread Diversity

I think that a single thread is probably best, but there needs to be some form of organization where we collect key posts on certain topics, say we could provide links under each bug in the top post to key posts discussing the involved bug or such. Even separate threads make it hard to find information on specific bugs, for example I read 14 pages to see if people had tackled the Oculus bug yet then found out it was apparently covered elsewhere entirely.

Depending on how seriously we want to take this I could set up a really simple hub where we could post up bugs and then leaves comments on each bug specifically. We could link to posts here on that system, or link from here to that system if we wished so that they had a sense of cohesion. Of course the loss of a seperate system is that you don't get passers by, but the benefit is we could organise the entire system ourselves really well making seperate sections for key knowledge and guides to help people get into helping out etc.

I guess it really depends on how much effort people are willing to put in etc to organize everything, the current system isn't working that badly, though I know as I have just started, I am finding it rather difficult to find ground already covered on specific issues and as such I seem to be retracing a lot of ground already covered by others (not always a bad thing, but you see my point).

I think the ability to train of thought issues is beneficial as you can reply to a number of topics easily and having to read through the thread means you learn quite a bit, but then it's also really hard to find exactly what you need etc. I've only been here a day or so, I'm sure you all have stronger opinions on how things operate.